Skip to content
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

Closed
ksons opened this issue Feb 3, 2015 · 1 comment
Closed

IE 11 Support #97

ksons opened this issue Feb 3, 2015 · 1 comment
Assignees
Milestone

Comments

@ksons
Copy link
Member

ksons commented Feb 3, 2015

No description provided.

@ksons ksons added this to the Release 4.9 milestone Feb 3, 2015
@csvurt csvurt self-assigned this Feb 17, 2015
csvurt added a commit that referenced this issue Feb 17, 2015
csvurt added a commit that referenced this issue Feb 17, 2015
csvurt added a commit that referenced this issue Feb 18, 2015
csvurt added a commit that referenced this issue Feb 19, 2015
csvurt added a commit that referenced this issue Feb 19, 2015
… the internal value and that seems to be consistent
csvurt added a commit that referenced this issue Feb 19, 2015
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.
csvurt added a commit that referenced this issue Feb 20, 2015
…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").
@csvurt
Copy link
Contributor

csvurt commented Feb 23, 2015

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.

@csvurt csvurt closed this as completed Mar 31, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants