We are using a labeled graphic as a tab in our presenter to give users an over view of the player properties. However, the labels do not work with HTML5 with chrome or other browsers.
Our HTML5 support would be for Chrome alone on the PC desktop, and Safari also on the Mac, and although I don't see the same behavior as you described, I'm not able to click on the other markers - so I think we'd want to take a look at the Presenter package as a whole in terms of how this is set up. Can you share it here with us?
Apologies, yes this is using chrome. As our users are all across the country and use many different means we are trying to get something that works the same for all of them.
As an aside, published for the web separately this interaction works as it supposed to in IE,Chrome, and Firefox.
After some thought, the random showing of presenter slides could have been caused by it being run from the C: drive of my computer.
Thanks and I checked in on your case and it seems that Victor was able to recreate the issue in your initial files, and then determined it may have been an element of corruption associated with the Engage file, so he recreated it for you. It seems that one worked as expected and he offered a reminder to only work on project files locally.
Glad he was able to assist and let us know if you need anything else!
3 Replies
Hi Dan,
Our HTML5 support would be for Chrome alone on the PC desktop, and Safari also on the Mac, and although I don't see the same behavior as you described, I'm not able to click on the other markers - so I think we'd want to take a look at the Presenter package as a whole in terms of how this is set up. Can you share it here with us?
Apologies, yes this is using chrome. As our users are all across the country and use many different means we are trying to get something that works the same for all of them.
As an aside, published for the web separately this interaction works as it supposed to in IE,Chrome, and Firefox.
After some thought, the random showing of presenter slides could have been caused by it being run from the C: drive of my computer.
Same interaction as in this package as well. Sent the other package to support as suggested, Case Number: 00560353 for reference.
Hi Dan,
Thanks and I checked in on your case and it seems that Victor was able to recreate the issue in your initial files, and then determined it may have been an element of corruption associated with the Engage file, so he recreated it for you. It seems that one worked as expected and he offered a reminder to only work on project files locally.
Glad he was able to assist and let us know if you need anything else!
This discussion is closed. You can start a new discussion or contact Articulate Support.