-
Notifications
You must be signed in to change notification settings - Fork 489
Firefox: a.__shady is undefined #811
Comments
I'm continuing to see this same issue in the newest release (1.0.3). |
Same issue for me in Firefox. Seems to be related to #809 |
The latest version of the WebComponents polyfills has a bug which makes vaadin-board unusable in Firefox and IE11. Until the bug is fixed, the version of webcomponentsjs polyfills used to build the the precompiled vaadin board package has to be pinned (to avoid using the latest). The version of polymer is pinned as well but only because the latest version of polymer requires the latest version of webcomponentsjs. WebComponents polyfills issue: webcomponents/webcomponentsjs#811
…#110) The latest version of the WebComponents polyfills has a bug which makes vaadin-board unusable in Firefox and IE11. Until the bug is fixed, the version of webcomponentsjs polyfills used to build the the precompiled vaadin board package has to be pinned (to avoid using the latest). The version of polymer is pinned as well but only because the latest version of polymer requires the latest version of webcomponentsjs. WebComponents polyfills issue: webcomponents/webcomponentsjs#811
It worked for me the preset bundled build, after disabling MINIFY for html for Firefox. Chrome it was working fine.Problem faced by me even with the Polymer 2 starter kit. |
We were hoping that 1.0.3 would address this issue but apparently it has not. We'll be looking into and fixing this asap. |
@anirban-dutta Your workaround seems work fine on my side, but not working 100% case. The problem disappeared on Firefox and Edge once I adopted your workaround, but I got another problem on IE 11. Here is the browser console outputs: (just like as #518)
Do you have any idea of how to solve this problem? |
To add to @First87's comment, the errors related to custom elements being already defined do not appear when |
In the newest release (1.0.2) i get the following error in firefox while in version 1.0.1 everything is working:
The text was updated successfully, but these errors were encountered: