Closed Bug 1368408 Opened 3 years ago Closed 3 years ago

Selection should assume that start and end container of a selection range and current node of content iterator before done are never nullptr

Categories

(Core :: DOM: Selection, enhancement)

enhancement
Not set

Tracking

()

RESOLVED FIXED
mozilla55
Tracking Status
firefox55 --- fixed

People

(Reporter: masayuki, Assigned: masayuki)

References

Details

Attachments

(1 file)

No description provided.
Comment on attachment 8872277 [details]
Bug 1368408 Selection::SelectFrames() can assume that the result of nsRange::GetStartParent(), nsRange::GetEndParent() and nsIContentIterator::GetCurrentNode() never returns nullptr in it

https://reviewboard.mozilla.org/r/143776/#review147560
Attachment #8872277 - Flags: review?(mats) → review+
Pushed by masayuki@d-toybox.com:
https://hg.mozilla.org/integration/autoland/rev/0ca74eae6beb
Selection::SelectFrames() can assume that the result of nsRange::GetStartParent(), nsRange::GetEndParent() and nsIContentIterator::GetCurrentNode() never returns nullptr in it r=mats
https://hg.mozilla.org/mozilla-central/rev/0ca74eae6beb
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
You need to log in before you can comment on or make changes to this bug.