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

Internet Explorer 11 does not load Apache superset URL #9022

Closed
MahsaSeifikar opened this issue Jan 25, 2020 · 7 comments
Closed

Internet Explorer 11 does not load Apache superset URL #9022

MahsaSeifikar opened this issue Jan 25, 2020 · 7 comments
Labels
.pinned Draws attention

Comments

@MahsaSeifikar
Copy link

MahsaSeifikar commented Jan 25, 2020

A clear and concise description of what the bug is.
I run the apache superset on Centos 7 with a docker image. When I enter the apache superset URL in IE11 and the main page does not load after login!

(please complete the following information):

  • superset version: 0.35.1
  • python version: 3.6
  • node.js version: 8.17
  • npm version: 6.13
@MahsaSeifikar MahsaSeifikar changed the title Internet Explorer 11 does not load Apache superset Internet Explorer 11 does not load Apache superset URL Jan 25, 2020
@stale
Copy link

stale bot commented Mar 26, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.

@stale stale bot added the inactive Inactive for >= 30 days label Mar 26, 2020
@stale stale bot closed this as completed Apr 2, 2020
@keehl1213
Copy link

I got the same error. Is there any solution?

@MahsaSeifikar
Copy link
Author

@keehl1213 I haven't solved the problem yet!

@stale stale bot removed the inactive Inactive for >= 30 days label Aug 7, 2020
@swanitzek
Copy link

Are there any information available what is required to get the Internet Explorer working with Superset?

@MahsaSeifikar
Copy link
Author

@swanitzek If you find any please share here.

@SaiManojG
Copy link

SaiManojG commented Dec 9, 2020

I have to support superset in IE11, as there is no official way found, i have tried the below steps and still got no luck :(

  1. installed react-app-polyfill & babel-polyfill packages in (superset-frontend) and imported them at the very top in index files as below

import 'babel-polyfill';
import 'react-app-polyfill/ie11';
import 'react-app-polyfill/stable';

  1. added "not dead" in browserslist section in package.json (superset-frontend)

  2. added target: "es5" in tsconfig.json (superset-frontend)

also builded the project with above changes and still iam not able to run superset in IE.

iam getting login screen and then after entering the login credentials, iam getting infinite loading screen and an error stating "Expected :" from welcome.hash.entry.js

please let us know if there any workarounds for the IE support? @mistercrunch

also did you find any way to support superset in IE..? @MahsaSeifikar @swanitzek @keehl1213

Thanks in advance..

@keehl1213
Copy link

I have to support superset in IE11, as there is no official way found, i have tried the below steps and still got no luck :(

  1. installed react-app-polyfill & babel-polyfill packages in (superset-frontend) and imported them at the very top in index files as below

import 'babel-polyfill';
import 'react-app-polyfill/ie11';
import 'react-app-polyfill/stable';

  1. added "not dead" in browserslist section in package.json (superset-frontend)
  2. added target: "es5" in tsconfig.json (superset-frontend)

also builded the project with above changes and still iam not able to run superset in IE.

iam getting login screen and then after entering the login credentials, iam getting infinite loading screen and an error stating "Expected :" from welcome.hash.entry.js

please let us know if there any workarounds for the IE support? @mistercrunch

also did you find any way to support superset in IE..? @MahsaSeifikar @swanitzek @keehl1213

Thanks in advance..

I finally gave up supporting IE11 and legacy Edge because of this announcement.
I suggest you only support chromium-based Edge since IE11 and legacy edge both have security problems.

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

No branches or pull requests

5 participants