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

@annevk Are you talking on behalf of Apple? That sounds like a different line of argument than what they have used previously, but if there is a commitment there, then we would have multiple browser engines!

I wonder, could a way to get implementations in more than one browser engine be to limit the spec to only document existing behavior (in the other browser engines)? If other browser engines aren't required to make any changes, then maybe that will make it possible to get a promise to implement the spec from them.

At any rate, `execCommand` is already taking a disproportionately large amount of time in the working group given its limitations and current usage with the spec text in its current state. I don't think it will get worse if it turns into a deliverable. In fact, the situation could improve if @zcorpan can put some time into maintaining and improving the text, checking where engines differ, etc. . So I think this is a good idea, at least to try out.

If we cannot promise what state the spec will advance to at what time, etc. then maybe it is a solution to add it to the items we [may possibly deliver](https://www.w3.org/2021/06/web-editing-wg-charter.html#ig-other-deliverables) rather than the ones we set concrete dates and goals for. That way we won't over-promise.

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

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