Wondering if anyone has decided to not allow courses to be viewed in HTML5 due to browser compatibility issues (I'm running into a lot of Firefox issues that I think are due to the HTML5 option being checked? Thinking perhaps it might help if I didn't have that checked...I don't know really, I'm grasping at straws trying to debug this monster.)
I guess I'm wondering what should I consider in this decision, other than the obvious of whether I want it to be viewed on an iThing. Is there any other reason to publish to HTML5?
I would expect only users who are viewing via a tablet to be using the HTML5 version I don't see any reason why a PC or Mac user would not view the flash version.
Only Chrome and Safari are supported browsers at the moment, other browsers will work to some degree.
Can you give me some examples of what goes wonky on browsers when the HTML5 option is turned ON? I'm trying to figure out if that's our issue.
We are experiencing a lot of instability in desktop Safari, even. Chrome seems fine-ish, depending on whether I view it from tempshare or from the client's server. Just wondering if killing HTML5 could at least cut down on a few of my issues.
Just wanted to post here that we solved the problem (for anyone in the future experiencing similar issues). More details of the issues and the solution here.
4 Replies
I would expect only users who are viewing via a tablet to be using the HTML5 version I don't see any reason why a PC or Mac user would not view the flash version.
Only Chrome and Safari are supported browsers at the moment, other browsers will work to some degree.
Currently, I don't output on HTML5 as the courses I have produced ran into all sorts of problems on Chrome and Safari.
However, I haven't published since the last couple of updates. I'm sure it is a lot more stable now.
Can you give me some examples of what goes wonky on browsers when the HTML5 option is turned ON? I'm trying to figure out if that's our issue.
We are experiencing a lot of instability in desktop Safari, even. Chrome seems fine-ish, depending on whether I view it from tempshare or from the client's server. Just wondering if killing HTML5 could at least cut down on a few of my issues.
Just wanted to post here that we solved the problem (for anyone in the future experiencing similar issues). More details of the issues and the solution here.
This discussion is closed. You can start a new discussion or contact Articulate Support.