-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Internet Explorer 11 not supported #2677
Comments
@ArminVieweg I'm afraid I must close this for the same reasons explained in this comment:
|
Hey. Thanks for the response. I've asked the best Frontend guy I know and he did it. Basically two polyfills and a small change when including js files are required to make EAB work in Internet Explorer 11. Would you consider to merge a PR for this, when I provide it? |
I thank you for your proposal, but I prefer to not include that in the bundle. The reason is that, even if it may look like a small change now, it forces you to take that into account forever, so it may affect new features (e.g. #2670). |
I understand, nevermind. |
I'm interested in your fix cause I would like to run EasyAdmin on IE11 for a customer. Do you have it ? Thx ! |
I'm interested too @ArminVieweg 👍 please :) |
Actually, this fix works... But the performance is very very bad! The performance is so bad, that I have to find another solution. It is so stupid to optimize web applications for IE... But I think about taking the original AdminLTE styles and adjust them a little bit. Not sure how much work this will be. According to the description of EAB, it is based on AdminLTE. What hurts IE most is the |
I'm interested too @ArminVieweg can you explain how you fix it please :) |
Maybe it's more a missing feature, than a bug:
A blank Easy Admin Installation, with some default YAML configuration (no custom CSS or JS), looks like this in IE11:
The console also outputs some JS issues:
This makes in impossible to use EasyAdmin in IE11 (which is unfortunately still required, for some projects).
The text was updated successfully, but these errors were encountered: