You're loading platform.js: https://github.com/urandom/readeef/blob/feefcb4b450d0be3a15339d1c8eb2ae6a20c6795/templates/app.tmpl#L9. Have you tried loading webcomponents.js?
See https://blog.polymer-project.org/releases/2014/11/12/release-0.5.1/#0-5-1_platform On Mon, Nov 17, 2014 at 8:12 AM, Viktor Kojouharov <[email protected]> wrote: > That's not the problem at all. > > 0.4.2 had no problem displaying that element correctly. Regardless, I > removed the bind attribute from the template element (and I found another > that also had such a bind element), but that didn't change anything. > > CustomElements.parser is still undefined. > > On Sunday, November 16, 2014 9:53:42 PM UTC+2, Eric Bidelman wrote: >> >> You're missing an outer <template> in your element definition, the one >> that polymer creates shadow dom from. It should not have any bindings on it. >> >> The stylesheet should go there as well so polymer can do the style >> shimming. Last time I checked, stylesheets inside a conditional template >> did not work. >> On Nov 16, 2014 1:56 AM, "Viktor Kojouharov" <[email protected]> wrote: >> >>> Hello, >>> >>> I'm getting a lot of errors when I tried switching to 0.5.1 (from >>> 0.4.2). Since I couldn't find any published list of changes, could anyone >>> tell me what I need to change in order to get back on track? >>> >>> I'm assuming all my custom elements will cause an error now. For >>> example, one of the first elements I can see looks broken, visually, and >>> that's right after I get the CustomElements.parser is undefined error (in >>> the latest chrome stable). >>> That element looks like this: >>> >>> https://github.com/urandom/readeef/blob/feefcb4b450d0be3a15339d1c8eb2a >>> e6a20c6795/templates/components/rf-login.tmpl >>> https://github.com/urandom/readeef/blob/feefcb4b450d0be3a15339d1c8eb2a >>> e6a20c6795/static/js/rf-login.js >>> >>> 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/93c4909c-004e-4d00-a6bf-e18dc634e65a% >>> 40googlegroups.com >>> <https://groups.google.com/d/msgid/polymer-dev/93c4909c-004e-4d00-a6bf-e18dc634e65a%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/0b945b68-6e83-4b75-a3b2-d8e4c45da18a%40googlegroups.com > <https://groups.google.com/d/msgid/polymer-dev/0b945b68-6e83-4b75-a3b2-d8e4c45da18a%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/CACGqRCBfDOs9xhrB5AUnPANUmd4VY4yrN%3Dbx%2BPq%2BmDMf1BXmAw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
