Re: [w3c/editing] Updated the intro material to better reflect the current status. (#302)

The initial discussion about this was mainly on the email list. Try reading the email thread with the title "existing contenteditable spec" [1] That then turned into a meeting. A few months later, the wording again came up for discussion under the thread "on execCommand() and script-triggered copy/cut/paste" [2]. The parts that were discussed at informal parts of the F2F meetings were not captured there. If I recall correctly, it was mainly a question of whether the feature should be marked as "deprecated" or  whether it should be classified as "we may work on this again some time in the future". Especially the Chromium team was very clear about their view: they would not change their implementation due to anything any spec would ever say, but they might under some circumstances change their implementation of individual features to be closer to that of other browsers. The final wording there was carefully negotiated and was not easily reached at as there were several different positions to cover.

It is true that positions may change and that may just have happened here. But given that it has been a major decision to go away from trying to get execCommand to work for editors and instead to work on other mechanisms, and that this wording was negotiated, I think such a change would at the least be needed to be discussed on the mailing list and all the involved parties should be consulted.

So yes - let's put this on the agenda for a call or let's have a new discussion on the email list about this. And I would think that @njdjacobs should probably sign some type of agreement with the W3C, as such a discussion would possibly also involve things that are relevant in terms of intellectual property, licenses, etc. .

[1] https://lists.w3.org/Archives/Public/public-editing-tf/2015May/thread.html

[2] https://lists.w3.org/Archives/Public/public-editing-tf/2015Aug/thread.html

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