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

Hey,

this is a Call for Consensus for publishing the [document entitled "ContentEditable"](https://github.com/w3c/contentEditable) as a note and then to stop work on it following [a resolution of the call on 2024-01-09 to do so](https://lists.w3.org/Archives/Public/public-editing-tf/2025Jan/0000.html).

The background for this decision is that this document was written a decade ago while we were trying to come up with a new text editing API that would work around some of the inherent problems present in contenteditable=True/execCommand that already was present in browsers at the time. These proposals are what eventually led to the [EditContext API](https://github.com/w3c/edit-context) which supersedes it and has since been implemented and shipped in Chrome and is on track to be shipped by other browser engines as well.

This does not affect the definition of contenteditable=true, contenteditable=false and contenteditable=plaintext-only as they can be found in the [HTML spec](https://html.spec.whatwg.org/#contenteditable). Nor does it affect execCommand which is described in [another unofficial draft document](https://w3c.github.io/editing/docs/execCommand/).

If you have comments or questions or you disagree with this decision, please comment on this Github issue by February 18 2025.

**Note: We initially aimed at publishing the document as a note. But [as Florian Rivoal pointed out](https://github.com/w3c/editing/issues/479), a discontinued draft is the better choice.**

Best regards,

Johannes Wilm (IE, Web Editing WG Chair)

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

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