"Blank screen" in newest Mozilla Firefox about securesha.re-client HOT 7 CLOSED

Thanks - I'm sure this is probably a Polymer incompatibility. I'll look into it. I've been meaning to do some big upgrades to the site. The Polymer is (relatively) ancient.

from securesha.re-client.

Cool. Waiting for your update.

from securesha.re-client.

Hi, Any news about the incoming update?

from securesha.re-client.

Hey - sorry, been traveling, just haven't had the time. All it should take is an update of the lib and some testing to make sure the site still works. I think there may have been an API change or two. I would be very happy to accept a PR... otherwise, I'll get to it within the next few weeks. Sorry for the outage.

from securesha.re-client.

+1 on this!

from securesha.re-client.

Fixed this in 59035c0. The major changes were a difference in bower paths, css :host specification and style scoping, and the modification of event syntax from on-click="handler" to on-click="{{handler}}". Once all the modules were up to date it went smoothly.

It looks as though much of the degradation in the app over the last few months has to do with Chrome partially implementing much of the web components spec, making web components into much more discrete pieces than is possible with a polyfill. For example, I now have to include the main stylesheet (just bootstrap) in each component that relies on those styles, as page styles no longer bleed in. That certainly hints that a different application structure may be in order.

I've updated https://securesha.re and we're back up & running.

from securesha.re-client.

Nice ! Thanks for the fix.

from securesha.re-client.