- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 28 Jun 2019 18:28:08 +0000
- To: public-houdini-archive@w3.org
Yes, it looks like this is a problem in the harness, where it's not using sufficient global knowledge to understand that PaintWorklet is a subset of Worklet. The current structure of the `Global` attribute is... weird for its requirements. I think the correct way to tell is to globally collect all the things that advertise `Global=PaintWorklet` and all the things that advertise `Global=Worklet`, verify that the first is a subset of the second, and thus conclude that `Exposed=PaintWorklet` on a subclass is valid when the superclass is `Exposed=Worklet`. (A better structure would probably be to have a more explicit "subclassing" of global names, so that you could declare, say, `[Global=Worklet:Paint]` and automatically be targeted by `Exposed=Worklet` *and* `Exposed=Worklet:Paint`, without having to do this global collection/intersection/etc. Different issue tho.) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/909#issuecomment-506834012 using your GitHub account
Received on Friday, 28 June 2019 18:28:09 UTC