Re: [clipboard-apis] Move script-created events out of "fire a clipboard event" (#16)

@hallvors : Indeed, that seems to be the current state of affairs, although it is a taskforce and not a community group. The main point of the taskforce is to make editing in the browser usable and taking on all the editing spec works and figuring out which ones are to survive and which ones aren't. The feedback we have received from browser makers so far has been that they have no interest at all in implementing a contentEditable=true or execCommand specification and that they would also like to see both deprecated. Additionally, we have discussed whether we should deprecate these features but still write the specs for them, and the feedback has been that there is no interest in implementing such specs if these features are deprecated anyway.

Also, we have not been able to found anyone willing to spend time on working on these specs and noone has suggested spending any time at the F2F to work collectively on these specs.

With that in mind, it seems fairly plausible that the F2F meeting either decides to remove all text of the spec drafts and replace it with a text discouraging the use of execCommand and contentEditable and deprecating these, or that it will postpone this decision to a later date but to not allocate any further time to work on these. 

Of course you guys can change it all. The F2F meeting in Paris 23-24 August will also be accessible through IRC, etc. so if you have a good argument why these should continue to be developed and someone has the time required to work on these, I don't think anyone will be against doing that.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/clipboard-apis/issues/16#issuecomment-127382687