Closed
Bug 14030
Opened 25 years ago
Closed 25 years ago
<P></P> should not be ignored in NavQuirks mode {ll}
Categories
(Core :: Layout, defect, P3)
Tracking
()
M17
People
(Reporter: nisheeth_mozilla, Assigned: nisheeth_mozilla)
References
()
Details
(Keywords: testcase, Whiteboard: (py8ieh: search for other examples and evangelise, if the decision is changed))
HTML like "Line One <P></P> Line Two" causes 2 line breaks on
navigator but only 1 in raptor. This was causing the news headslines in the
right most column of the ESPN page to squich together vertically.
Updated•25 years ago
|
URL: www.espn.com → http://www.espn.com
Comment 1•25 years ago
|
||
This likely has something to do with special P-element-specific code that kipp
wrote based on comments in the HTML spec. I tend to think those comments
weren't intended quite as written, but just to require CSS-style
margin-collapsing.
Updated•25 years ago
|
Whiteboard: [TESTCASE]
Comment 3•25 years ago
|
||
This is a testcase from bug 14161:
http://bugzilla.mozilla.org/showattachment.cgi?attach_id=1729
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M16
Assignee | ||
Comment 4•25 years ago
|
||
Accepting bug and setting milestone to M16...
Comment 6•25 years ago
|
||
Comment 7•25 years ago
|
||
Bulk moving [testcase] code to new testcase keyword. Sorry for the spam!
Keywords: testcase
Comment 9•25 years ago
|
||
According to a strict reading of the specs, <p></p> should be ignored, which
means that in fact we should not even be causing a line break there.
Summary: <P></P> causes two line breaks on navigator, but only 1 on raptor → <P></P> should not be ignored in NavQuirks mode {ll} {compat}
Comment 10•25 years ago
|
||
I don't think the HTML spec needs to be read that strictly... and anyway, I
*think* it says "should", not "must".
Comment 11•25 years ago
|
||
That's what I said! "should"! :-)
It says: "We discourage authors from using empty P elements. User agents should
ignore empty P elements." (end of section 9.3.1)
Just out of interest, are there any other sites that use this kind of markup?
(...and could someone list them? I may wish to evangelise.)
Also, what exactly is the behaviour we want? We can't just use CSS rules,
otherwise CSS starts bordering empty P paragraphs, and such like. And if an
author uses padding instead of margins on <P> elements, then all kinds of
weird things start happening, none of which look like us ignoring paragraphs.
Whiteboard: [TESTCASE]
Comment 12•25 years ago
|
||
Incidentally, the fix for this should be "simply" to bypass Kipp's "ignore
empty P elements" code if the empty <P> element is flanked on both sides by
inline elements or anonymous inline boxes (i.e., raw text). In quirks mode
only, of course.
Whiteboard: (py8ieh: search for other examples and evangelise)
Comment 13•25 years ago
|
||
*** Bug 21631 has been marked as a duplicate of this bug. ***
Comment 15•25 years ago
|
||
I'm not even sure this should be quirks mode only. See the thread on www-html
beginning with http://lists.w3.org/Archives/Public/www-html/2000Apr/0024.html .
Comment 16•25 years ago
|
||
Since the rules changed, this is now a dup of 35768.
*** This bug has been marked as a duplicate of 35768 ***
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Summary: <P></P> should not be ignored in NavQuirks mode {ll} {compat} → <P></P> should not be ignored in NavQuirks mode {ll}
Whiteboard: (py8ieh: search for other examples and evangelise) → (py8ieh: search for other examples and evangelise, if the decision is changed)
Comment 17•25 years ago
|
||
Ian, I think you missed the right bug on the DUPL. bug #35768 is about applying
style for :lang elements, no?
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Comment 18•25 years ago
|
||
Err, not bug 35768, sorry. I meant bug 35772.
*** This bug has been marked as a duplicate of 35772 ***
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → DUPLICATE
Comment 20•24 years ago
|
||
*** Bug 49327 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
•