287472 2025-02-11 00:21:36 -0800 document.caretPositionFromPoint returns null over SVG elements and elements with `-webkit-user-select: none` 2025-08-21 13:39:11 -0700 1 1 1 Unclassified WebKit DOM WebKit Nightly Build Unspecified Unspecified RESOLVED FIXED https://github.com/web-platform-tests/wpt/pull/54176 InRadar P2 Normal --- 286941 1 annevk akeerthi bfulgham rbuis simon.fraser webkit-bug-importer oldest_to_newest 2093752 0 annevk 2025-02-11 00:21:36 -0800 <svg width=100 height=100><circle cx=50 cy=50 r=50 /></svg> <script> range = document.caretRangeFromPoint(50, 50); w(range); </script> logs null instead of a range pointing to the svg element. This can make shadow trees containing SVG observable (as we return null rather than a range for the host element). I discovered this in bug 286803. https://software.hixie.ch/utilities/js/live-dom-viewer/?%3Csvg%20width%3D100%20height%3D100%3E%3Ccircle%20cx%3D50%20cy%3D50%20r%3D50%20%2F%3E%3C%2Fsvg%3E%0A%3Cscript%3E%0Arange%20%3D%20document.caretRangeFromPoint(50%2C%2050)%3B%0Aw(range)%3B%0A%3C%2Fscript%3E 2095417 1 webkit-bug-importer 2025-02-18 00:25:08 -0800 <rdar://problem/145038689> 2107552 2 bfulgham 2025-03-31 13:46:06 -0700 Shouldn't this be `document.caretPositionForPoint()`? 2107558 3 bfulgham 2025-03-31 13:51:47 -0700 https://software.hixie.ch/utilities/js/live-dom-viewer/saved/13608 2107734 4 annevk 2025-03-31 23:27:06 -0700 I'm pretty sure both use the same underlying infrastructure and we need to fix that as this ends up exposing shadow roots when they use SVG. 2134622 5 akeerthi 2025-08-05 20:53:17 -0700 Pull request: https://github.com/WebKit/WebKit/pull/48997 2134761 6 akeerthi 2025-08-06 14:29:16 -0700 Submitted web-platform-tests pull request: https://github.com/web-platform-tests/wpt/pull/54176 2134818 7 ews-feeder 2025-08-06 18:08:19 -0700 Committed 298313@main (74c2e1e966aa): <https://commits.webkit.org/298313@main> Reviewed commits have been landed. Closing PR #48997 and removing active labels. 2138077 8 akeerthi 2025-08-21 13:39:11 -0700 *** Bug 287796 has been marked as a duplicate of this bug. ***