Does webcomponents.js/webcomponents-lite.js actually work in Firefox/Safari/IE?

317 views
Skip to first unread message

andreas...@hotmail.de

unread,
Jul 17, 2015, 6:36:53 AM7/17/15
to polym...@googlegroups.com
Here's a site that I'm currently working on. Neither webcomponents.js nor webcomponents-lite.js are working in the browsers not supporting web components, so basically all except for Opera/Chrome.. Removing the unresolved from the body upon load shows that no custom elements are working. Do you need to add anything besides webcomponents.js to make the polyfills work?

andreas...@hotmail.de

unread,
Jul 18, 2015, 6:06:16 AM7/18/15
to polym...@googlegroups.com, andreas...@hotmail.de

I have uploaded a simpler demo of the non working polyfill. I guess this way it's easier to see if I am doing something wrong.  You should be seeing a paper-button and an iron-icon.

There are no custom packages installled on this site. The only two resources being loaded is the webcomponents polyfill and the vulcanized custom elements (+ the automatic js/css that's always loaded with meteor, including jquery).

Michael Giuffrida

unread,
Jul 18, 2015, 8:03:23 AM7/18/15
to andreas...@hotmail.de, polymer-dev
It looks like you're creating the <paper-button> dynamically in a script that loads before webcomponents-lite.min.js. Try loading your script after the web components polyfill.

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 polymer-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/446b3db9-8abd-48df-bc2d-74635a5eff59%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

andreas...@hotmail.de

unread,
Jul 19, 2015, 2:13:10 AM7/19/15
to polym...@googlegroups.com, andreas...@hotmail.de
Yes, you're right that the polyfill gets loaded after meteor loads templates and creates the DOM. But shouldn't any newly added element after that be working? Which is not the case.

Anyway, I'm trying to come up with a solution right now. Turns out it is not that easy to load a javascript file before the first DOM insertion in meteor.
Reply all
Reply to author
Forward
0 new messages