183494 - Javascript controlled frame with menu loads blank

Status: RESOLVED WORKSFORME

(Core :: DOM: Core & HTML, defect)

Description

[Matt Foster]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2.1) Gecko/20021130

In the page at http://isl715.nws.noaa.gov/tdl/icwf/user_guide_ifps11/ the left
frame should load a Javascript menu, but it comes up blank.  The initial loading
of the page does not trigger any JavaScript errors, but reloading the page
triggers this error:

Error: uncaught exception: Permission denied to get property Window.name

When I load the page with NS4.x the left frame first comes up with "No
JavaScript?" at the top, and after a few second delay then loads the menu properly.

I'll initially put this to DOM Level 0, but I wouldn't be too surprised if it's
actually a Tech Evangelism issue.  I'm not real swift a diagnosing this sort of
problem.  :-(


Reproducible: Always

Steps to Reproduce:
1. Direct browser to given URL.

Actual Results:  
Left frame is blank.


Expected Results:  
Left frame should have a menu.

Comment 1

[R.K.Aa.]

mozilla doesn't see that the left frame is a frame at all..
right-click in it: The context menu contains no frame related items

Comment 2

[Olivier Cahagne]

may come from JavaScript from top frame:
http://isl715.nws.noaa.gov/tdl/icwf/user_guide_ifps11/mtmcode.js

Code seems to be old and may not handle Mozilla properly.

Comment 3

[Matt Foster]

I believe Oliver is correct.  I'm not very familiar with JavaScript, but I see
references in mtmcode.js to document.layers and document.all, which I believe
are proprietary.  Should we go ahead and send this over to Tech Evangelism?

Comment 4

[Johnny Stenback (:jst)]

Mass-reassigning bugs to [e-mail]

Comment 5

[José Jeria]

This bug seems to be outdated, reading the comments, it seems to have been a
envagelism bug. Also now the url doesnt even work. Can anyone verify and close
this bug?

Comment 6

[Fabian Guisset]

Without a testcase we can't do anything about this bug. Marking WORKSFORME,
please reopen if someone can find a testcase for the problem, thanks!