polymer: Polymer 2.0 having Browser compatibility issue with IE11,IEedge & Mozilla. The SHOP Progressive app Demo itself not rendering properly in other browsers except Chrome even though enabled Pollyfills. Could any one can help us on this issue.. As we are planing to use Polymer 2.0 to build web application so kindly advice.

Update: For local development Shop is working on IE11, Edge, and Firefox with the latest releases of polymer, shadycss, and webcomponentsjs:

├─┬ polymer#2.0.2
│ ├── shadycss#1.0.5
│ └── webcomponentsjs#1.0.11

polymer serve can be used to serve the shop/ directory directly, or you can statically serve the contents of build/es5-bundled/ after doing a polymer build.

For deployment, there is a small issue with iron-location (used by app-route) that is affecting IE11 when Shop is on a host with no specified port. See https://github.com/PolymerElements/iron-location/issues/93 for more details, but this doesn’t affect the inital load.

@tjsavage @sorvell as you can see, many users complain here and there (mostly in slack channel) about poor IE 11 support for 2.0. There are several issues which look critical once the app grows:

• not inspectable elements opened 23 mar
• shadydom performance opened 25 may

And there are more, e. g. broken Promise polyfill issue which was fixed recently.

I must say it is still much better than it used to be as of 0.5, but not very much progress since 1.x (where occasional crashes happen as well as weird errors like #4455).

So, is there any official opinion regarding IE11 support? How much should it beconsidered stable? The blog post summarizing known limitations (no way for <template> in <table> etc) and bugs with possible workarounds would be nice.

@web-padawan Done 😄

@TimvdLippe would you mind adding IE11 label for this repo BTW? There is an ie10 one which could be removed (since it is no longer supported)

Tagging all IE11 issues would help us developers to check if the bug is already filed, as well as to decide whether 2.0 is really production ready or not.