Open Bug 236957 Opened 21 years ago Updated 4 years ago

Selection code creates ranges that cross anon content boundaries.

Categories

(Core :: DOM: Selection, defect, P5)

defect

Tracking

()

People

(Reporter: jst, Unassigned)

References

Details

Attachments

(1 file)

Followup bug to bug 236270. When selecting on a webpage, it's possible to end up with DOM range objects that start in the document's "real" DOM nodes, but ends in anonymous content. This confuses the content iterators, if nothing else. See testcase in bug 236270.
Maybe this is useful (if not, I'm sorry). Here is a simple testcase that shows how the range methods interact with content/anonymous content.
Also see bug 236796.
Depends on: 372086
So with bug 372086 fixed it should no longer be possible to create a range which has one end in anonymous content and the other in non-anonymous. Does that help with this bug?
Assignee: selection → nobody
QA Contact: selection

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.

Attachment

General

Created:
Updated:
Size: