I can definitely say that HTML5 is not 100% reliable. This is for many reasons - mainly web browsers and supported functionality. For example, some functionality may be completely supported in Google Chrome or Maxthon, but not supported at all in Firefox or Internet Explorer.
A great way to get a good idea of what a specific browser supports is to check out HTML5test.com - if you view that page with all of the web browsers available, you'll see some scores that vary - greatly, in some case. For example, if I view that page with Chrome, I get a score of 503, with Internet explorer the score is 335.
If you'd like to check them all, just to see the differences, here's the download links for the most popular browsers:
So, unless you can restrict users to a specific web browser that supports HTML5 really well and you've confirmed that the feature you're using is supported in the content itself, it can be a bit tricky.
3 Replies
Hi Jay,
Just curious - is this related to the issue you posted earlier?
I responded to that thread requesting more information, but I'm not sure if you've seen it.
Thanks!
Thanks Christine! It was a similar post. I got your reply. It seems to only get glitchy in some instances.
Do you recommend that clients don't rely on strictly HTML5? It seems like it is not 100% reliable.
Jay
Hi Jay,
I can definitely say that HTML5 is not 100% reliable. This is for many reasons - mainly web browsers and supported functionality. For example, some functionality may be completely supported in Google Chrome or Maxthon, but not supported at all in Firefox or Internet Explorer.
A great way to get a good idea of what a specific browser supports is to check out HTML5test.com - if you view that page with all of the web browsers available, you'll see some scores that vary - greatly, in some case. For example, if I view that page with Chrome, I get a score of 503, with Internet explorer the score is 335.
If you'd like to check them all, just to see the differences, here's the download links for the most popular browsers:
So, unless you can restrict users to a specific web browser that supports HTML5 really well and you've confirmed that the feature you're using is supported in the content itself, it can be a bit tricky.
I hope that makes sense!
Let me know if you have any questions :)
Thanks,
Christine
This discussion is closed. You can start a new discussion or contact Articulate Support.