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)

[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.

[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.]

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.

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. :+)

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.

Marking Invalid verfied.

*** Bug 107476 has been marked as a duplicate of this bug. ***