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

IE 11 support #109

Open
oliviertassinari opened this issue Dec 29, 2020 · 3 comments
Open

IE 11 support #109

oliviertassinari opened this issue Dec 29, 2020 · 3 comments

Comments

@oliviertassinari
Copy link

I have found that this dependency breaks support for projects relying on IE 11 investigating mui/material-ui#24167. For instance, see the arrow function returned in http://unpkg.com/rifm.

@istarkov
Copy link
Contributor

ie 11 was released at 2013, I remember that year I worked as an electrician inside deep Russia. Then few years after I became a web developer (just more money nothing else). Since that time I changed few places, got additional child, and IE 11 is still here :-) even I think it was dead few years ago ;-) We will take a look, just for fun, wtf is happening :-)

@MkMan
Copy link

MkMan commented Mar 26, 2021

If you exclude node_modules from being processed by your bundling tool (e.g. Webpack) making an exception for rifm might help. It worked for us 🙂

@MartinWebDev
Copy link

Would bump for this. Since mui v5 is only out recently, any projects still relying in mui v4 and using the date picker library encounter an IE11 crash due to inclusion of this library. Naturally I'd prefer that the picker library update to IE11 support and drop the use of rifm, as they should for mui4 compliance, but as they have closed the project I don't see that happening, so instead I've come to the "source" of the issue for help 😛

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants