Open Bug 1459269 Opened 6 years ago Updated 2 years ago

Consider optimizing GetRangesForIntervalArray and its consumers

Categories

(Core :: DOM: Selection, enhancement, P3)

enhancement

Tracking

()

People

(Reporter: bzbarsky, Unassigned)

References

Details

In bug 1387143 comment 32, Mats says:

A side note on GetRangesForIntervalArray: Maybe it could be optimized to take advantage of the bits we have on each node whether they are part of a selected range and get the potential ranges from there?  Also, some callers probably don't need this detailed information anyway and/or would be more efficient if they handled each range sequentially rather than demanding the full array upfront (e.g. mozInlineSpellChecker::IsPointInSelection).
Depends on: 1387143
Priority: -- → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.