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

@garykac thanks for the comment.
The conclusion at https://github.com/w3c/webcomponents/issues/513#issuecomment-224486249 was to iterate on each UA-firing events (not UI events) to see if it is a good fit for having `composed=true` by default or not.  So not all UI events are `composed=true` by default.  (while I'm writing this @annevk outpaced me).

@annevk I agree that I don't see much sense ClipBoardEvents having `view` or `detail` - we don't make clipboard events inherit UIEvent just because we want to make its `composed` default to be true. So to answer @hayatoito's question https://github.com/w3c/clipboard-apis/issues/61#issuecomment-357930616 we don't have to make clipboard events inherit from UI Events, but we can do it independently from `composed` default value change, if necessary.

Let's close the loop for whether or not inherit from UIEvent.

-- 
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-359706849