Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Sticky table headers in a clean install of Drupal 7.10 are messed up. They are pushed to the side whilst leaving white gaps in the middle.
It appears not to be related to a specific theme as both Bartik, Seven and Stark show the same issue.
My guess is that it is more a javascript and/or CSS problem.
See some screenshots here: (hopefully they stay on the gyazo server)
Safari
http://gyazo.com/c77f1ce90a37df5d680ef957e82314e9 (Bartik theme)
http://gyazo.com/3e74408cf925d2fda1549a851f237369 (Seven theme)
http://gyazo.com/d5eded91d440d82b23e795e370447367 (Seven theme)
http://gyazo.com/b0fd7bc4031ca8118bade6937785217b (Stark theme)
Google Chrome
http://gyazo.com/8dfefff4b96130f104b1ad25240c59d5
Firefox: doesn't have this issue
http://gyazo.com/9036834bd17bd8f2aa94514f7549c4f2
Opera: doesn't have this issue
http://gyazo.com/16cb4b12a00876aa2e3894a3f8ed53bb
Some say that it is related to the Overlay module but when this module is turned off and caches are cleared the issue still shows.
(side note: uploading files here is a pain.. the first gets uploaded but the second always gets stuck.. therefore only one uploaded image :) I'll have to report another issue for that as well I guess )
| Comment | File | Size | Author |
|---|---|---|---|
| Safari-5-1-2-Seven2.png | 91.21 KB | bassplaya |
Comments
Comment #1
crifi commentedI can confirm this bug. I think this issue is caused by the "show row weights" function of the sortable tables.
Comment #2
crifi commentedThis issue is probably a duplicate of #988930: Sticky table headers need to react properly to "show/hide weights column" link. Please test the patch in this issue.
Comment #3
bassplaya commented@crifi: I don't understand why you changed the version to 8.x-dev? It happens in 7.x-10 as well. Can you explain please?
Comment #4
crifi commentedIssues should be reviewed against the latest dev version of Drupal:
More you can find in the doc page: http://drupal.org/node/73179
If possible test the patch provided in #988930-52: Sticky table headers need to react properly to "show/hide weights column" link against the latest dev version to accelerate the work on this issue. We should find out if the issue is already reported before doing something else.
Comment #5
geerlingguy commentedJust confirming that I've had this bug annoy me so much I've disabled sticky headers on most D7 sites I use.
Comment #6
swentel commentedIt's a duplicate indeed. see #988930: Sticky table headers need to react properly to "show/hide weights column" link
Comment #7
bassplaya commented@ crifi: I understand now why I didn't find anything in the issue queue of Drupal core 7.10 (the latest release at this moment), because I didn't look in 8.x-dev? That doesn't make sense man.. you have a problem with Drupal 7 why would you look into Drupal 8? I could understand if one were to look in 7.x-dev, yes but 8?? So next time I have a problem with Drupal 6 I have to look in the issue queue for 7x.-dev or 8.x-dev? I'm sorry but I don't get this logic.
I'll try the patch in Drupal 7.x-10 and let you know.
Comment #8
bassplaya commentedWhich means: Drupal 7.x-dev not Drupal 8.x-dev imho
Comment #9
crifi commentedHey. The reason for this behavior is the development cycle of the Drupal core:
Bugs are always fixed against the highest development version. That means if there is a bug in D6, D7 and the current highest development version 8.x-dev than the bug is fixed in 8.x-dev first. The reason is, that a couple of bugs (which are hard to fix in lower versions) won't be backported to the lower versions of drupal. To avoid bugs in future versions we fix them in the highest one first...
D6 and D7 bugs should be always queued in 7.x-dev and so on...
Looking at issue #988930: Sticky table headers need to react properly to "show/hide weights column" link you will see, that this bug is queued in 8.x-dev. Sorry, but that's the logic.
Comment #9.0
crifi commentedI added the specific version of Drupal being 7.10 as I had set that as the version where I found the issue in but someone moved it to Drupal 8.x-dev.. I can't find the logic in that. I'm sorry.