Re: [w3c/webcomponents] Slots in a flat tree (#308)

> Looking at WebKit I think right now slotted elements inherit from the parent of the <slot>, and webkit only respects display: none. That is doing slot { display: block; } has no effect.
>
> I'm very hesitant to ship with matching behavior, it doesn't seem like that's how display: contents was supposed to work.

Correct, that is a broken implementation.  Firefox has, afaik, a *real* implementation of display:contents.

> display: contents also has implications, for example are counter increments considered when declared on the slot? What about quoting level? Does slot::before and slot::after work? does display: contents disable ::before? (I hope so). What about slot::first-line ?

All defined by <https://drafts.csswg.org/css-display/#valdef-display-contents>.

Counters work on the element tree; they're not disturbed by box-tree manipulation.  (If they were, then the 'order' property would mess with them too.)  Quotes aren't very specific (they're defined by language lingering from CSS2, when we were *much* less explicit about the element/box/fragment divisions), but they *should* work the same.  Pseudo-elements still generate as normal.

---
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/308#issuecomment-204455431