Closed
Bug 7647
Opened 25 years ago
Closed 25 years ago
frames not reflected as frameset properties
Categories
(Core :: DOM: Core & HTML, defect, P3)
Tracking
()
M7
People
(Reporter: martin.honnen, Assigned: vidur)
Details
With both existing ns and ms browsers the following doc <HTML> <HEAD> </HEAD> <FRAMESET ROWS="50%, 50%"> <FRAME NAME="frame0" SRC="nn5FrameReflection1.html"> <FRAME NAME="frame1" SRC="nn5FrameReflection1.html"> </FRAMESET> </HTML> causes the frames to be reflected as properties of the frameset window top.frameName e.g top.frame0 top.frame1 Mozilla m6 displays undefineds for the following <HTML> <HEAD> <SCRIPT> function testFrames() { for (var i = 0; i < frames.length; i++) alert(window[frames[i].name]); } </SCRIPT> </HEAD> <FRAMESET ROWS="50%, 50%" ONLOAD="testFrames()"> <FRAME NAME="frame0" SRC="nn5FrameReflection1.html"> <FRAME NAME="frame1" SRC="nn5FrameReflection1.html"> </FRAMESET> </HTML> That breaks a lot of DOM level 0 (which features list shows as 100% done) code I think.
Assignee | ||
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Comment 1•25 years ago
|
||
A known problem. Tom, you should probably move this higher up on your bug list since it has so many DUPs. *** This bug has been marked as a duplicate of 1839 ***
Updated•25 years ago
|
Status: RESOLVED → CLOSED
You need to log in
before you can comment on or make changes to this bug.
Description
•