Re: [webcomponents] How about let's go with slots?
On Mon, May 18, 2015 at 8:54 PM, Hayato Ito wrote: > > The hint we can use is: > > - tag name > - id attribute > - class attribute > - any other attributes. (Okay to have a dedicated attribute, such as > 'content-slot') > - The position of the node in the list > - Other status, such as ":focused" (in CSS's terminology) > - Anything else? > Another potential hint is element class/type/instanceof. I can see a situation where I'd want to "select" any element that is an `instanceof` HTMLButtonElement. Or if a third-party library creates an element that "selects" , it may want to allow the selection of subclasses of that element but not other arbitrary elements.
Re: [webcomponents] How about let's go with slots?
Pardon my question if this has been discussed elsewhere, but it's not clear from my reading of the "slots" proposal whether they would be allowed to target elements that are not direct children of the component. I believe the with the `select` attribute this was implicitly required because only compound selectors were supported (i.e. no child or descendent combinators) [1]. Would named slots be able to target elements farther down in the tree? [1] http://w3c.github.io/webcomponents/spec/shadow/#dfn-content-element-select
Re: [webcomponents]: First stab at the Web Components spec
Personally, I had no objection to rel="component". It's similar in usage to rel="stylesheet" in the fact that it's descriptive of what you're linking to. On the other hand, rel="include" is very broad. It could just as easily apply to a stylesheet as a Web component, and may limit the usefulness of the term if/when future rel values are introduced. (p.s. I'm new to this list and haven't read through all the previous discussions on Web components. Feel free to disregard this comment if I'm rehashing old topics) On Mon, Mar 11, 2013 at 2:28 PM, Dimitri Glazkov wrote: > On Fri, Mar 8, 2013 at 1:47 PM, Robert Ginda wrote: > >> rel="include" ? >> > > And "Inclusions" as the name? Or "HTML Inclusions"? This could work. > > Any objections or better names? Rob might just win this one. > > :DG< >