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

Hey @zcorpan ,
the description of in scope and out of scope can be found in points 1.2 and 1.3: https://www.w3.org/2021/06/web-editing-wg-charter.html . As far as I can tell, the execCommand spec falls into the current scope.

Could you specify what you want to change in the in scope list? Or do you mean that you propose to make the execCommand a deliverable? 

The issue thus far has been that (other than Mozilla?) no browser vendor wants to commit to implement the spec even if completed and that prevents the specification from advancing. This is due to several legacy apps that rely on the browsers behaving the way they do + it would take an extreme amount of resources to make browsers behave the exact same way. It's also the reason multiple other specs have been launched over the past decade, such as the Input Events spec or the EditContext spec, which both aim at making execCommand obsolete. JavaScript editors have largely stopped using execCommand many years ago.

If you can find a second browser vendor willing to commit to implement the spec and you can find someone willing to take over maintainership of the document and work a  lot on it over the next few years, I would be in favor of putting it on the list of deliverables. If you cannot find such support, I don't see how we can commit to delivering it.

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

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