Mozilla Mac: collapsible fieldsets display error [#210615]

I'm having this strange behavior since months ago and I cannot understand how this have not been reported yet. At least, I could not find any fixed nor a pending issue about it.

I attach an image for a better understanding: on pages with some form fieldsets, like the admin/build/modules page, when there is a large fieldset placed anywhere in the page, like when you have plenty of views modules installed or the core modules filedset, the elements inside that fieldset doesn't show properly, and make actually some of those elements invisible. See the attached image. I had this same problem on admin/build/themes with a large list of themes installed. You might only see this problem when scrolling the window.

I'm using Firefox 2.0.0.11 on a Mac with no add-ons (I deactivated them) and the garland theme. I'm having this same problem with Netscape Navigator 9.0.0.1 for Mac. (no problems with Safari or Opera)

Possibles solution I've found:

1.- Deactivating admin menu module. Too bad.
2.- Deleting the following css value in modules/system/system.css (core css file)

line 333

html.js fieldset.collapsible .fieldset-wrapper {
  overflow: auto;
}

Comment	File	Size	Author
#9	Firefox OSX bug screenshot.png	50.69 KB	Andy Inman
#9	Firefox OSX bug screenshot2.png	68.91 KB	Andy Inman
#2	admin_menu-DRUPAL-5--2.css-fieldsets_2.patch	543 bytes	robertgarrigos
#2
#1	admin_menu-DRUPAL-5--2.css-fieldsets.patch	535 bytes	sun
#1
	admin_menu_error.png	5.13 KB	robertgarrigos

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

sun

German

Karlsruhe

CreditAttribution: sun commented 16 January 2008 at 20:46

Title:	display error within form fieldset	» Mozilla Mac: collapsible fieldsets display error
Component:	Code	» CSS / Browser Support
Priority:	Critical	» Normal
Status:	Active	» Needs review

File	Size
admin_menu-DRUPAL-5--2.css-fieldsets.patch	535 bytes

First shot. I have no Mac available, so I'm not able to test attached patch.

Comment #2

robertgarrigos CreditAttribution: robertgarrigos commented 17 January 2008 at 10:48

File	Size
admin_menu-DRUPAL-5--2.css-fieldsets_2.patch	543 bytes

nop. Setting the height doesn't help either. I changed the patch a bit and this fixed the problem.

Comment #3

Owen Barton CreditAttribution: Owen Barton commented 8 February 2008 at 03:37

Subscribing

Comment #4

robertgarrigos CreditAttribution: robertgarrigos commented 8 February 2008 at 09:08

Status:

Needs review

» Reviewed & tested by the community

this is ready to be commited, if no one else thinks differently

Comment #5

sun

German

Karlsruhe

CreditAttribution: sun commented 8 February 2008 at 19:04

@Grugnog: Did the last patch work for you?

Comment #6

Owen Barton CreditAttribution: Owen Barton commented 11 February 2008 at 06:42

@sun: I don't have a mac (yay Ubuntu!), so I can't actually test this one...

Comment #7

marcoBauli CreditAttribution: marcoBauli commented 12 February 2008 at 16:09

same problem

just used the patch above and things work sweet now :)

Comment #8

sun

German

Karlsruhe

CreditAttribution: sun commented 12 February 2008 at 16:32

Status:

Reviewed & tested by the community

» Fixed

Committed, thanks!

Comment #9

Andy Inman CreditAttribution: Andy Inman commented 25 February 2008 at 17:45

Priority:	Normal	» Critical
Status:	Fixed	» Postponed (maintainer needs more info)

File	Size
Firefox OSX bug screenshot2.png	68.91 KB
Firefox OSX bug screenshot.png	50.69 KB

Thanks for throwing some light on this which has been driving me nuts since I started using Druapl a few months ago. My problem is *not* fixed by the patch or latest version of Admin Menu. This is clearly not a bug in Admin Menu, but somehow triggering a bug in Firefox OSX (I also confirmed some time ago that Camino, another Gecko based browser for OSX behaves similarly.) Please see attached screen shots - this looks to me like memory corruption in Firefox, but I've confirmed it only happens when Admin Menu is in use. Seems to occur with a long page with lots of collapsible fieldsets, maybe only in "edit" mode (I always get the problem on node edit screens.) Can anyone confirm this? I want to put in a bug-report to the Firefox team, but I'm not sure what the factors are - Drupal, collapsible fields and Admin Menu - maybe depends on Mac model, I've had this problem with an old iMac G3 and a newer eMac G4. It doesn't happen with Safari (Apple's own browser offering)
The screen corruption occurs when scrolling down the page. In the second screen-shot, part of the contents of a different tab (showing Google main page) are left on the screen after switching from the Drupal tab to the Google tab and then back. Again, this is *not* a bug as such in Admin Menu, but something it and/or Druapl collabsible fields are doing is triggering a Firefox/Gecko bug (or is it a lower-level video driver bug in the Mac?) Please give whatever info you can so I can put a more meaningful report together for the Firefox folks. Thanks.

Comment #10

Andy Inman CreditAttribution: Andy Inman commented 25 February 2008 at 22:14

Category:	bug	» support
Priority:	Critical	» Normal

Spoke via irc to the Mozilla people - not much chance of getting any response unless the bug is also exhibited in Firefox 3 - I can't run Firefox 3 as it needs OS X 10.4.x which is a chargeable upgrade from 10.3.x -- Anyone using OS X 10.4.x with firefox 3 can confirm whether or not this is a problem?

Comment #11

robertgarrigos CreditAttribution: robertgarrigos commented 25 February 2008 at 22:38

mmmm I had the same problem shown in your screenshots and this patch actually fixed the problem. Have you tried to run firefox without plugins? With what drupal urls are you still having this problem?

Comment #12

Andy Inman CreditAttribution: Andy Inman commented 3 March 2008 at 10:45

Status:

Postponed (maintainer needs more info)

» Reviewed & tested by the community

Um... Thanks for the pointer. I checked again, and took a closer look at what css was actually active on the page (thank you firebug) - turned out that some custom theme css was setting the overflow property so that's why the problem was occurring even after the patch/new version. So, apologies, the fix works (just make sure nothing else is setting the overflow property again.) Still not good that Firefox can be broken in this way but nothing's perfect.