If the subscriptions fieldset is placed in a block, and is not expanded by default, then the table containing the checkboxes is invisible on Internet Explorer 7 (but not 6 or 8).

If the fieldset is placed above the comments (instead of in a block), then it works correctly, regardless of whether the fieldset is expanded by default.

I tried using Firebug Lite in IE 7 and comparing what I saw with Firebug Lite in IE 6 -- and discovered that hovering over the "tr" elements in Firebug makes the entire table spring into visibility, after which it begins to function correctly (at least for the duration of that page load under Firebug). However, I have no clue what Firebug's hovering is doing, except perhaps trying to show a bounding box or highlight the area. Hovering in Firebug Lite over the "tr" elements also fixes the problem when the fieldset is collapsed - i.e., you don't have to expand the fieldset first, you can just hover over the "tr" in the source, and then if you expand the fieldset it shows up.

It appears as though there is some subtle issue with IE 7, perhaps a missing event or a subtle difference in event order that's causing this -- and causing it only when the fieldset is in a block and initially collapsed.

Sadly, this is way over my current level of Javascript-fu, or I would try to submit a patch along with this report. :-( I did try two different themes (Garland and Pixture), and used browsers on different computers to try to rule out any other idiosyncrasies besides the ones described above.

Comments

pje’s picture

pje commented

One more piece of information: if you choose the "Display only a Subscribe link that makes the fieldset visible" option, then it works correctly in a block on IE7.

So, the precise settings that fail are:

  • Always display the fieldset
  • Fieldset in Subscriptions interface block (below the comments)
  • "Expand the node form fieldset" NOT checked

Any deviation from this precise combination will work. Unfortunately, this is exactly the combination I want to use on my sites. ;-)

However, I've also noticed that this combination of settings will not ALWAYS produce the problem: some logins and some pages do not seem to have the problem, and I have not yet been able to ascertain why.

salvis’s picture

salvis
he/his
commented

Thank you for your precise report. I'm completely stumped over what to do here. We're using only standard Drupal elements and not doing anything funny, so this must be an issue in core's fieldset implementation, but since it's triggered only in a very specific situation, the chances for getting it fixed are not so great.

Do you know if it occurs in D7 as well?

pje’s picture

pje commented

No, I don't have any D7 installations as yet. For the moment I've resorted to just putting the fieldset above the form, and using the link option.

(As far as "not doing anything funny", I was thinking this maybe had something to with your behaviors for making the checkboxes appear and disappear, but as I said my level of jQuery-fu is inadequate to actually testing that.)

salvis’s picture

salvis
he/his
commented

(As far as "not doing anything funny", I was thinking this maybe had something to with your behaviors for making the checkboxes appear and disappear, but as I said my level of jQuery-fu is inadequate to actually testing that.)

Yes, maybe. You can easily test that by temporarily clearing the .js file on your site, clearing your browser cache, and checking whether that makes any difference.

salvis’s picture

salvis
he/his
commented
Status: Active » Closed (cannot reproduce)

No follow-up.