-
Notifications
You must be signed in to change notification settings - Fork 159
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
Safari 6 bug: "SYNTAX_ERR: DOM Exception 12: An invalid or illegal string was specified." #11
Comments
Will fix now. Thanks for the debugging effort :) On Thursday, February 20, 2014, Aseem Kishore notifications@github.com
|
Great to hear! Thanks for the awesomely fast response too. =) |
Thanks for the quick fix! Would you mind posting here whenever a new xdomain is available with this xhook update? Looking forward to it! |
Yep no worries, had to run, will work on that soon On Thu, Feb 20, 2014 at 9:46 AM, Aseem Kishore notifications@github.comwrote:
|
fix is up :) |
Seems to work great. Thank you! |
Good to hear :) On Thu, Feb 20, 2014 at 4:27 PM, Aseem Kishore notifications@github.comwrote:
|
Hi there,
Great work on xhook and xdomain. Really like the idea, and we're switching to it in an app I work on, to get rid of annoying CORS pre-flight requests for our JSON API.
Unfortunately, the switch has killed our app in Safari 6 with the following error:
I've debugged this error to this part of xhook:
k
is indeed"type"
, butrequest.type
isundefined
, and Safari 6 rejects settingxhr.responseType
toundefined
.It seems to work fine in Safari 7 (Mavericks), iOS 7 Mobile Safari, and Chrome.
We're on the latest xdomain 0.6.1 which contains xhook 1.1.4. We're using xdomain with jQuery 1.10, but not making Ajax calls directly; we're a Backbone app, so it's doing that automatically / under the hood.
Any ideas? Thanks for the help!
The text was updated successfully, but these errors were encountered: