Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document mode IE10 on classic pages is giving problems with loading modules #1617

estruyf opened this issue Apr 9, 2018 · 3 comments


Copy link

@estruyf estruyf commented Apr 9, 2018


  • Question
  • Typo
  • Bug
  • Additional article idea

Expected or Desired Behavior

When running an SPFx web part on a classic page, it should not behave differently as in running it on the modern pages.

Observed Behavior

We noticed that on some tenants, the document mode of the classic pages is still on IE10. When this is the case, the web part returns the following error when loading it in IE11:

***Failed to load component "8c1ebe8b-1fd0-41cd-b00c-0131456dad64" (CustomWebPart).
Original error: ***Failed to load entry point from component "8c1ebe8b-1fd0-41cd-b00c-0131456dad64" (CustomWebPart).
Original error: Error loading https://component-id.invalid/8c1ebe8b-1fd0-41cd-b00c-0131456dad64_1.2.0
	https://component-id.invalid/8c1ebe8b-1fd0-41cd-b00c-0131456dad64_1.2.0 did not call System.register or AMD define. If loading a global module configure the global name via the meta exports property for script injection support.

   at t._generateErrorStackForIE (
   at t (
   at t (
   at e.buildErrorWithVerboseLog (
   at e.buildLoadComponentError (
   at Anonymous function (
   at T (
   at S (
   at j (
   at g (

I have tested the web part on a couple of tenant, most of them are running in IE=edge, but we also have a couple running in IE=10 (default Seattle.master is used, no customizations).

Loading the web part on a modern page works fine in IE11.


This comment has been minimized.

Copy link

@VesaJuvonen VesaJuvonen commented Apr 12, 2018

This seems to be related to the MC127395 where we informed that we are moving away from the IE10 mode. That admin message also contained instructions to handle ghosted master pages, which seems to be the case in the tenants where you can see the issue - as the rollout has been already completed.

Key information about the guidance is available from the following article, as we apparently are not exposing these messages outside of tenant admin message center -

Closing as there's really nothing else we can do here. If you, however, see the issue still after re-ghosting the master pages, please let us know.


This comment has been minimized.

Copy link

@bknagaraj bknagaraj commented Nov 9, 2018

We are using the solutions which you have provided but the issue is still not resolved.
We are getting the error even after making compatibility to IE 10.



This comment has been minimized.

Copy link

@bg6472 bg6472 commented Dec 7, 2018

Same here, still having the issue after setting compatibility to IE10

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
4 participants
You can’t perform that action at this time.