Closed
Bug 161691
Opened 22 years ago
Closed 22 years ago
Almost-standards mode doesn't use quirks layout in all cases
Categories
(Core :: CSS Parsing and Computation, defect, P2)
Core
CSS Parsing and Computation
Tracking
()
VERIFIED
FIXED
mozilla1.2alpha
People
(Reporter: emeyer, Assigned: dbaron)
References
()
Details
(Keywords: testcase, topembed+, Whiteboard: [patch] [adt2])
Attachments
(1 file, 2 obsolete files)
2.34 KB,
patch
|
caillon
:
review+
bzbarsky
:
superreview+
jesup
:
approval+
|
Details | Diff | Splinter Review |
The "almost standards" mode (see bug 153032) is failing in cases where table cells have multiple <br>-separated images. In quirks mode, the layout is the same as NN4.x and IE/*. In strict mode, the images spread apart, as expected. In almost standards mode, the images spread apart, which is not expected. This is demonstrated in the following three testcases (they're all linked to each other): http://www.meyerweb.com/eric/css/tests/almost-standards.html http://www.meyerweb.com/eric/css/tests/almost-standards-quirk.html http://www.meyerweb.com/eric/css/tests/almost-standards-strict.html In quirks mode, the <br> elements seem to overcome the whitespace separating the images and thus smash the images together, which is the classic "images have to be followed by a <br> element to close up space" behavior, circa 1996. This isn't carried forward to "almost standards." The expected result, from an author's point of view, is that the layout of the almost-standards page and the quirks page (above) would be the same.
Assignee | ||
Comment 1•22 years ago
|
||
The quirky BR behavior that is part of the quirks mode inline box model was still keying off the modes so that it was doing the standards mode behavior in AlmostStandards mode. This patch changes it so that the quirky BR behavior is also quirky in AlmostStandards mode, which I agree is the right thing to do.
Assignee | ||
Updated•22 years ago
|
Status: NEW → ASSIGNED
Priority: -- → P2
Whiteboard: [patch]
Target Milestone: --- → mozilla1.2alpha
Reporter | ||
Comment 4•22 years ago
|
||
Marking topembed, although with the amazingly speedy patching I almost feel like it isn't necessary. You rock, David!
Keywords: topembed
Comment 5•22 years ago
|
||
Comment on attachment 94470 [details] [diff] [review] patch sr=bzbarsky
Attachment #94470 -
Flags: superreview+
Comment 6•22 years ago
|
||
Comment on attachment 94470 [details] [diff] [review] patch r=caillon
Attachment #94470 -
Flags: review+
Assignee | ||
Comment 7•22 years ago
|
||
Fix checked in to trunk, 2002-08-11 11:00 PDT.
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 8•22 years ago
|
||
Verifying fix in 2002081208-trunk. Great work!
Status: RESOLVED → VERIFIED
Comment 9•22 years ago
|
||
From email from Evangelist, this sounds like "a simple fix, self-contained", that would prevent sites to be broken in the future, by not "further fragment the DOCTYPE switching space." This has baked for 3 weeks, with no known regressions on the trunk. Adding edt1.0.2 and Mozilla1.0.2 keywords to nominate for 1.0 branch landing.
Whiteboard: [patch] → [patch] [adt2]
Comment 10•22 years ago
|
||
Comment on attachment 94470 [details] [diff] [review] patch a=rjesup@wgate.com for 1.0 branch. You know the drill. Check in asap if you want to make 1.0.2
Attachment #94470 -
Flags: approval+
Updated•22 years ago
|
Keywords: mozilla1.0.2 → mozilla1.0.2+
Assignee | ||
Comment 11•22 years ago
|
||
Fix checked in to MOZILLA_1_0_BRANCH, 2002-09-11 13:14 PDT.
Keywords: mozilla1.0.2+ → fixed1.0.2
Comment 12•22 years ago
|
||
Jaime please + the topembed
Comment 13•22 years ago
|
||
Please verify the bug. Once verified, change the keyword fixed1.0.2 to verified1.0.2
Comment 14•22 years ago
|
||
susie: i could plus it, but it appears to already be checked in on the trunk and 1.0 branch. i will give it a posthumus edt1.0.2+ and topembed+ for you. ian, as assigned QA Contact, can you pls verify this as fixed on the 1.0 branch? Once verified, change the keyword "fixed1.0.2" to "verified1.0.2."
Comment 15•22 years ago
|
||
I don't have a branch build and do not have the time to concentrate on anything apart from the trunk, sorry.
Comment 16•22 years ago
|
||
Thanks for the feedback Ian. Bob/Susie: Is this something the evangelist can verify?
Comment 17•22 years ago
|
||
verified fixed on branch : checked on -- win2000 ----- 2002-10-03-08-1.0 build -- linux 7.2 --- 2002-10-03-07-1.0 build changing KW from fixed1.0.2 to verified1.0.2
Keywords: fixed1.0.2 → verified1.0.2
You need to log in
before you can comment on or make changes to this bug.
Description
•