Closed
Bug 5013
Opened 26 years ago
Closed 25 years ago
{compat} Spacing/Layout flaw - no space proceeds <LI>
Categories
(Core :: Layout, defect, P3)
Tracking
()
VERIFIED
INVALID
People
(Reporter: Crysgem, Assigned: buster)
References
()
Details
Attachments
(1 file)
(deleted),
text/html
|
Details |
The beast appears to disfavor the <P> tag currently... producing a page that is
considerably "scrunched" in it's vertical presentation of text. Where a newline
should appear between bodies of text, there is now none.
(Mozilla.org Nightly build, April 12)
Assignee: rickg → troy
Component: Viewer App → Layout
QA Contact: 3853 → 4144
Updated•26 years ago
|
Whiteboard: (py8ieh:will update summary)
Target Milestone: M15
Comment 1•26 years ago
|
||
[dbaron: removing M15 marker to get this back onto our radar.]
Perhaps the same flaw results in Slashdot's current (Apprunner Build ID
1999060708)... "compressed" rendering.
*Squirming in awareness of greater presence* DBaron regarding MY mere report? I
am honored. Perhaps I can alarm a coder or several into long-overdue action
(having reached M6, the very cusp of M7, with a **<P>** bug?) by daringly
Dopplerizing to M8.
Updated•25 years ago
|
Target Milestone: M8
Comment 3•25 years ago
|
||
[Re-removing milestone. Kipp (to whom this bug has been assigned) is currently
on sabbatical, and dbaron and I (py8ieh) have been assigned to examine bugs on
Kipp's buglist until he returns. Bugs on Kipp's list are being marked M15 once
dbaron or I ascertain that they really are bugs, and are not duplicates or
invalids. Bugs that have not yet been examined have their milestone field set
to nothing. This bug has not yet been examined. If this bug is deemed important,
then when it is examined it may be passed on to another engineer.]
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Whiteboard: (py8ieh:will update summary)
Comment 4•25 years ago
|
||
I do not see any spacing/layout flaws on http://www.reston.com/nasa/watch.html
with the 19990614 build. Note also that this page has a gazillion errors in the
markup. Pass it through the validator to http://validator.w3.org/ to see what
I mean. If you the bug is still there but I could not see it, please reopen
the bug. Thanks.
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 5•25 years ago
|
||
With the June 19th Build (1999061908), paragraph spacing is correct.
I, too, view through the 1999061908 Apprunner's presentation. But now this
report may chronicle a new spacing issue at the same page. Seemingly the beast
will not insert white space before a <LI> that is sans a progenitor <OL> tag
(unlike Enforcer 5.0)... Now, at this, py8ieh=bugzilla@bath.ac.uk may mark the
archive invalid if the specification is risked. :+)
Resolution: WORKSFORME → ---
Summary: Spacing/Layout flaw → [4.xP] Spacing/Layout flaw - no space proceeds <LI>
Updated•25 years ago
|
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → INVALID
Summary: [4.xP] Spacing/Layout flaw - no space proceeds <LI> → {compat} Spacing/Layout flaw - no space proceeds <LI>
Comment 8•25 years ago
|
||
The <P>s in question are empty <P> elements and are thus correctly ignored by
Mozilla, as per the HTML4 specification. IE is incorrect in its rendering.
Marking Invalid.
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 9•25 years ago
|
||
Marking Invalid verfied.
Comment 10•23 years ago
|
||
*** Bug 107476 has been marked as a duplicate of this bug. ***
You need to log in
before you can comment on or make changes to this bug.
Description
•