[Webkit-unassigned] [Bug 102398] Clamp cursor hotspot values that are out of range to be consistent with Chrome and Firefox (even though no one has complained)

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=102398

--- Comment #31 from Rick Byers <rbyers at chromium.org> ---
Note that this originally came up in Chrome as a surprise/confusion from a web developer when I changed Chrome to match Safari instead of all the other browsers: https://bugs.chromium.org/p/chromium/issues/detail?id=172857#c13. Happy to discuss and align in a standards forum if there's interest in unifying one way or the other. We could probably even collect some hard web compat data if that would be useful - like what fraction of pageloads we clamp hotspots on, and possibly even some example URLs. But I think we all agree this is far from being a high priority interop issue.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20220718/651e5421/attachment.htm>