Closed Bug 2054998 Opened 1 month ago Closed 14 days ago

Avoid requesting all character bounds if EditContext.text is long for QueryCharacterAtPoint

Categories

(Core :: DOM: Editor, enhancement)

Product:
Core
Component:
DOM: Editor
Type:
enhancement

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: ltenenbaum, Assigned: ltenenbaum)

References

Details

Currently for handling OnQueryCharacterAtPoint, we request all of the character bounds and search for one that matches. For very long text this is not ideal, as it may take some time to generate them on the JavaScript side. So we should try to do a binary search, since in the majority of cases, the character bounds will be ordered lexicographically by (top, left) for horizontal or (left, top) for vertical text. If this fails, we can fall back to requesting all of the bounds.

This might not be relevant anymore due to bug 2058621 (we might not be firing characterboundsupdate at all in OnQueryCharacterAtPoint)

No longer relevant due to bug 2058621

Status: ASSIGNED → RESOLVED
Closed: 14 days ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.