Re: [editing] Reference actions in clipboard API spec for execCommand copy/cut/paste (#61)

@hallvors btw, is Chrome working the way you expect it to? I noticed that Firefox would throw a security error in my example: http://pastebin.com/fnVGa7wC

If Chrome works the way you expect to, and the only thing that is important for you is that it is "user initiated", maybe such a user initiated check could simply be added to a normal function call that accepts the data to be added to the clipboard as an argument for use with cE=intentions?

If, on the other hand, Firefox is closer to the security level you are expecting, I think I would stick to my above proposal to simply have another function call instead of execCommand for use with cE=Intentions, so that browser makers eventually can remove execCommand altogether once they see usage has dropped to a very low number in a few years.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/61#issuecomment-127416308