Re: [w3c/editing] [charter] execCommand spec should be in scope (Issue #432)

 
> 1. The specification needs to be web compatible for it to be useful. Any changes to existing behavior of implementations need very good justification. Probably a higher bar than we employ elsewhere.
> 2. The specification needs to allow implementations to follow platform-specific conventions where applicable.

 I think these two points Anne mentioned make sense from a Chrome/Chromium perspective as well. I'd also like to note that:

* In practice item 1 will tend to result in choosing existing Blink/WebKit behavior if it's shared by those implementations.
* My research so far leads me to conclude that not many libraries or sites use `execCommand` very much (but still a substantial enough number to be worried about web compat), which is another reason to be conservative about accepting normative changes.



-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/432#issuecomment-1599599667
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/editing/issues/432/1599599667@github.com>