User interaction blocked while mp4 loading in IE 11....

[ryan schar]

Hello,

We are currently experiencing a weird phenomenon in IE 11.  Our Captivate project has a lot of mp4s which play fine in all browsers but IE 11.  In IE 11 the screen darkens when the video starts to play and there is a "Loading..." on top of the project ...  Furthermore, the screen is "locked" and you cant interact with the project. The video can be seen playing under the dark "layer", but the user cannot do anything.

I took a look at the DOM and it looks like this text and image stem from a DOM element with the id of "blockUserInteraction".  This seems to always be there, at least it's there in another project I looked at that doesn't have mp4s.

In all other browsers, there is no darkening of the screen and you can interact with the project while the video is playing.

Has anyone had this problem?

[markm7872831]

Hi Ryan,

No solution here, I'm afraid, but just to say that we have had the exact same issue. We specifically noticed when a pc using Windows 10 in IE11, but it could also appear on rare occasions on Windows 7 with IE11. All other browsers seemed fine. The issues occured on our own LMS, and on Scormcloud.

We spent a considerable amount of time with Adobe customer support, online, and over the phone, and nothing they or we tried could 100% fix it.

The issue was pretty random, so once Adobe support were able to view a video slide without issues a couple of times in Scormcloud , they deemed it solved...

Also worth noting that support blame everything EXCEPT Captivate for the issue. We ended up converting the course in Storyline 360 to get it to the client working.

Sorry for the doom and gloom, but I would love to find a solution!

Regards,

Mark

[markm7872831]

I forgot to add, the one thing we found that helped reduce the occurrence of the issue was to move the start of the video about a half second from the start of the timeline (we filled the blank at the start with an image of the first frame of the video). After doing this we could not get the issue to occur, and we thought it was a reasonable work-around. The client, however, still seemed to get the issue on a fairly frequent basis.