fix for bad ie pathname implementation #32
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
reopen if this is still an issue |
|
Why hasn't this commit been merged? I think it fixes the issue. |
|
I'm experiencing this issue as well. It would be nice to have this solution applied IMO |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
I tried to figure out for one day now, what was causing problems on IE9. I just discovered that IE handles
el.pathnamequite different, see this question on stackoverflow.This is a quick fix. I did not test this widely across browsers.
Could someone test this on other Internet Explorer versions? I'd like to include it upstream, but this should definitely be verified.