Open
Bug 651103
Opened 13 years ago
Updated 8 months ago
Editor should not rely on the legacy parser for IsBlock and IsContainer
Categories
(Core :: DOM: Editor, defect, P5)
Core
DOM: Editor
Tracking
()
NEW
People
(Reporter: hsivonen, Unassigned)
References
(Blocks 1 open bug)
Details
Currently, Editor uses nsParserService to query elements for blockness or containerness. nsParserService relies on nsElementTable, which is part of the old parser and should go away. Editor should get some new source of information for this so that the bulk of nsElementTable can go away.
Comment 1•13 years ago
|
||
(In reply to comment #0) > Currently, Editor uses nsParserService to query elements for blockness or > containerness. nsParserService relies on nsElementTable, which is part of the > old parser and should go away. Editor should get some new source of information > for this so that the bulk of nsElementTable can go away. Do you have a suggestion for this new source?
Reporter | ||
Comment 2•13 years ago
|
||
(In reply to comment #1) > Do you have a suggestion for this new source? I'd put virtual PRBool IsContainer() { return PR_FALSE; } virtual PRBool IsBlock() { return PR_FALSE; } on nsIContent and override those in the per-element subclasses as appropriate according to the WHATWG HTML spec.
Comment 3•3 years ago
|
||
Bulk-downgrade of unassigned, >=5 years untouched DOM/Storage bugs' priority and severity.
If you have reason to believe this is wrong, please write a comment and ni :jstutte.
Severity: normal → S4
Priority: -- → P5
You need to log in
before you can comment on or make changes to this bug.
Description
•