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

> It's tricky, certainly, but it doesn't follow that there shouldn't exist a normative spec.

Right, and that's why the document exists in the form it has over the past decade with small modifications being done, but a clear note that the spec is likely not ever going to advance. 

If we add it to deliverables, that is saying that we promise/hope that the document will advance in the W3C system over the period of the charter. Until now we have had no such ambitions because of the clear indications made by browser makers other than Mozilla. Additionally, Mozilla did not participate much in the Editing Taskforce/Working Group historically, so there was probably little expectation that a Herculean effort of implementing a finished spec would take place in Firefox. 

But I notice there has been some more participation in the past year, so if only you can recruit a second browser maker to promise to implement an execCommand spec once it's reasonably complete, then I see nothing in the way of adding it to deliverables.

Note though that JavaScript editors work using other techniques than execCommand as of 2023. Even if execCommand were implemented without bugs in the exact same way in every browser engine, execCommand would need to get a new feature to allow extendability/customization for it to become of interest to most JavaScript editors. So I would ask you to make sure that any work on execCommand does not affect implementation/standardization work on other editing techniques that--at least for now--are of higher value to JavaScript editors (such as Input Events, EditContext, etc.).

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

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