For some reason mozilla cannot display this site: www.slickedit.com. All I see in the browser is a graphic on the left side which appears to corresond to only one part of the frame set.
Confirmed. Making test case.
The above testcase is a simplified version of the frameset in question. I think I could have simplified it more, but I'm not sure at what point it stops being valid syntax. This case shows 3 frames, 3 picture in Netscape. Only the first frame/picture is displayed in Mozilla.
Sorry for spam. Forgot to reset Keyword.
Funny, I specifically fixed this type of page not too long ago: <FRAMESET cols="147,0*" rows="*"> This means "A column of 147 pixels followed by a frame of 0 pixels.", according to HTML 4.0 Section 6.6 states: 3. MultiLength: The value ( %MultiLength; in the DTD) may be a %Length; or a relative length. A relative length has the form "i*", where "i" is an integer. When allotting space among elements competing for that space, user agents allot pixel and percentage lengths first, then divide up remaining available space among relative lengths. Each relative length receives a portion of the available space that is proportional to the integer preceding the "*". The value "*" is equivalent to "1*". Thus, if 60 pixels of space are available after the user agent allots pixel and percentage space, and the competing relative lengths are 1*, 2*, and 3*, the 1* will be alloted 10 pixels, the 2* will be alloted 20 pixels, and the 3* will be alloted 30 pixels. I can fix this to be backwards compatible in quirks mode, but the page should probably be changed to: <FRAMESET cols="147,*" rows="*"> To achieve the desired effect in standards compliant browsers.
Nav and IE treat 0* as 1*. I have a fix in my tree that makes this so iff we are in quirks mode.
*** Bug 43921 has been marked as a duplicate of this bug. ***
(updating mutiple bugs) Nominating this bug for beta3 because it is either a crasher or a correctness bug and I have a straightforward fix in hand. This bug fix is small, low risk, and can easily be reverted with no side effects.
This fix has been checked in. Coming up with a test case to assist in verification...
Marking verified in the Aug 24th build.