Compatibility with IE11

I’m submitting a … (check one with “x”)

[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, post on Stackoverflow or Gitter

Current behavior

In IE 11 - Modal window does not open at all, console throws “Application error has occurred: TypeError: Object doesn’t support this action” message.

Expected behavior

Modal window should open.

Reproduction of the problem

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

Angular 8.2.9 and ngx-smart-modal version 7.2.1.

• Smart Modal version: 0.8.x

• Angular version: 2.0.x

• Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

• Language: [all | TypeScript X.X | ES6/7 | ES5]

[KrishnaSharmaCC]

@khylias , @DanWebb , i faced the same issue. Turns out IE10/11 do not supprt customevent See here. I fixed it by adding this polyfill in polyfills.ts. Hope this helps…

(function () {
    function CustomEvent ( event, params ) {
      params = params || { bubbles: false, cancelable: false, detail: undefined };
      const evt = document.createEvent( 'CustomEvent' );
      evt.initCustomEvent( event, params.bubbles, params.cancelable, params.detail );
      return evt;
     }
    CustomEvent.prototype = window['Event'].prototype;
    window['CustomEvent'] = <any>CustomEvent;
  })();

[DanWebb]

The project which I’m reproducing the error on has the following browserlist configuration > 0.5%, last 2 versions, Firefox ESR, not dead this includes IE11.

Everything else on the project continues to work on IE11, including ngx-smart-modal 7.1.1 or earlier.

I’m afraid this points to an incompatibility in the lib with IE11.

I’d happily be proved wrong if you could provide the config or polyfills you used to get it working during your tests, I’m sure that would be helpful to others trying to use the library too.

If not, I think at least the fact there’s an issue here should be acknowledged by re-opening this. Then, I’ll try investigating further when I get time to see if the issue can be pinpointed further because it’d be a shame to be stuck on 7.1.1 and miss out on all the great updates you guys keep releasing!