Re: [w3c/webcomponents] Styling default slot content with ::slotted (#631)

Good catch. Yeah, I think this is not a spec bug. This should be considered as an implementation bug.

The following is a brief history:

1. We defined `::slotted` to consider `assignedNodes({ flatten: true })`, instead of `assignedNodes()`, in the spec. That was intentionally done.
2. Blink implemented `::slotted`
3. After that, we introduced the concept of fallback contents of slots, and we extended the meaning of `assignedNodes({ flatten: true })` to consider slot's children too in the spec, without any considering its impact for `::slotted`. See https://github.com/w3c/webcomponents/issues/317
4. It looks Blink forgot to update the implementation of `::slotted` to consider slot's fallback contents. :(

Regarding the spec, although we have not considered anything about an impact for `::slotted`, in https://github.com/w3c/webcomponents/issues/317, I am +1 for the status quo of the spec.

If it is okay, I'll file a bug in Blink and close this spec bug.




-- 
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/631#issuecomment-288294444