Once again, I restate what I said before: custom elements are not necessarily compatible with any framework.
The original poster is asking about Ember and Handlebars. He's not asking about basic DOM capabilities like attributes, properties, etc. The fact that there is no standard for data-binding is an important part of the "any framework" aspect of the question. The poster wants to know if he can use custom elements with any framework and have it all work correctly, especially frameworks that support databinding like Ember. The answer to that question is no. Some things might work, others might not. It will probably depend on the framework. As I said, it won't work correctly with Angular 1.x. If that isn't a concrete example, I'm not sure what is. Now, I'm less familiar with Ember, so I'm not sure if they have that problem as well. Maybe not. Incidentally, the problem isn't a lack of a databinding standard. The problem is that the web components spec doesn't include any notion of metadata or self-describing components. Many would say that is an essential aspect of any component system. I've worked with many component systems over the years and web components is the first that seems to be missing that piece. If that were added to HTML, then it would be much easier to build binding systems like Angular's and Ember's and to ensure they work properly with anything. A lot of other interesting things would also be possible, of course. On Wednesday, November 12, 2014 4:56:08 PM UTC-5, Scott Miles wrote: > > >> Actually, no, custom elements are most definitely not theoretically > compatible with any framework > > This is not accurate from our perspective. Custom elements are > fundamentally indistinguishable from native elements and therefore work in > any DOM context. > > >> This is one of several reasons that Angular has to make big breaking > changes in 2.0 and why other libraries with databinding support will > probably follow in some fashion or another. > > There is no standard for data-binding. > > One can say, Angular doesn't support data-binding to Custom Elements, but > this is no fault of Custom Elements. > > It might also be true to say, Polymer's data-binding doesn't support > framework X. This also has nothing to do with Custom Elements, and again > reflects only the lack of a data-binding standard. > > Custom Elements support attributes, properties, events, and children, the > same as native elements. > > Scott > > On Wed, Nov 12, 2014 at 5:26 AM, Rob Eisenberg < > [email protected] <javascript:>> wrote: > >> Actually, no, custom elements are most definitely not theoretically >> compatible with any framework. Not out of the box at least. This is one of >> several reasons that Angular has to make big breaking changes in 2.0 and >> why other libraries with databinding support will probably follow in some >> fashion or another. >> >> On Tuesday, November 11, 2014 5:49:31 PM UTC-5, Eric Bidelman wrote: >>> >>> Theoretically, custom elements are compatible with any framework. >>> >>> https://www.polymer-project.org/docs/start/customelements.html#interop >>> >>> On Wed, Nov 12, 2014 at 9:18 AM, Christopher Dumas <[email protected]> >>> wrote: >>> >>>> I am a huge fan of Google's Material Design (and I think >>>> Polymer is really cool), and also of Ember.JS. I was interested to know >>>> whether you plan to have compatibility with Ember.JS. To clarify: I was >>>> hoping that Polymer might at least play nicely with Ember and Handlebars. >>>> Keep up the good work! >>>> >>>> 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/CD4C3C6E-FA6D-466E-ADAA-A3732FDBFE42%40me.com. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> 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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/polymer-dev/6fd8b32c-975f-4f65-89bd-5128db29d8bd%40googlegroups.com >> >> <https://groups.google.com/d/msgid/polymer-dev/6fd8b32c-975f-4f65-89bd-5128db29d8bd%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > 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/f4da903e-e2df-4c3a-96f8-9bd3cddb666a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
