-
Notifications
You must be signed in to change notification settings - Fork 1
Site does not load (whitescreen) on IE11 #29
Comments
I tried casting the strings via So I tried updating to the master version of Vulcanize, but that didn't help at all. The root cause seems to be that it is trying to register custom elements before the template polyfill is fully initialized and available. This seems like an obvious issue that Vulcanize is designed to avoid, but it's not. Vulcanize also seems to be in a bad state atm with the last 3 releases (1.14.9-1.4.11) being unpublished from npm due to bugs and no new release since 1.4.8 in March 2016. It also has no commits since July 2016, so it would seem that it is no longer supported with the polymer-cli being preferred? Other related issues: It may be fixed in a newer version of Polymer, but that brings with it tons of breaking changes that we don't have time to resolve. We're already on the latest polyfills ( |
I've also verified that the fix for Chrome breaking due to web-animations-js didn't cause this regression. |
https://ohiodevfest.com/ also has this problem on failing to load on IE11. |
https://devfest.gdgseattle.org/ does not have this issue since they are based on the latest Hoverboard 1.x+ which uses polymer-cli and a newer version of Polymer. IE11 is still really slow, but it at least renders the site. Unfortunately, there are major breaking changes and the site has to almost be rebuilt from scratch to move to this version. That's not something we're looking forward to when the conference is in a week. |
I’m going to just show the following message on IE browsers rather than spend more time (already hours spent) trying to support them this close to the event: |
915c995 displays the error for IE only, not Edge. |
It looks like an exception is causing the site to just be a white screen and fail to load on IE11.
The text was updated successfully, but these errors were encountered: