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)

@siusin It cannot be fully replaced by EditContext.  This document listed 3 different types (`events`, `caret`, `typing`) of contenteditable-alike API. EditContext goes into detail in one of these three.

With this document, we also tried to standardize places the caret should be able to go, which AFAIK is still not specified anywhere else and which has [recently been requested again](https://github.com/w3c/editing/issues/481). Some of this the issues experienced in this area were solved by having Chromium and Gecko developers get into direct communication with JS  developers and fix a number of bugs without there being any specification around this.

This document was mentioned [as a delivery in the TF charter](https://github.com/w3c/editing/blob/gh-pages/CHARTER.md) until 2021.

I was under the impression that this document should fall under the "scope" of our charter as it lists all the areas we will work on, whereas the list of deliverables only mention those that we believe strongly will advance. But I am not a lawyer. If it's not possible to do as mentioned above, another option could be to just wait for half a year until our charter is up for renewal and then to add it to the list of deliverables. Based on [@frivoal's comments](https://github.com/w3c/editing/issues/479#issuecomment-2636098918) I understand it is important for the W3C not to hurt the brand value of W3C Notes and to avoid having them be a dumping ground of discontinued specs. This could be a way to avoid that.

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

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