-
Notifications
You must be signed in to change notification settings - Fork 25
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 #97
Comments
…n the way IE11 handles Function.toString
…E 11 doesn't support it in these cases
… the internal value and that seems to be consistent
IE automatically lowercases all attribute names when doctype is HTML. This is a small bandaid to fix setAttribute for fields like fieldOfView in IE until we normalize all attribute names to be lowercase.
…weird behavior with document.URL in IE In IE document.URL always holds the same value as window.location.href, even if the document was loaded from an external source with an HTTP request. Without explicitly storing the original request URL in the response we have no way of resolving relative URIs inside the returned XMLDocument (ie. src="asset.xml#asset").
IE 11 support should be complete now. There's one issue left (and as a result one failed test), listeners of the "onload" event added to the XML3D element as an attribute will be called twice in XHTML documents. Because we plan to phase out XHTML in the future, and because this only affects IE 11 in a non-critical way, we've decided to leave this as a known issue rather than build in an IE specific workaround. |
No description provided.
The text was updated successfully, but these errors were encountered: