- From: <bugzilla@jessica.w3.org>
- Date: Thu, 18 Dec 2014 09:51:46 +0000
- To: public-css-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27626
Simon Pieters <simonp@opera.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |adrianba@microsoft.com,
| |bzbarsky@mit.edu
--- Comment #4 from Simon Pieters <simonp@opera.com> ---
The page with only caretPositionFromPoint uses it after checking for "firefox"
in navigator.userAgent, so it would start breaking in Firefox if it was
removed, but it wouldn't break for Blink to support it.
TinyMCE and CKEditor feature-check for caretRangeFromPoint before using it.
They don't use any other "WebKit-specific" code in that code-path. So it
wouldn't break for other browsers to support it.
To me this suggests the best path forward is to support both. The main risk I
think is that there are pages on the long tail that use other browser-specific
APIs depending on whether caretRangeFromPoint or caretPositionFromPoint is
supported, but it is encouraging that it appears to not be present in the
httparchive data.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 18 December 2014 09:51:48 UTC