Version: Unbekannt (using KDE 3.1.4) Installed from: Gentoo Compiler: gcc version 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r1, propolice) OS: Linux (i686) release 2.4.20-gentoo-r8 When surfing to the website http://www.quirinus-gymnasium.de in the green header below the java applet there is a navigation menu written in JS that works fine Mozilla. When moving with the mouse on one of the menu entries the selected menu expands showing you it's contents. In Konquerer you only see the menu heading but the menu does not expand.
That "javascript" is of the worst kind ;(
I tested it with Konqueror of KDE 3.3.2a and this bug is still present as described.
Can confirm that this renders OK in firefox 1.5 and not in konqueror 3.5.2
Confirmed broken with Konqi 3.5.4, works on FF 1.5, works on opera 9.0. This site uses coolmenus3.js Version 3.02 ( http://www.quirinus-gymnasium.de/coolmenus3.js ) When set oCMenu.useframes=1, the menu doesn't render. When you set it to 0, the menu renders OK if not used in a frame, else it renders on left edge of frame when used in frame. coolmenus3.js seems very hackish, and not well thought out (IMO), but perhaps Konqi can make it work anyway. The issue seems to be rendering the output in a named frame other than the frame the script is called in, e.g. called from frmMenu, should render in frmMain. The script is set up to give debug errors if the frame can't be found, or if the menu isn't rendered, so it seems like the error may be with visibility or layer rendering??? Testcase below. Regards, Mark A. Taff
Created attachment 17542 [details] Frames test case for coolmenus3.js open test.htm
Also, not sure if this should be a site-issue, as I am sure that there are *many* sites that use coolmenus3.js with frames. Regards, Mark A. Taff
Created attachment 24227 [details] testcase new testcase as the old one was referencing some external URL for the script which is no longer present.
Confirmed in 4.5.4 with the testcase of comment 7. Updating version.
Ah, the good-old "browsers don't care about that part of the spec" WRONG_DOCUMENT_ERR thing. *** This bug has been marked as a duplicate of bug 100457 ***