Closed Bug 751 Opened 27 years ago Closed 26 years ago

GetPosition in nsTextFrame is slow

Categories

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

Product:
Core
Component:
DOM: Selection
Platform:
x86
Windows NT
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: kipp, Assigned: rods)

Details

(Whiteboard: this bug is just waiting for reporter/owner to verify)

Currently it does a linear scan forward. A simple demonstration of why this is very bad can be made by creating a text element with, say 10,000 characters in it, and then watching the selection speed suck. Something on the order of a binary search seeded assuming the x coordinate maps to 1/2 the max-width of the font will probably work much better
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
installing myself as QA Contact en masse
Changing a few bugs at once...This is a bug that I have determined I am unable to properly verify. More than likely this would be because it is outside my expertise or experience, or i don't have the necessary tools. I am now ASKING PLEASE, please could the bug owner or reporter take it upon themselves to verify the fix for this bug and mark it VERIFIED? Don't be shy, step right up. Thank you.
Whiteboard: this bug is just waiting for reporter/owner to verify
Status: RESOLVED → VERIFIED
marking verified....
Per a request from Selection and Search component eng (mjudge) and qa (elig), moving all "Selection and Search" bugs to new "Selection" component. Original "Selection and Search" component will be retired.
You need to log in before you can comment on or make changes to this bug.