Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The following css (sheetnode.css) breaks fieldsets in IE:
/* Fix fieldset relative offset problem: http://drupal.org/node/735674 */
html.js fieldset.collapsible { position: static; }
Put "relative" just for IE8 solves the problem.
Comment | File | Size | Author |
---|---|---|---|
fieldset-fail.png | 27.08 KB | soulfroys |
Comments
Comment #1
infojunkieBut the whole reason for the CSS is to fix a problem caused by fieldsets with
position: relative
. Are you saying that the problem addressed by the CSS does not show up in IE8? If so, can you suggest a way to avoid that CSS rule in IE8 specifically?Comment #2
infojunkieAlso, can you help me reproduce this? Basic sheetnodes are appearing fine on my IE8 in the Garland theme.
Comment #3
soulfroysYou're right! In Garland works ok. The problem must be with my (rubbish) custom theme... I am really sorry about the buzz. :(
Thanks for your time!
Comment #4
mausolos CreditAttribution: mausolos commentedSo the past couple months, since I've installed Sheetnode, I've noticed that when I'm in the Seven admin theme in views, I can't get links to scroll when editing fields, filters, sorts, etc - in other words, if the editing space is long enough to scroll, the links stay where they are outside of the edit space, so you can't access the settings there.
sheetnode.css (line 56)
html.js fieldset.collapsible { position: static; }
When I disable this line in Firebug while live on the page, the problem just goes away, and I'm able to scroll properly again.
So to be clear, you could reproduce this issue by opening up any view in Firefox, Chrome, Safari or IE9 on OSX, Windows or Ubuntu, clicking on any of the links that allow you to edit parameters/settings for the view.
Comment #5
infojunkieFixed in the latest dev. Please test and let me know. I can make a new beta release.
Comment #6
mausolos CreditAttribution: mausolos commentedYup! That fixed it, thanks! Pretty fast response, I'm impressed! :)
Comment #7
infojunkieThanks. It was already fixed though, I just replied to you :-) New beta containing fix released.