window.document.caretRangeFromPoint is not supported in Firefox
Categories
(Core :: DOM: Core & HTML, defect, P3)
Tracking
()
Webcompat Priority | P3 |
People
(Reporter: karlcow, Unassigned)
References
(Blocks 1 open bug, )
Details
(Keywords: dev-doc-needed, parity-chrome, parity-safari)
The lack of window.document.caretRangeFromPoint
might get us blocked from using the site https://coda.io/
Reported initially on https://webcompat.com/issues/30408
Steps to reproduce:
On https://coda.io/signin
Firefox is redirected to https://coda.io/unsupported-browser?continueTo=%2Fsignin
On this page, they are pledging they are in the process of supporting other platforms.
Impersonating Chrome UA we can avoid the redirection, and access the application. After the sign up process, the application fails because of the lack of window.document.caretRangeFromPoint
That doesn't mean that if Firefox supported it, it would solve all issues for this case, but that's a starting point it seems.
This is currently supported by Blink, WebKit, EdgeHTML
not supported by Trident and Gecko.
https://developer.mozilla.org/en-US/docs/Web/API/Document/caretRangeFromPoint
Here an example of polyfill for it
https://github.com/Abel-Jr/OurSite/blob/55c221dd8abf474a1075c5d3a817eaae97b73fce/wp-includes/js/dist/dom.js#L614-L647
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Comment 1•5 years ago
|
||
We should file a bug in the compat standard for this, at least.
Updated•5 years ago
|
Comment 2•4 years ago
|
||
Coda now is working on Firefox (even still without the caretRangeFromPoint support) , but not on Fenix.
Hi Karl, do you think you can help us do further investigation to understand the root cause of the issue on Android/Fenix? Thank you.
Comment 3•4 years ago
|
||
Guessing Hsin-Yi may have meant other Karl.
Updated•4 years ago
|
Reporter | ||
Comment 4•4 years ago
|
||
Let's see if Adam has an opinion about Fenix and Coda.
Does the site work or is used on Google Chrome too?
Hsin-Yi, When you say this is not supported on Fenix? In which ways?
Updated•2 years ago
|
Comment 5•2 years ago
|
||
Clear a needinfo that is pending on an inactive user.
Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE
.
For more information, please visit auto_nag documentation.
Updated•2 years ago
|
Comment 6•7 days ago
|
||
This would help us to pass the WPT https://wpt.fyi/results/css/css-contain/content-visibility/content-visibility-080.html, which Safari and Chrome both pass.
Updated•7 days ago
|
Description
•