Re: [w3c/webcomponents] flatten: true in assignedNodes doesn't make much sense when a slot doesn't have display: contents (#493)

> No, you only care about `display:contents` when you generate the flattened tree. For the DOM API that should not matter one bit. We don't let `firstChild` depend on whether any child has `display:none`.

In that case, we shouldn't have `flatten: true` option at all.

Think about why we need `flatten: true` in the first place.  That's because nodes assigned to slot A, which is in turn assigned to slot C appear as though they're direct children of slot C.  However, this is a consequence of the fact slot A has `display: contents`.  If it didn't, then there is nothing special about slot A.  All assigned nodes of slot A would generate CSS boxes under slot A's CSS box, and they don't appear as direct children of slot C at all.

---
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/493#issuecomment-217935674