Closed (duplicate)
Project:
Drupal core
Version:
5.1
Component:
base system
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
11 Feb 2007 at 09:19 UTC
Updated:
4 Nov 2009 at 15:18 UTC
I have found that the new, fancy-schmancy option/selectors work just fine in the Konquror browser, but NOT in the most recent release of Firefox (2.0.0.1).
MENU SETTINGS, COMMENT SETTINGS, AUTHORING INFORMATION, PUBLISHING OPTIONS, and INPUT FORMAT.
Firefox does not show the little triangle/expandy thing, and the phrases are NOT hyperlinks.
Regardless of whose bug it actually may turn out to be, Drupal needs to fix this to work with Forefox. This is a showstopper/install older version level problem. MAJOR usability problem.
(scrnshot attached)
| Comment | File | Size | Author |
|---|---|---|---|
| scrShot.png | 6.08 KB | crawdad |
Comments
Comment #1
mr700 commentedI had the same problem when our counter stopped working for a while (4.7 though). After the request for the counter image times out all 'onload' events fire and all is ok, but this can take a looong time. Is that the problem? Please check if you have any such image (or wait 5-15 minutes and see if FF shows all controls).
Comment #2
giorgoskI confirm this behaviour,
I have also realized that it does not always happen. For me it happens in the admin/build/modules but not all the times
I have the feeling that jquery waits for the page to load fully before it starts attaching the fold/unfold code
I think the page never gets fully loaded (or at least FF thinks its not) and jquery never gets called.
The reason I believe this is happening is:
There are times that the fold/unfold triangles have not shown but when I click on a link to go to another page (for that split second before leaving the page) the triangles DO SHOW UP. (it could be that when I hit the link, firefox thinks it time to at least declare the previous page as loaded)
In conclusion I feel its more of a Firefox bug.
Comment #3
mike stewart commentedI encountered this problem during an upgrade from 4.7 to 5.1. I am using firefox 1.5.0.9 (due to a really cool plugin that was never updated to FF 2.x)
with only core modules, DHTML menu's worked fine (using garland theme). at some point during the process of upgrading contributed modules they quit working. As i recall, I beleive I had forgotten to run the upgrade script for the workflow module. (I was doing about 10 things at once, so Im not positive). however, I am sure that during the process I eventually clicked on the (much improved) administration menu - which brought to my attention some sort of versioning error and suggested I needed to run the update.php script.
after running the update for the culprit module, my DHTML menu's in firefox are now again working properly. hope this works for you. (but I bet its unlikely to be a magic bullet)
Comment #4
Roi Danton commentedFor me it doesn't work in Opera either with jQuery 1.1.1
All collapseable elements have that problem. I've encountered the problem with a fresh Drupal 5.1 install:
create content -> page, story
admin -> modules
etc
Comment #5
Roi Danton commented-> sorry, muddled the title ... that behaviour I encountered (collapsible elements doesn't collapse after expanding) is wanted and is not a bug (and hasn't to do with the problem of the lack of $(document).ready() in FF). Sorry for the wrong follow up above!
Btw, an upgrade to jQuery 1.1.1 helped on this topic. See this, too: http://drupal.org/node/118846
Comment #6
mr700 commentedDoes the patch from node 110935 comment 195854 fix this (can someone who experiences this check)?
Comment #7
drummPlease reopen if this happens with Drupal 5.x from CVS. I believe this issue was fixed, but I can't find the other issues.
Comment #8
goye2cz commentedJust to confirm, i know this thread is quite old but I had the same original described issue. I am testing 5.x due to panels not quite being ready for 6.x (afaik) I noticed firebug complaining about some problem with lightbox so I disabled the lightbox module. It works perfectly now. Just in case someone else experiences this, they can see what helped me.
Comment #9
giorgosk@goye2cz
perhaps an issue in the issue queue of the module that you disabled would be most appropriate for other users to take notice