102861 - JavaScript does not function correctly - fails to expand tree

Status: RESOLVED WORKSFORME

(Core :: Layout: Images, Video, and HTML Frames, defect)

Description

[phil]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20010913
BuildID:    2001091303

Instead of expanding a javascript-implemented tree, Mozilla opens a new window.

Reproducible: Always
Steps to Reproduce:
1. Go to www.college-sport.org.nz
2. Click through the first page.  Wait for the frameset to load.
3. Try and click on a "+" to expand the tree in the left frame.  Mozilla will
open a new window.  IE correctly expands the tree.

Actual Results:  Mozilla opened a new blank window.  Nothing in the URL.

Expected Results:  IE expands the javascript navigation tree.

Comment 1

[Boris Zbarsky [:bzbarsky]]

Looks like top.foo() is not working.... shouldn't 'top' return the toplevel
frameset and then foo() call the function defined therein?

Comment 2

[Phil Schwartau]

If I do View | Frame Source on the "treeFrame", I see different HTML source
in Mozilla vs. NN4.7. The HTML in NN4.7 includes <IMG> and <A> elements,
but in Mozilla there are only <IMG> elements, no <A>'s ...

Since the <A> elements contain the HREF's, this would explain the behavior
reported above. 

Will attach this comparison below - 

Comment 3

[Phil Schwartau]

Attachment: "treeFrame" HTML source in NN4.7 vs. Mozilla

Comment 4

[Phil Schwartau]

That can't be it - in Mozilla you can clearly see the HREF's when
you mouseover the tree. Must be a bug in View | Frame Source.

Comment 5

[Phil Schwartau]

TRY THIS:

1. Go to www.college-sport.org.nz
2. Click through the first page.  Wait for the frameset to load.
3. Key this in URL bar --->  javascript: top.toggleFolder('sports',1)
4. Mozilla will correctly expand the tree.

This shows that we're not having any problem binding the 
top.toggleFolder function...

Comment 6

[Phil Schwartau]

Summarizing: 

1. Load http://www.college-sport.org.nz/frameset.htm
2. Mouseover the '+' image for "Sports Code Info"
3. You will see in the status bar ---> javascript: top.toggleFolder('sports',1)
4. If you enter that in the URL bar, the tree expands (use 0 to contract)
5. But if you click on the '+' sign, you get this error in the debug console:
                  JavaScript error: 
                  line 0:
                  top.toggleFolder is not a function
6. No errors appear in the JavaScript Console
7. A new child window opens up with nothing in it: completely blank

Comment 7

[Phil Schwartau]

I don't think this is a problem in JS Engine. For some reason, the
left frame can't resolve top.toggleFolder, whereas the URL bar can.

Reassigning to HTMLFrames for further triage -

Comment 8

[Phil Schwartau]

I don't suppose this is a consequence of bug 101746,
"frames array has frames in incorrect order" ? 

Assigning to hyatt just in case; cc'ing jrgm -

Comment 9

[Phil Schwartau]

OK, to see the true source of the "treeFrame" in Mozilla, 

1. Load http://www.college-sport.org.nz/frameset.htm
2. Enter this in the URL bar:
   javascript: alert(window.treeFrame.document.documentElement.innerHTML);

3. When this comes up, look carefully for the "Sports Code Info" anchor.
4. The HTML looks OK to me ...

Comment 10

[John Morrison]

I have a simple test case for this. The problem arises this way:

1) the left hand frame loads an initial document that declares
   "<BASE TARGET='Body'>"
2) when the left and right frames have loaded, the top document (the frameset)
   overwrites the original document in the left hand frame with a JS generated
   document. 

It seems that something about that initial document, with the <BASE TARGET>
is not cleared, and that confuses things. If I modify the initial document to 
be identical except for that <BASE TARGET>, then everything works fine.

The simple test case is (inside the firewall)
   http://jrgm/bugs/102861/page.html

I'll attach a tar.gz of the files, for outside the firewall.

-> jst, DOM-fu

Comment 11

[John Morrison]

Attachment: testcase; frameset document, plus three frame documents (.tar.gz)

Comment 12

[Boris Zbarsky [:bzbarsky]]

Site no longer seems to have a JS navigation tree and the attached testcase
worksforme (both frames act identically).

Marking worksforme, but please reopen if the problem is still present (and
please list steps to reproduce if so).