Closed
Bug 44584
Opened 25 years ago
Closed 24 years ago
Incorrect closing of paragraph when combined with <strong>
Categories
(Core :: DOM: HTML Parser, defect, P3)
Tracking
()
VERIFIED
FIXED
Future
People
(Reporter: jesup, Assigned: rickg)
References
()
Details
(Keywords: testcase, Whiteboard: fix in hand)
Attachments
(1 file)
1.29 KB,
text/html
|
Details |
The example included lays out incorrectly - the <p align=center> ends up causing
all the subsequent left items to be sort-of centered. If the (unclosed)
<strong> is removed from the first paragraph, it lays out correctly. Note that
most of the list items have the marker far away from the paragraph as well -
removing the <strong> and </strong> from the list items (as in the first) causes
the markers to be with the text (though still incorrectly centered).
I found this looking around at www.negril.com and cut down an example.
Reporter | ||
Comment 1•25 years ago
|
||
Moving to Parser/harishd. This looks like either a simple parser
problem or a residual style problem.
Assignee: clayton → harishd
Status: UNCONFIRMED → NEW
Component: HTML Element → Parser
Ever confirmed: true
Not a high priority bug. FUTURing it. Please let me know your concerns.
Status: NEW → ASSIGNED
Target Milestone: --- → Future
Reporter | ||
Updated•24 years ago
|
Keywords: correctness
Assigning to myself; I have a patch for this.
Assignee: harishd → rickg
Status: ASSIGNED → NEW
Two things needed to happen. First, phrasals are NOT flowentities (correct this
in the elementTable). Then in handleDefStartToken(), add this patch:
@@ -1093,8 +989,8 @@
eProcessRule theRule=eNormalOp;
if((!theParentContains) &&
- (nsHTMLElement::IsResidualStyleTag(theParentTag)) &&
- (IsBlockElement(aChildTag,theParentTag))) {
+ (IsBlockElement(aChildTag,theParentTag)) &&
+ IsInlineElement(theParentTag,theParentTag)) { //this fixes 44584
Reporter | ||
Comment 7•24 years ago
|
||
Change langed. I'll look into the other bugs cited at the end (for possible
dups) momentarily.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•