CMS broken in IE11

[tech4him1]

- Do you want to request a feature or report a bug?
bug

- What is the current behavior?
The CMS seems to be broken in IE 11. The error deals with Symbol not being a valid type.

- If the current behavior is a bug, please provide the steps to reproduce.

- What is the expected behavior?
The CMS should work in IE 11.

- Please mention your CMS, node.js, and operating system version.

master

[tech4him1]

@erquhart Are you able to check into this as well, or are you not on Windows?

[talves]

Take a look at this solution babel/babel-preset-env#203 (comment)

It may be a better option for the babel setup. I will test it out also when I get a chance.

[tech4him1]

This will be much easier to implement after #702 can be done.

[erquhart]

After much discussion in Gitter, dropping IE11 support seems the proper path forward.

Reasons, in order of importance:

1. IE11 usage is even smaller than Safari now, under 4% globally, and shrinking.
2. We can't guarantee support without extensive, continual testing against that browser, which isn't proportionate to impact for our users, and our dependencies already vary in IE11 support.
3. Bundle size.

Lastly, and perhaps most tellingly, the CMS seems to have always been broken in IE11, and no one has reported it.

Documentation should be added about this decision with the PR for dropping support.

[t1merickson]

Where are you reading that stat on IE11? I'm seeing 11.99%, much higher than 4%

[tech4him1]

Just another note on this: the CMS has been broken in IE11 only since 0.3.1, released January 19. We might still have IE11 users that haven't upgraded yet (this fits enterprise usage as well).

[erquhart]

@neutyp http://gs.statcounter.com/

All of these stats services are based on whatever data that service has collected, in statcounter's case via their analytics script. It's the most used reference in my experience. What are you using?