Yes, I would love this feature to return. Not having it is probably the single most annoying thing with using Polymer for me.
I started designing an extensible set of UI components in the brief period when the feature was available and it was great! However, shortly afterwards it was removed and I had to instead use containment, which for a lot of situations is not nearly so neat. It seems completely logical to me to be able to inherit the basic look/layout of a component when creating another component that extends from it. I'm not entirely sure why the feature was removed as it worked well. I think I read somewhere that other browsers were having trouble implementing it, but if Chrome managed it, I can't see why they couldn't. Here's hoping there's some news of it's return soon! Mark On Tuesday, June 11, 2013 at 4:36:58 PM UTC+1, Jan Miksovsky wrote: > > In porting a component framework to custom elements, I've hit a > significant hurdle in creating a custom element that can both derive from, > and populate the visual presentation of, a base element. Because the > problem description got more involved than can comfortably fit in a > discussion board post, I've written a blog post on the problem: > http://blog.quickui.org/2013/06/11/puzzle-define-html-custom-element-subclasses-that-can-fill-in-base-class-insertion-points/ > . > > Any thoughts or suggestions from this community would be much appreciated! > 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/b0666a85-b2b9-4adc-bec1-6c3cfd2c3083%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
