Closed Bug 49327 Opened 24 years ago Closed 24 years ago

Paragraph tags not being handled properly

Categories

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

x86
Linux
defect

Tracking

()

VERIFIED INVALID

People

(Reporter: sterno, Assigned: rickg)

References

()

Details

(Whiteboard: [Strict DTD Invalid Page])

I've notice that if you use a closing paragraph tag, it apparently breaks the
HTML rendering, leading to pargraphs running together.  So:

blah blah
<P>
blah blah

seperates properly but:

<P>
blah blah
</P>
<P>
blah blah
</P>

does not even though, as I understand it, it is more correct.
dup of bug 35772? (by way of bug 14030)
Brief explanation by Sean Richardson also found in bug 37349 (another dup)

*** This bug has been marked as a duplicate of 14030 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Those bugs are about empty paragraphs.  They were also fixed well before this
was reported.  Reopening.  What, exactly, is the problem here?
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
No, this is a strict DTD issue.  It is an invalid page messed up by the strict
DTD.
Assignee: clayton → rickg
Status: UNCONFIRMED → NEW
Component: HTML Element → Parser
Ever confirmed: true
QA Contact: petersen → janc
Whiteboard: [Strict DTD Invalid Page]
According to the W3C for HTML 4 closing tags of a paragraph are optional so it
shouldn't be considered invalid by the strict DTD.  
As David mentioned, the page is invalid ( not talking about Pragraph tags ), and
therefore, is getting messed up in Strict DTD.

Sterno, if you remove the DOCTYPE the problem will go away.

Note: I removed the </P> from your document, to verify if your claim was true,
and that did not fix the problem!
Sorry, didn't understand what you were saying about the strict DTD.  I have
since gotten to work just fine with the loose DTD.  Thanks!
Status: NEW → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → INVALID
verified
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.