Polymer app doesn't work at all in Firefox

[pie.o...@gmail.com]

I have built a simple app in Polymer and it works great in Chrome but fails miserably i Firefox due to being extremely slow and I get multiple A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.before the page even loads at all.

My page is located at http://raxa.se (production, minified, inlined and similar) and my code can be seen at https://github.com/re222dv/1DV449_re222dv/tree/master/Laboration3/client

The above warning happens both in development and production mode.

Do anyone have any ideas of things I should test or do?

[Rob Dodson]

Hm, I can't even get it to load in Firefox. I can't say if it's a bug or something wrong in the architecture. A reduced test case would help. Is it possible to strip out features of the site until it loads again and add them back until you can isolate what's breaking?

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/fa851fde-3545-4ad4-a2f6-32adbb46e3df%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Rasmus]

Thank you! That's something that I clearly should have thought of, I found the error very quickly using your debug technique and is now a bit ashamed :(

The error is at https://github.com/re222dv/1DV449_re222dv/blob/eebacf3a78b4e9e2b947bf8cf97546f065d749a1/Laboration3/client/app/elements/laboration-three/laboration-three.html#L46

where I return an array in a databound property. Obviously I return a new instance every time the property is called, which in Firefox seems to be all the time.

The error is of course very easy to fix and something I should have spotted, however as it works perfectly in Chrome I didn't... I guess Chrome optimizes that one to only ever create a single instance of the array that obviously never changes.

In Angular one receives a warning when a databound proerty never stabilizes and Angular stops caring about that property. Maybe something similar could be implemented in Polymer too to help development?

--

Rasmus

[Rob Dodson]

hm that's an interesting idea. If you're able to create a really tiny reproducible test case we could open a ticket for it and see if the engineering team is interested?