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.

[ananth4u]

Description

Live Demo

http://jsbin.com/luhaxab/1/edit

Steps to Reproduce

Expected Results

Actual Results

Browsers Affected

• Chrome
• Firefox
• Edge
• Safari 9
• Safari 8
• IE 11

Versions

• Polymer: vX.X.X
• webcomponents: vX.X.X

[web-padawan]

1. I don't experience any problems with Shop in Firefox, neither Safari 9 (just a bit slow)
2. Safari 8 is no longer supported
3. your JSBin is not expected to work in IE11 and Safari 9 without babel transpilation.
4. there are several issues related to IE, especially this one

[TimvdLippe]

@frankiefu Could you confirm/deny that shop is working in IE and Edge?

[frankiefu]

Afaik It works in Edge and IE11. There was a Shady CSS issue but it should be fixed now.

[TimvdLippe]

I just tested Shop, it works in Firefox and Edge, but it does not work in IE. @frankiefu is investigating IE right now.

[frankiefu]

Just tested on the latest and found an issue when using es5-bundled build on IE11. I believe is related to this: https://github.com/Polymer/polymer-cli/issues/856

[web-padawan]

@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.

[TimvdLippe]

@web-padawan Done 😄

[LarsDenBakker]

We are running into the same issues for our app, and see the same error for the shop on IE11. Any update on this? It's blocking our Polymer 2 upgrade.

[web-padawan]

@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.

[keanulee]

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 PolymerElements/iron-location#93 for more details, but this doesn't affect the inital load.

[LarsDenBakker]

@keanulee strange, my experience is different. I will test again and make sure I am on the same version of the dependencies. Have you tried reloading the shop on IE11 a few times with console open?

[LarsDenBakker]

@keanulee I just did another test run, still having the same issues.

I am on a MacBook Pro running Sierra. I am using Windows 7 IE11 virtualbox image from https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/. I have had the same issue on a regular windows laptop as well.

I use the latest shop from the master branch of https://github.com/Polymer/shop. Polymer 2.0.2, webcomponentsjs 1.0.11, shadycss 1.0.5. Both the built and unbuilt version crash for me.

The crash happens more often with the dev tools opened. With the dev tools closed it happens around 1 out of 10. When opened sometimes the app does not load 8 out of 10 times.The app stops loading halfway when it happens:

No content:

No nav bar:

Errors vary, some snippets:

I know these errors are probably not related to the shop itself, but it is the best reference application that somewhat represents a real production application.

[Westbrook]

I'd suggest we collect the specific sub version of each IE11 instance people are running these tests against. Each OS has a different current and sometimes final version, and it's also hard to say whether the IE11 you are using is actually up to that level depending on the testing environment. I've seen very specific differences between various releases, even at the subversion and bug fix number, so it'll go a long way to clarifying this line of conversation.

[LarsDenBakker]

Good point. In my case I am running IE 11.0.9600.17420, Update version 11.0.14

[LarsDenBakker]

Update: Tested the same setup through browserstack VMs.

On Windows 7 with the same IE version as above I get the same errors. On Windows 10 IE 11.540.15063.0 Update Versions 11.0.45 I occasionally get the same error, but far less. In 50 tries I got it twice.

[keanulee]

@LarsDenBakker Try updating IE on the Win 7 VM - seems to be working fine with 11.0.9600.18792 / Update version 11.0.46

[dfreedm]

So, it seems that IE 11.0.9600.18792 is the most up to date version of IE 11 on Windows 7 (after updating with the 60+ updates that this VM I'm using needed), and the shop app seems to be working correctly after 10+ reloads.

IE 11.0.9600.17420 seems to be the version that shipped with Windows 7 SP1, from 2014.

[LarsDenBakker]

Thanks for the updates guys. After updating my VM to IE 11.0.9600.18792 it is definitely more stable, but about 1 in 20 loads I still ge 'unable to get property '__catchall' of undefined or null reference'. The other errors are gone though. Seems to be similar to: webcomponents/shadydom#168

What’s the official policy on IE11 sub versions? IE 11.0.9600.17420 seems to be installed on at least the laptops I tested at our company, and it’s the default on the VM provided by microsoft and browserstack as well.

[TimvdLippe]

I think we support the latest version of IE, just like the other browsers we support. I am inclined to close this particular issue in favor of webcomponents/shadydom#168 which seems to be the last issue with IE. @azakus maybe you can take a look at that one to fix all IE11 issues? It seems that it is related to slot (https://github.com/vaadin/vaadin-board/pull/69/files and webcomponents/shadydom#168 (comment))

[graynorton]

There's now a pull request open for webcomponents/shadydom#168. Let's get that integrated and see if it clears up the remaining failures on newer IE 11 releases (e.g. IE 11.0.9600.18792).

With respect to older releases, we’d appreciate any concrete information that our enterprise-focused partners can provide to help us better understand the real-world situation with respect to IE 11 subversion penetration. Hard data would be great, but anything more than the limited picture currently painted here would be welcomed.

There’s a significant cost involved in investigating and attempting to address sporadically reproducible issues on a version of IE that is now several years old and many official MS updates behind. Prioritizing this work will require compelling evidence that it’s required.

[graynorton]

@LarsDenBakker, we cut a new release of the polyfills last week with the fix for webcomponents/shadydom#168.

When you have a chance, can you test again to see what issues you're still observing on IE 11? Our expectation is that you'd see no errors in the latest IE 11 release. It would be great to confirm that, and also to get an updated report on what you see in older IE 11 releases now that this particular issue has been addressed.

Thanks!

[jab]

@graynorton, I just left what seems like a relevant comment at webcomponents/custom-elements#103 (comment) (seeing issues with IE11 on a PSK2-generated site) and then saw this - I'll follow here now as well. (Just shared access to the code for that site (https://uproxy.github.io/uproxy.org/) with you too in case it's helpful for testing)

[ggriffithsIDBS]

I found this thread through https://github.com/webcomponents/shadydom/issues/117

Im having issues on Edge/IE 11 where elements seem to be ignoring ShadowDOM styling in certain scenarios. In my screenshot it can be observed that the contents of the ShadowDOM for my element is outside of the HTML node.

Im not sure this is related or not. This seems to occur when I used the this.async utils in my Hybrid elements on Polymer 2.0

Im seeing this when running a hybrid element through the Polymer CLI using Polymer 2.1.1 and WebComponentsjs 1.0.14

[ruud]

@graynorton , I am a colleague of Lars Den Bakker. The webcomponents/shadydom#168 fixed the __catchall issues for us, but introduced a new one, unfortunately:

• Failed to execute 'insertBefore' on 'Node': The node before which the new node is to be inserted is not a child of this node. bower_components/webcomponentsjs/webcomponents-lite.js (bower_components/webcomponentsjs/webcomponents-lite.js) in insertBefore$1 at line 3535:9. This is using the unminified version of WebcomponentJS

This can be reproduced using the forked version of the shop: https://github.com/ruud/shop using IE 11.0.9600.17420 on Windows 7.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically closed after being marked stale. If you're still facing this problem with the above solution, please comment and we'll reopen!