Closed
Bug 21268
Opened 25 years ago
Closed 24 years ago
Re: Small Frames
Categories
(Core :: Layout: Images, Video, and HTML Frames, defect, P3)
Core
Layout: Images, Video, and HTML Frames
Tracking
()
VERIFIED
FIXED
M15
People
(Reporter: st8, Assigned: pollmann)
Details
(Keywords: testcase, Whiteboard: Fix in hand)
Attachments
(1 file)
283 bytes,
text/html
|
Details |
Here is an example of framset being strange, thanks for your time
Updated•25 years ago
|
Assignee: karnaze → pollmann
Comment 2•25 years ago
|
||
Reassigning to Eric.
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M14
Assignee | ||
Comment 3•25 years ago
|
||
This ia a carryover of Nav's logic. We're sizing a cols="0%,100%" frameset document to the give a width to the left column. Some code of interest is in nsHTMLFramesetFrame::CalculateRowCol() and nsHTMLFramesetFrame::GenerateRowCol()
Updated•25 years ago
|
Whiteboard: [TESTCASE]
Target Milestone: M14 → M16
Comment 5•25 years ago
|
||
Ugly but not fatal to user experience. Moving to M16.
Comment 6•25 years ago
|
||
Bulk moving [testcase] code to new testcase keyword. Sorry for the spam!
Keywords: testcase
Assignee | ||
Comment 7•24 years ago
|
||
We were doing the bad compatability math in nsFrameSetFrame::ParseRowColSpec. The fix is to change it from: if (i<=0) i=1 or i=100/count; to: if (i<0) i=0; I think it would be safe to fix this even for nav compatability mode, as I doubt any web sites depend on the old behaviour. :) I'll walk the top 100 before checking this in though, of course.
OS: Windows NT → All
Hardware: PC → All
Whiteboard: [TESTCASE] → Fix in hand
Target Milestone: M16 → M15
Assignee | ||
Comment 8•24 years ago
|
||
Fix checked in. To verify, view the attached test case. You should see lycos.com, but none of yahoo.com. Thanks!
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Core → Core Graveyard
Updated•6 years ago
|
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.
Description
•