- From: Elliott Sprehn <notifications@github.com>
- Date: Thu, 31 Mar 2016 18:22:27 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
Received on Friday, 1 April 2016 01:22:54 UTC
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. display: contents also has implications, for example are counters increments considered when declared on the slot? What about quoting level? Does slot::before and slot::after work? does display: contents display ::before? (I hope so). I'd like to work out the details before we commit to making display: contents be a thing, and slot having a dependency on that technology. The current system is easy to explain, <slot> is just gone by the time styles are computed. There's no subtle rules for what does and does not apply. --- 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-204198578
Received on Friday, 1 April 2016 01:22:54 UTC