- From: Hayato Ito <notifications@github.com>
- Date: Wed, 10 Jun 2015 19:14:39 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Message-ID: <w3c/webcomponents/issues/92/110970487@github.com>
I guess you guys might want to read the slots proposal carefully. Aa far as I can read from the slots proposal, [1], there is one significant change in the behavior. - \<content\> doesn't select other \<content\> elements. It tries to select the distributed nodes of the other content elements. See http://w3c.github.io/webcomponents/spec/shadow/#dfn-pool-population-algorithm for details. - \<slot\> selects other \<slot\> elements [1] https://github.com/w3c/webcomponents/blob/gh-pages/proposals/Slots-Proposal.md That's the reason I have a concern. In \<content\>, I guess developers doesn't get confused by `::content` because content elements never select other content elements. In \<slot\>, developers might get confused by `::slot` because slot elements *select* other select elements. It is also worth noting that '::content' is always used with a left side selector, such as "content::content". "#abc::content", in practical. "::content" might be okay, but it should be avoided in practical because "*::content" is very wasteful. "content::content" can replace "::content" unconditionally. I guess the same thing applies for slots elements. - "::content" can be replaced with "slot::content", and it should be recommended to avoid unnecessary selector matching. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/92#issuecomment-110970487
Received on Thursday, 11 June 2015 02:15:19 UTC