I was wondering that myself. I extended the 0.5 core-splitter with great success. Essentially I wanted *all* the functionality from the JS plus a little extra but *none* of the HTML, I wrote my own view.
On Thursday, March 12, 2015 at 4:59:47 PM UTC-4, Helen Wu wrote: > > I was wondering what the reasons behind not having custom element > inheritance were. I know that it's good to prefer composition over > inheritance, but there are also places where the use of inheritance is > pretty obvious. > > Is it possible to share the plan to update the current polymer elements to > use composition over inheritance (for example the elements that use > core-selector would be a good example), so that we have an idea of what > changes to make in our 0.5 versions to prepare for the 0.8 release? > > 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/e9461306-2598-478a-8986-4030f4176d39%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
