Users are using Internet Explorer to visit smash and some features crash

At least for now, it could be good idea to avoid arrow functions.

mentioned in merge request !198 (merged)

added Done high priority and removed To Do labels

removed high priority label

If you want to use ES2015 or higher maybe we should introduce babelify in the future?

I consider it would be a bit of overwork since it requires more stuff server side. I would just write the app requirements which are not only ES6 but might be HTML5 or CSS3 as well. The same way some apps require certain hardware or operating system we could require the use of a modern browser such as Chrome or Firefox (or even Edge, despite Microsoft is moving to Chromium as well). Right now it seems they had no problem switching to one of those.

In fact, after removing the arrow functions I remembered that some libraries (or even us) might use JavaScript promises which are also ES6.

Usually the libraries provide releases that are JS 5 compatible.

Yes but I think is not worth the effort to work with server side stuff like babelify just in case some people use IE. You know the project better, do you consider this a priority or could we request that a modern browser is used? Either of the currently maintained or updated browsers could do it but IE is no longer maintained, only for security patches.

I agree that IE doesn't need to be supported.

Babelify is not only server side software - you can transpile the JS before releasing (in command similar to collectstatic in deployment).

But for me this is low priority.

added enhancement label and removed bug label

Should we then consider this Issue as resolved?

Before resolving it I would do two things:

• let's decide which browser we support. I would go for Firefox, Chrome, Safari, we can decide the minimal version, but I'm not sure which
• when the front end detects browser that is not supported or detect old version show a warning that it's not supported

Are these new requirements still a 0.12.2 issue or should we move the issue to the 0.13 milestone?

Sure we can move it to 0.13.0, it's no longer bug fixing

closed

changed milestone to %0.13.0