Thanks for your reply Santiago. Wouldn't it be nice if the styles would be inherited too ?
On another note, I have the following beef (issue, bug?): In a child (inheritance) element, ::content selectors need to be doubled. See the sample code: https://gist.github.com/clyfe/1bc824479eb2d29c3d13 Is this a bug or expected behavior? If bug on what repo should I fill ? luni, 27 octombrie 2014, 13:03:00 UTC+2, Claudius Nicolae a scris: > > Let's say element B extends A. > > <polymer-element name="A"> > <template> > The property: {{property}} > </template> > <script> > Polymer({ property: 'Property defined in A' }); > </script> > </polymer-element> > > <polymer-element name="B" extends="A"> > <template> > <!--shadow></shadow--> <!-- NO shadow! I want my own completely > different template! --> > My own template, with binding: {{property}} > </template> > <script> > Polymer(); // no overrides here > </script> > </polymer-element> > > 1. (templating) > Can B have it's own template without calling "<shadow></shadow>" ? > If yes, will properties and events defined in A be bound the B's new > template ? > > 2. (styling) > Will styles defined for A apply to B, now that the tag name has changed ? > If yes, how much of them? Only those defined on :host, or also those > involving the "A" tag name ? > > Thanks. > Follow Polymer on Google+: plus.google.com/107187849809354688692 --- You received this message because you are subscribed to the Google Groups "Polymer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/5df0f8eb-a800-44da-a55e-c17d50041795%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
