Re: [w3c/webcomponents] Named slots and the slot attribute requirement (#726)

> @cary-smith no, @rniwa states that only an *imperative* solution would be acceptable to Apple. Thus far we haven't been able to figure out such an API.

That's not true. We're against using the CSS selector as a mechanism to match an element but not against providing a declarative mechanism to select an element based on its type such as the interface object. Our only requirement is that the slotting mechanism be performant; i.e. not as slow as evaluating a CSS selector whenever a node gets modified.


-- 
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/webcomponents/issues/726#issuecomment-367172635