Closed Bug 52237 Opened 25 years ago Closed 25 years ago

change the value of the attribute rows in frameset doesn't work

Categories

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

x86
Windows 95
defect

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: violaine.lebeaupin, Assigned: pollmann)

Details

I use NN6PR2. I try change the rows value of a frameset but with NN6PR2, no change is visible. However the alert are OK. This program works correcly in IE5. <HTML> <HEAD> <SCRIPT> function init () { alert (window.document.getElementById("FrameSet1").rows); window.document.getElementById("FrameSet1").rows = "150,*"; alert(window.document.getElementById("FrameSet1").rows); } </SCRIPT> </HEAD> <FRAMESET NAME="FrameSet1" rows="20,*" onLoad="init()"> <FRAME NAME="Frame1" SRC="blank.htm"> <FRAME NAME="Frame2" SRC="blank.htm"> </FRAMESET> </HTML>
This appears to works in the Sept 14th build. Reporter please download the latest nightly build and try test again.
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Works For Me: OS: Windows 98 Platform: PC Mozilla Build #: 2000100508
Status: RESOLVED → VERIFIED
I use the built 2000103104 in Windows 98 and these lines don't work correctly : if (_fenetre==window.top.frames["framework"].frames["FrameReference"]) { alert (window.top.frames["framework"].document.getElementById ("FrameSetMain").rows); window.top.frames["framework"].document.getElementById("FrameSetMain").rows = "471,471"; } "framework" is an iframe. The first time, the alert displays "0,*" (it's OK) then nothing. The console displays this error : JavaScript error: line 0: uncaught exception: [Exception... "Unexpected error" code: "- 2147418113" nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)" location: "file:///....js Line: 1059"] the others times, the alert displays "471,471" but in the fact, only one frame is visible. It works correctly with IE5.
Product: Core → Core Graveyard
Component: Layout: HTML Frames → Layout: Images
Product: Core Graveyard → Core
You need to log in before you can comment on or make changes to this bug.