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

IE9, unable to get property 'innerHTML' #3

Open
philwig opened this issue Dec 18, 2014 · 2 comments
Open

IE9, unable to get property 'innerHTML' #3

philwig opened this issue Dec 18, 2014 · 2 comments

Comments

@philwig
Copy link

philwig commented Dec 18, 2014

Anyone out there used this with IE9? It's ok with IE7 and IE8, but with IE9 I'm getting a crash on
FustyFlowFile iFrameLoaded, where it tries to access
$.iFrame.contentWindow.document.body.innerHTML

The $.iFrame.contentWindow.document exists, but things inside there are ropey and .body.innerHTML doesn't exist. That's the crash I'm getting. I can't avoid this: I need the contents of that network response, so I have to fix this, and I can't stub it out.

Sadly the IE11 IE9 emulator (!) crashes when I much about with this, probably because of the same IE "security" issues which are causing the IE9 problem. The Angular demo of fusty-flow appears to work in IE9.... but it doesn't actually do any upload, so that's no test.

Anyone... I need a way to get the innerHTML from an ie9 iframe I guess, and that needs to be in here, else IE9 doesn't work.

I think.

@AidasK
Copy link
Member

AidasK commented Dec 18, 2014

Maybe this is just IE11 emulator issue? Try to downgrade IE to IE10.

@philwig
Copy link
Author

philwig commented Dec 18, 2014

The original problem is a live system issue : it does not work on real IE9 (our ticket HA-077-30246).

It's as described above. The work around is for IE9 to pull your json from:
$.iFrame.contentWindow.document.documentElement.childNodes[0].data

This is confirmed to work on the IE11 emulator in IE9 mode, an IE9 Virtual machine (win 7), and a real IE11 user install (Win 7). I don't have time to patch that in for you, but that's the fix. Please leave issue where people can find it as it may help someone else.

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