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

I agree `execCommand()` is legacy and the spec can be clear about that. The point here is not to change direction for how to write editors.

We (Mozilla) need to fix [bugs with `execCommand()`](https://bugzilla.mozilla.org/buglist.cgi?quicksearch=execcommand&list_id=16606133) for web compat reasons and consider what its behavior should be for e.g. `contenteditable=plaintext-only` (#419). My hypothesis for specs for legacy features is that they're an investment that pays off in terms of less interop issues and therefore less web compat issues.

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

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