RESOLVED INVALID 227191
HitTestLocation should not use a fixed (1px, 1px) area for point based hittest 
https://bugs.webkit.org/show_bug.cgi?id=227191
Summary HitTestLocation should not use a fixed (1px, 1px) area for point based hittest
zalan
Reported 2021-06-19 21:21:00 PDT
at least it should be based on the device scale factor
Attachments
Patch (36.53 KB, patch)
2021-06-19 21:34 PDT, zalan 		no flags
DetailsFormatted DiffDiff
Patch (41.79 KB, patch)
2021-06-21 14:14 PDT, zalan 		no flags
DetailsFormatted DiffDiff
Patch (43.21 KB, patch)
2021-06-22 12:57 PDT, zalan 		no flags
DetailsFormatted DiffDiff
Show Obsolete (2) View All Add attachment proposed patch, testcase, etc.
zalan
Comment 1 2021-06-19 21:34:31 PDT
Created attachment 431812 [details] Patch
Sam Weinig
Comment 2 2021-06-20 13:16:05 PDT
Comment on attachment 431812 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=431812&action=review > Source/WebCore/ChangeLog:16 > + Eventually the input to HitTestLocation::intersect should be a device pixel snapped rect similar to painting. What makes doing this now difficult?
Sam Weinig
Comment 3 2021-06-20 13:16:46 PDT
Comment on attachment 431812 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=431812&action=review > Source/WebCore/ChangeLog:12 > + This is an intermediate solution to support hit-test content on subpixel position. > + It fixes cases when we incorrectly find renderers on subpixel positions due to the integral inflate of the hit coverage area. > + e.g > + hit testing location is at [10, 10] > + renderer is at [10.6, 10] -> device pixel snapped to [11p, 10] on a 2x display Seems like we should have some tests for this.
zalan
Comment 4 2021-06-21 14:14:26 PDT
Created attachment 431907 [details] Patch
zalan
Comment 5 2021-06-22 12:57:50 PDT
Created attachment 431986 [details] Patch
Radar WebKit Bug Importer
Comment 6 2021-06-26 21:21:19 PDT
<rdar://problem/79824597>
Brent Fulgham
Comment 7 2022-06-29 14:23:22 PDT
Alan ended up landing a more targeted fix. This change is no longer needed.
Note You need to log in before you can comment on or make changes to this bug.