Re: [w3c/editing] CfC: Publish the "ContentEditable" draft spec as a FPWD, and then immediately republish as a Discontinued Draft (Issue #480)

johanneswilm left a comment (w3c/editing#480)

> Why publish it at all if we don't want the community to look at it?

This is probably the most important question. The thing is that there is a non-zero chance that we will need to go back to this document as we did a number of times around 2013-2016. So far we have one implementation of EditContext and one major independent user of it who [recently announced that they would suspend usage of EditContext due to certain unpredictable behavior](https://github.com/w3c/edit-context/issues/111#issuecomment-2618931646) which we hope to change in the spec, but it's not clear we will be able to. We also do not have a second implementation of EditContext. There is also the question of legal caret positions which is not dealt with in any other document that came up again just a few days ago.

Even though neither the contentEditable nor the execCommand specs have any formal standing in the W3C (both pre-FPWD, both have not been worked on formally for years), they continue to be referred to and used as if they were official. It was when we discussed which documents to put on the deliverables list for the next charter that it was suggested to add the contentEditable document to it and I had to explain the status of the document again (it is listed as "archived" in our overview at https://github.com/w3c/editing ). This is why we wanted to publish it as a note to make it clear that it is not moving on (in our current view) while preserving it in its current state just in case it needs to be reanimated in the future.  

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

Message ID: <w3c/editing/issues/480/2669322738@github.com>