Re: [w3c/clipboard-apis] Define each event type is composed or not, update the spec (#61)

Thanks. Given your explanation so far, I guess your motivation came from:

- ClipboardEvents and InputEvents are similar. So make ClipboardEvents composed=true for consistency.

Is the consistency the only motivation?  Can I assume that we have not heard any use case or request from customers, like Polymer, to make this happen?

> I don't think on copy/cut you can read the to-be-placed-in-clipboard data from ClipboardData, but just you can set your own arbitrary data to it. But I may miss something.

I don't know neither. Please make sure there wouldn't be an unintentional content leak in CblipboardEvent, before making PR.

-- 
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/clipboard-apis/issues/61#issuecomment-357878833