Closed
Bug 16963
Opened 25 years ago
Closed 23 years ago
missing JS handled pop-down menus
Categories
(Core :: DOM: HTML Parser, defect, P3)
Tracking
()
VERIFIED
WONTFIX
mozilla0.9.1
People
(Reporter: gemma, Assigned: harishd)
References
()
Details
Attachments
(1 file)
1.29 KB,
text/html
|
Details |
With Communicator, rolling over the menu at the top will have the sub-menu pops down, but M10 doesn't handle that
Updated•25 years ago
|
Assignee: mccabe → trudelle
Component: Javascript Engine → XP Toolkit/Widgets
Comment 1•25 years ago
|
||
Guessing XP Toolkit. Any clues there?
Updated•25 years ago
|
Assignee: trudelle → rickg
Component: XP Toolkit/Widgets → HTML Form Controls
Comment 2•25 years ago
|
||
Those menus are all part of the HTML content, using CSS absolute positioning, nothing to do with XPToolkit. reassigning to rickg for triage.
Peter, why isn't this javascript response in XUL? CSS involves style/layout, but not event response.
Updated•25 years ago
|
Assignee: trudelle → hyatt
Comment 4•25 years ago
|
||
I guess I don't understand how this involves XPToolkit, even if the reponse should be done using XUL. reassigning to hyatt for triage.
Updated•25 years ago
|
Assignee: hyatt → rickg
Comment 5•25 years ago
|
||
This is referring to HTML-implemented "popup menus". XUL has nothing to do with this.
Comment 7•25 years ago
|
||
changed to M14
Updated•25 years ago
|
Component: HTML Form Controls → Javascript Engine
Comment 12•24 years ago
|
||
I need to take a closer look at this. Marking M16 for now until I know more
Target Milestone: M18 → M16
Comment 13•24 years ago
|
||
If you run mozilla with the console open, you'll get the following error when you mouse over one of the top images (ie "products", "solutions", etc): JavaScript error: http://www.sgi.com/ line 102: menus[menunumber] has no properties
Comment 14•24 years ago
|
||
Comment 15•24 years ago
|
||
Here is what is going on: <STYLE TYPE='text/css'> #menu5 {position: absolute; left: 533px; top: 24px; z-index: 106; visibility: hidden; width: 77px;} </STYLE> ... <div id=menu5> ... </div> When you apply style that includes positioning to a div tag in 4.x it turns it into a "layer" object. You refer to it directly by id (for example window.dicument.menu5) Then you can set the visibility directly on the object like: window.document.menu5.visibility = 'hidden'; This all works. When this very example is run in Mozilla, it can't find the element using the window.document.menu5 because the id is "menu5" not the name. Then, even if you found the object using getElementById, setting the visibility directly on the obj doesn't work. In the attached example their is a boolean "doNav" which lets you test it for Nav using nav code, or you can set it to false to try it out in Mozilla with standard DOM attrs. This is a backward compatibility issue. reassigning, I'll with you jst.
Comment 16•24 years ago
|
||
M16 has been out for a while now, these bugs target milestones need to be updated.
Comment 17•24 years ago
|
||
There are numerous severe problems on the SGI page, both HTML problems and DOM problems. The worst problem is that the markup for the popups is *after* the html end tag (</HTML>) in the file and because of that the elements that make up the popup menus don't end up in the document. As for the DOM problems, the site needs to be changed to not rely on non-standard 4.x DOM extensions, for instance the line: window.document.menu5.visibility = 'hidden'; should be: window.document.getElementById("menu5").style.visibility = 'hidden'; when loaded in mozilla (that needs to be detected properly). Since mozilla doesn't support the 4.x "layer" in any way I think this should be marked WONTFIX, but I'll reassign to the parser people so that they can decide what to do (if anything at all) about the data after the </HTML> tag not showing up in the document, harishd?
Assignee: jst → harishd
Assignee | ||
Comment 18•24 years ago
|
||
Not a high priority. Moving to the FURTURE list.
Status: NEW → ASSIGNED
Target Milestone: M16 → Future
Comment 19•24 years ago
|
||
Removed nsbeta3 nomination from futured bugs.
Comment 20•24 years ago
|
||
Not JS Engine; updating component to Parser -
Component: Javascript Engine → Parser
Assignee | ||
Comment 21•23 years ago
|
||
Parser ignores /HTML, from the document, no matter where it appears. That is, markup after /HTML, in a document, will get parsed as though it appeared before /HTML.
Assignee | ||
Comment 22•23 years ago
|
||
LAYERS == WONTFIX
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
Comment 24•23 years ago
|
||
Marking verified as per above developer comments.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•