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

@foolip Others can of course join the editing taskforce, and argue to not deprecate execCommand. The point is precisely to coordinate the efforts in the area of editing in this taskforce. It's not a lack of interest in execCommand that makes people want to deprecate it. It is more an active wish to make it go away that seems to drive this pending decision.

@annevk Of course, it will take a while before execCommand can be removed entirely from browsers due to the legacy code that is out there that depends on it. That is likely also why they preferred to replace cE=True with something entirely new. 

But I suggest for all of you guys to join the mailing list and argue your point.

But even if contenteditable=true/execCommand is to be revived, none of this will influence the new specs in which execCommand will not work.

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