Closed Bug 100048 Opened 24 years ago Closed 22 years ago

toshiba.no - JavaScript menus look all wrong

Categories

(Tech Evangelism Graveyard :: Norwegian, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: toralf, Unassigned)

References

()

Details

(Whiteboard: [LAYER][PROPRIETARY-DOM])

Attachments

(1 file)

The JavaScript menus on http://www.toshiba.no/ look all messed up; refer to screenshot which will be attached shortly. This is true for the front page as well as menus elsewhere on the site, with have different layout but (presumably) a similar menu engine. This problem may well be related to other reports about layers in menus, but I'm submitting separately as these belong to different components (i.e. regions). The existence of layer handling code is also what makes me think that the error is with the web site, not the browser...
Attached image Screen-shot of web page
Component: European → West Europe
QA Contact: momoi → caillon
The page definitely uses layers. However, it will conditionally try to use <div> instead; the JavaScript code is full of constructs like if(document.all) document.write('</div>') else document.write('</layer>') Perhaps all that is needed is to modify the tests so that they evaluate to true on Mozilla?
Summary: JavaScript menus look all wrong on Toshiba Scandiavia → if(document.all) document.write('</div>')toshiba.no - JavaScript menus look all wrong
Summary: if(document.all) document.write('</div>')toshiba.no - JavaScript menus look all wrong → toshiba.no - JavaScript menus look all wrong
http://www.toshiba.no/navet000203/main.html is the frame with the menus. All the code is based on if (document.all) {} else if (document.layers) {} document.layers is MSIE specific which we don't support and document.layers is NS4 specific which we don't support either. They need to upgrade to DOM compliance. Confirming bug on linux trunk 2001091721.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: PC → All
Whiteboard: [LAYER][PROPRIETARY-DOM]
I'm assuming what you meant to say was that document.all (not document.layers) MSIE specific. Based on that, it seems to me that what their doing most of the time is really if(<browser is MSIE>) { <add standard HTML> } else { <add Netscape Proprietary HTML> } which is rather dumb if you ask me (obviously, the standard stuff should generally go in the "else" branch of browser tests.) It looks like there are some truely MS specific bits as well, though...
their code uses MSIE specific (document.all which is what i meant to say above) and NS4 specific (document.layers). both are outdated. the point is there is no standard stuff in their code. only MSIE and NS4 specific.
Well, they do in fact add <div> (that's a standard tag, right?) rather than <layer) (which certainly isn't) if they think the browser is MSIE. I guess that doesn't help a lot, though, as long as other parts of the code will handle browser specific objects only.
Confirming on N62/Win2K. Accepting bug Setting P3.
Status: NEW → ASSIGNED
Priority: -- → P3
Blocks: 113492
No longer blocks: 113492
move..
Component: Europe: West → Norwegian
norwegian default owner
Assignee: nitot → norwegian
Status: ASSIGNED → NEW
QA Contact: z-caillon-obsolete2 → norwegian
The site seems to work now.. I think they redesigned it. I looked through the code and surfed around the site a bit, and it seems to work OK now. It doesn't display as well as it should, but it's useable.
Yup, redesigned. WFM.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: