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

I don't know this is a meaningful use case, but I found this while trying to convert `<input>` `<textarea>` elements to use V1 user-agent shadow DOM. Unless ClipboardEvent is composed, any clipboard event happened in the internal user agent shadow doesn't propagate outside the UA shadow.
So it means you cannot create your own input or textarea custom element, although technically it is possible to redispatch an event when a clipboard event is caught on the boundary shadow root.  So the request is coming from myself, so to say.

In the Shadow DOM V0 era, such clipboard events are not listed in the "scoped events" list, and crossed the shadow boundary already (including user-agent shadow boundary).

I think I made sure as much as I can to check if anything leaks, but no one can be perfect.
I'm asking people cc'ed here, and clipboard API authors for sanity checking and opinions.

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