Re: [csswg-drafts] [css-scoping] Handling global name-defining constructs in shadow trees (#1995)

I agree with @rniwa that off-hand I don't think `scope()` is necessary to solve this. Carrying the name and scope should be enough here.

Though it does have the caveat that fonts may leak out of the shadow tree for slotted children. I don't think I have a great solution for that though, and that does happen with a bunch of other stuff already (like, if the component sets some custom properties on the slot, the slotted children will inherit them and would be able to observe that there's a shadow tree).

GitHub Notification of comment by emilio
Please view or discuss this issue at using your GitHub account

Received on Tuesday, 16 April 2019 09:54:32 UTC