-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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 #1339
Comments
I haven't tried earlier versions of IE, I shudder to think anyone still needing to support them. The new Edge browser in Windows 10 works great already. |
Does IE have weird issues with common URLs? |
@mistercrunch what do you mean by common URLs? I can navigate through all the pages within caravel just fine, it's just the visualizations that aren't fetching correctly. |
Did anyone else make any progress with this issue? From what I can tell, it's still happening... Steps to re-create:
When tested via Chrome, everything seems to work just fine. However, when tested from IE11 (from the same machine used to test via Chrome) I see the same error from the screenshot above. Note: Superset itself is not installed on Windows - I use my Windows machine only to test with different browsers. Superset is installed/running from OSX. I did a little bit of troubleshooting - there's definitely a difference in the URLs being requested between Chrome and IE. IE:
Chrome:
If it isn't obvious from the above extremely-long URL, the only difference in the above URLs is that, in IE, the URL begins with Any idea what could be causing this issue? Is there any other logs I can provide that might help to reproduce and/or diagnose? |
Does anyone have any thoughts on this one? Why would IE write a different URL than Chrome/Safari? |
@woel0007 it doesn't make much sense to me why IE would behave differently, I haven't had a chance to look closer at the code yet though. I do find it odd that @mistercrunch added the can't reproduce label, I think it is easily reproducible |
It's only easy to reproduce if you have access to a windows computer |
Yes true, having windows would be necessary. I've used https://github.com/xdissent/ievms in the past with success. |
Yep, I also have the issue with v0.14.0 |
is there any breakthrogh for this issue? |
slice.jsonEndpoint() missing the '/' when you use ie 11 browser, so you can rewrite the jsonEndpotint superset.js jsonEndpoint() { |
@wbsljh care to open a pull request please? |
@xrmx we recently met the same issue and had fixed it in our local repo. I've created PR #1821 for it. Please have a review at it, thanks. The issue is caused by a long standing IE issue. Superset's |
@rlei thanks! |
This should fix issue apache#1339. IE 11 and lower has a long standing issue: out-of-document element's pathname has no leading '/'. See https://connect.microsoft.com/IE/feedbackdetail/view/1002846/pathname-incorrect-for-out-of-document-elements And Superset's Slice.jsonEndpoint() method relies on pathname() to build JSON API URL for slices: ```javascript jsonEndpoint() { const parser = document.createElement('a'); parser.href = data.json_endpoint; let endpoint = parser.pathname + this.querystring(); endpoint += '&json=true'; endpoint += '&force=' + this.force; return endpoint; }, ``` `parser` above is exactly an out-of-document element. Therefore when running in IE <= 11, Superset would build wrong JSON endpoint URLs, hence the 404 errors for loading data for slices. This commit adds a simple workaround when leading '/' is missing in the value returned by pathname().
This should fix issue #1339. IE 11 and lower has a long standing issue: out-of-document element's pathname has no leading '/'. See https://connect.microsoft.com/IE/feedbackdetail/view/1002846/pathname-incorrect-for-out-of-document-elements And Superset's Slice.jsonEndpoint() method relies on pathname() to build JSON API URL for slices: ```javascript jsonEndpoint() { const parser = document.createElement('a'); parser.href = data.json_endpoint; let endpoint = parser.pathname + this.querystring(); endpoint += '&json=true'; endpoint += '&force=' + this.force; return endpoint; }, ``` `parser` above is exactly an out-of-document element. Therefore when running in IE <= 11, Superset would build wrong JSON endpoint URLs, hence the 404 errors for loading data for slices. This commit adds a simple workaround when leading '/' is missing in the value returned by pathname().
PR is merged, closing. |
apache#1355) This reverts commit 19f8f6a09c284de157c7179d43275ea2344b2372.
apache#1355) This reverts commit 19f8f6a09c284de157c7179d43275ea2344b2372.
apache#1355) This reverts commit 19f8f6a09c284de157c7179d43275ea2344b2372.
apache#1355) This reverts commit 19f8f6a09c284de157c7179d43275ea2344b2372.
The urls that are created to fetch the json data seem to be formed wrong for IE in both the Dashboard and Slice views.
For example:
The IE url vs Chrome url . Looks like it's missing
caravel/explore/table/3
as a prefix.This was discussed in #1323.
The text was updated successfully, but these errors were encountered: