Closed
Bug 849745
Opened 11 years ago
Closed 4 years ago
Assertion failure: "AncestorHasDirAuto set on node but not its children" with nested dir=auto, comment
Categories
(Core :: DOM: Core & HTML, defect, P3)
Tracking
()
People
(Reporter: jruderman, Unassigned)
References
Details
(Keywords: assertion, regression, testcase)
Attachments
(2 files)
330 bytes,
text/html
|
Details | |
4.25 KB,
patch
|
ehsan.akhgari
:
feedback+
|
Details | Diff | Splinter Review |
Assertion failure: !aElement->AncestorHasDirAuto() || child->AncestorHasDirAuto() (AncestorHasDirAuto set on node but not its children), at content/base/src/DirectionalityUtils.cpp:684
Updated•11 years ago
|
Keywords: regression
Comment 1•11 years ago
|
||
Wow, I had no idea that comments turn up looking like other child nodes when walking the DOM. Are there other kinds of nodes that we should be excluding here?
Attachment #724845 -
Flags: feedback?(ehsan)
Comment 2•11 years ago
|
||
Processing instruction?
Comment 3•11 years ago
|
||
And does the code handle both TEXT_NODE and CDATA_SECTION_NODE? (There is some child->NodeType() == nsIDOMNode::TEXT_NODE check).
Comment 4•11 years ago
|
||
Comment on attachment 724845 [details] [diff] [review] Patch v.1 Review of attachment 724845 [details] [diff] [review]: ----------------------------------------------------------------- Yeah you want to handle PIs too.
Attachment #724845 -
Flags: feedback?(ehsan) → feedback+
Comment 5•7 years ago
|
||
Confirmed that current m-c is still affected.
Severity: critical → normal
Has Regression Range: --- → no
status-firefox56:
--- → wontfix
status-firefox57:
--- → wontfix
status-firefox58:
--- → fix-optional
status-firefox-esr52:
--- → wontfix
Priority: -- → P3
Comment 6•6 years ago
|
||
https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Move_fix-optionals
status-firefox59:
--- → ?
Assignee | ||
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
Comment 7•4 years ago
|
||
This was last seen by the fuzzers in Aug 2018. The attached test case also no longer reproduces the issue.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Updated•4 years ago
|
Resolution: FIXED → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•