Closed
Bug 172782
Opened 22 years ago
Closed 22 years ago
Regression: Wrong paragraph indentation after nested DL
Categories
(Core :: DOM: HTML Parser, defect)
Core
DOM: HTML Parser
Tracking
()
RESOLVED
FIXED
People
(Reporter: gekacheka, Assigned: harishd)
References
Details
(Keywords: html4, regression)
Attachments
(1 file)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021005 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021005 Regression of bug 55295. Paragraphs inside DD after a nested DL are indented incorrectly (as if at next level out). A following nested DL is indented correctly even after paragraphs. Reproducible: Always Steps to Reproduce: View uploaded test case. Actual Results: Paragraphs inside DD after a nested DL (see bold text in example) are indented one level out from where they should be. Expected Results: Paragraphs inside DD after a nested DL (see bold text in example) are indented at same level as paragraphs before the nested DL.
Updated•22 years ago
|
Keywords: regression
Comment 2•22 years ago
|
||
Parser. The inner <dl> is closing out the <dd> for some reason. This is patently incorrect. We're taking this perfectly valid document and producing a totally invalid DOM (with <p> as direct kids of <dl>, eg).
Assignee: attinasi → harishd
Severity: normal → major
Status: UNCONFIRMED → NEW
Component: Layout → Parser
Ever confirmed: true
Keywords: html4
OS: Windows 2000 → All
QA Contact: petersen → moied
Hardware: PC → All
Comment 4•22 years ago
|
||
Good question... We have probably at least half a dozen bugs on <dl> issues; I don't know how many are due, at heart, to this problem. I can try to figure it out if you want.... The thing is, this _is_ valid markup... and not particularly bizarre valid markup at that (eg all the closing tags are correctly in place). We should really try to get that right.
Comment 5•22 years ago
|
||
fixed by bug 179071
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•