Bug 213975 - Use RenderObject::positionForPoint instead of hit testing the entire view in closestEditablePositionInElementForAbsolutePoint
Summary: Use RenderObject::positionForPoint instead of hit testing the entire view in ...
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: WebKit Local Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Daniel Bates
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2020-07-05 12:36 PDT by Daniel Bates
Modified: 2020-07-06 09:28 PDT (History)
4 users (show)

See Also:

Attachments
Patch (2.34 KB, patch)
2020-07-05 12:52 PDT, Daniel Bates 		no flags Details | Formatted Diff | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Bates 2020-07-05 12:36:03 PDT 
This bug is following up on my comment bug 210939, comment 3. closestEditablePositionInElementForAbsolutePoint can be made more efficient by using RenderObject::positionForPoint to hit test the target element's renderer instead of doing this indirectly by way of hit testing the entire RenderView.
Comment 1 Daniel Bates 2020-07-05 12:52:08 PDT 
Created attachment 403561 [details]
Patch
Comment 2 Daniel Bates 2020-07-06 09:27:52 PDT 
Comment on attachment 403561 [details]
Patch

Clearing flags on attachment: 403561

Committed r263969: <https://trac.webkit.org/changeset/263969>
Comment 3 Daniel Bates 2020-07-06 09:27:54 PDT 
All reviewed patches have been landed.  Closing bug.
Comment 4 Radar WebKit Bug Importer 2020-07-06 09:28:14 PDT 
<rdar://problem/65134809>