Closed Bug 2471 Opened 26 years ago Closed 25 years ago

{vmargin} list reflow issue with P's and collapsed margins

Categories

(Core :: Layout, defect, P2)

Product:
Core
Component:
Layout
Platform:
x86
Windows NT
Type:
defect

Tracking

()

Status:
VERIFIED INVALID

People

(Reporter: michael.j.lowe, Assigned: buster)

Details

Following html parses incorrectly: <HTML> <BODY> <OL> <LI>Point 1<P> A<P> <LI>Point 2<P> B<P> <LI>Point 3<P> C<P> </OL> </BODY> </HTML>
Status: NEW → ASSIGNED
Assignee: rickg → kipp
Status: ASSIGNED → NEW
Kipp -- the layout of this is odd, but the content model is well formed.
Status: NEW → ASSIGNED
Setting all current Open/Normal to M4.
per leger, assigning QA contacts to all open bugs without QA contacts according to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser
Component: Parser → Layout
Summary: Parsing lists → list reflow issue with P's and collapsed margins
Severity: normal → critical
Summary: list reflow issue with P's and collapsed margins → {vmargin} list reflow issue with P's and collapsed margins
Another example of a collapsing bug (with the latest code; with yesterdays code, a margin was getting discarded)
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Fixed. The page now reflows properly.
Status: RESOLVED → REOPENED
In the June 18th Builds (Win32, Mac, Linux), the layout problem still exists. The second P element is not recognized. Below is a illustration of the list's layout. Gecko: (Only the first paragraph element is supported) 1.Point 1 <lf> A 2.Point 2 <lf> B 3.Point 3 <lf> C I.E. 5.0 and Comm 4.6:(Both P elements are supported.) 1.Point 1 <lf> A <lf> 2.Point 2 <lf> B <lf> 3.Point 3 <lf> C <lf> Amaga: (W3C Browser - Only the second paragraph element is supported) 1.Point 1 A <lf> 2.Point 2 B <lf> 3.Point 3 C <lf>
Resolution: FIXED → ---
Target Milestone: M6 → M7
This was a critical M6 fix which has been reopened on June 18 M7 candidate build. Setting to M7 milestone to review for action. Fix in M7? Or move on to M8?
Status: REOPENED → RESOLVED
Closed: 26 years ago → 25 years ago
Resolution: --- → INVALID
NGLayout is rendering this correctly at the moment. Per HTML4, empty <P> elements should be ignored. Marking bug invalid.
Status: RESOLVED → VERIFIED
Verified: 1999-06-18-09-M7 Quote from spec: "We discourage authors from using empty P elements. User agents should ignore empty P elements."
You need to log in before you can comment on or make changes to this bug.