IE11 bug when absolute URL is used #163
Comments
zipper
added a commit
to zipper/nette.ajax.js
that referenced
this issue
May 27, 2019
- do not use new URL constructor, use custom function instead - changed condition whether to use ajax when absolute URL is used
zipper
added a commit
to zipper/nette.ajax.js
that referenced
this issue
May 30, 2019
- do not use new URL constructor, use custom function instead - changed condition whether to use ajax when absolute URL is used
zipper
added a commit
to zipper/nette.ajax.js
that referenced
this issue
May 30, 2019
- do not use new URL constructor, use custom function instead - changed condition whether to use ajax when absolute URL is used
|
I believe I've solved this by PR #164. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When absolute URL is used on AJAX link, there is
new URL()used, which is not supported in IE11.More over, when the URL is parsed, the regular expression below doesn't make any sense (or does it?):
pathnameproperty used in string, which never should contain port number, so checking the port number is unnecessary. Port number would be inhost(or even better inport)./inpathname, even though thepathnamemight be missing in link. So even URL eg. "http://www.example.com#foo" will returnpathnameequal to/. Therefore,parsedUrl['pathname'] + parsedUrl['search'] + parsedUrl['hash']may never begin with#, but always with/.So in my opinion, the correct condition should be if
pathnamefrom currentlocationis the same as inparsedUrl,searchis the same and hash is specified inparsedUrl. If so, return false, otherwise return true. Is that correct or am I missing something?The text was updated successfully, but these errors were encountered: