Closed Bug 8388 Opened 25 years ago Closed 25 years ago

{compat} empty <P> elements used to space <li>s are ignored

Categories

(Core :: DOM: HTML Parser, defect, P3)

Product:
Core
Component:
DOM: HTML Parser
Platform:
x86
Windows 98
Type:
defect

Tracking

()

Status:
VERIFIED INVALID

People

(Reporter: Crysgem, Assigned: buster)

References

(
URL
)

Details

(Whiteboard: current behaviour is per spec) 

Apprunner Build ID: 1999061608

The unordered list on the document's starboard should be centered, and it's
items expansive within a single line... but, as if compressed within a cell or
line-broken, it's text spills.

A parser bug? A layout bug? There are minds greater than this one to determine.
Assignee: rickg → kipp
The only problem I see is that the <UL> on the top/center of the screen is too
closely aligned vertically. The nested <P> should be causing extra whitespace.
Here's the min. test case:

<html><body>
<ul>
  <p><li>item1
  <p><li>item2
  <p><li>item3
</ul>
</BODY></html>
The Apprunner created at 1999061708, rickg@netscape.com, validates your words...
the Parser bugs I report ever seem to heal before you scan them. However, the
GIF data heading the page should be aligned rightmost... aye, Herr Coder, a
seperate bug.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Summary: Unordered list eviscerated → nested table alignment is broken
*** This bug has been marked as a duplicate of 7112 ***
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Er, I mean not to override you, respected checker, but the issue of the bug as
perceived by rickg@netscape.com is *not* resolved. Yes?
Summary: nested table alignment is broken → UL elements not sufficiently spaced
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → INVALID
Summary: UL elements not sufficiently spaced → {compat} empty <P> elements used to space <li>s are ignored
Whiteboard: current behaviour is per spec
Sorry, I only noticed the GIF alignment bug, which is indeed a dup of 7112.

The bug that Rick notes is actually not a bug. Empty <P> elements should be
ignored according to the HTML4 spec, and Mozilla is doing exactly that.

Hence now I'm marking this bug invalid. You are welcome to reopen it, of course,
if you disagree or if there is another problem that I have missed!
Status: RESOLVED → VERIFIED
I've not absorbed the specification, but, on the right of adherence to intent, I
agree. (Assuming you are correct)
You need to log in before you can comment on or make changes to this bug.