IE9 web objects

Hi Chris and welcome to Heroes,

I just tested this on my system and it worked perfectly:

Does the web object work with other sites or is it specific to the site that you're adding?

I figured out that when viewed in a separate window, the web object works correctly. It still fails when the presenter is embedded within an iframe (and all of my content is embedded). At least there's some progress and I can now maneuver IE 9 users to a new window to retain functionality. 

Hopefully the next step is solvable as well. Thanks for the help.

Hi Chris,

Out of curiosity, do you see the "iframe" in the link below:

http://www.hicom.net/~oedipus/wai/ua/tests/iframe1.html

It should load under item #7.

Yes, the iframe works. On my own site, the player loads correctly within the iframes. The problem is only visible with web objects. 

I put together a simple object page with almost no content on it to try to isolate the problem. However, the object fails whether its a simple page or a complicated one. The first picture is IE9 and the background with the blue swirl at the top is the background of the original presentation. It's not loading the web object at all. The second is the same presentation in chrome with the web object working correctly. The object works correctly in IE8, Firefox, Chrome, and if click compatibility mode, it begins working in IE9.

We have had the same issue with embedded web objects...only works when compatibility mode is clicked. And, attachments won't open unless compatibility mode is selected.

Did a little more testing and discovered that the embedded web objects load fine when I launch the course from the web server, but not when I launch the same course from within the LMS. Have asked LMS vendor to look at it too.

Hi Sarah,

Please submit a support case so that we can take a closer look at the issue:

http://www.articulate.com/support/contact/

I was half way able to solve the problem for myself. IE9 standards mode sets the child doctypes to be the same as the parent. However, it appears that web objects with a different doctype cause some problems. When I set the parent page, the articulate player.html, and the child web object page to all contain the same doctype, the object began working again. 

I realized that my solution wasn't actually using standards mode. The doctype change was triggering IE9 to jump into quirk mode which allowed the web objects to run.