Re: [clipboard-apis] The ClipboardEvent constructor is strange (#10)

@annevk it's not supposed to cause actions, it is supposed to trigger listeners that carry out actions. Sorry if I'm being unclear. By "editor capable of handling a paste" and "context that has scripts listening to paste events" I mean DOM elements (whether contentEditable=true/designMode=on or plain TEXTAREA/INPUT) that have a 'paste' event listener that will respond to paste events and do something with the event's data payload. Hence, if a synthetic event can have a payload it can be used both for testing and for data exchange between components that are designed to avoid tighter coupling. 

If a synthetic paste event can *not* have a payload it's pretty much useless and we might as well drop the constructor and avoid the issue.

Clear enough?

(BTW I think I remember making a minor edit right after submitting the comment, perhaps Github E-mailed you the first version where the last sentence was less clear. Apologies for any confusion.)

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