Yes, I have updated my flash but the larger problem is we can't control our customers and whether they have updated their flash/browser except to provide a link and suggestion for them to update.
I think the best method for user experience is to prevent presentation_html5.html and/or try to understand why our presentation doesn't render in that version?
In the meantime, we are disabling that version from the output.
I appreciate the reply and the link you referenced.
It would likely work if you were able to launch it in a different browser such as Chrome or Safari (on a Mac). You can see the browsers we support for Flash vs. HTML5 here.
I am getting ready to post a new thread related to the problematic implementation of Studio 13 Presenter and Quizmaker with respect to "supported platforms" and I found this thread. Here is a prime example of what I consider to be a major Articulate failing. An implementor is posting about quizmaker. The problem is that Firefox in flash is supported. Firefox in HTML 5 is not supported; however, having to deal with end user browsers is not dealt with by the software. Either Articulate should support HTML5 on Firefox or it should put up an error message telling the end user that they need to turn on Flash if they want to use Firefox.
Same goes for Androids. And iPads. And all the other platforms where the software appears to run just fine without any warning until it doesn't. Until it locked up with data corruptions in quizmaker. Until it doesn't resume properly and chooses to not request current updates from the LMS and just tells the LMS to reset the data.
Then the feedback is to force the server to use TinCan API. Or force the server to support SCORM over AICC. Or to force the user/implementors to deal with tracking the nuances of the browsers on which the application should or should not run. Or better yet, dump Presenter/Quizmaker and migrate your entire library to Storyline.
Its time for Articulate to finally get around to supporting HTML 5 on all platforms or to issue errors that users can see.
It looks like you're discussing these issues with Emily as a part of your support case, so I'll defer to her for the continued assistance on these issues and what you're experiencing.
As far as continued and increased support for HTML5 across a number of platforms, our team is continuing to look at other options and avenues and want to ensure that it's the same experience across browsers. Since not all the browsers have implemented the same HTML5 standards our support is still limited to the browsers mentioned in our system requirements doc - and you may also want to look at a site such as HTML5test.com which does a good job comparing the different browsers to one another.
5 Replies
Hi Bryan,
There isn't a way to disable the redirect, as it's built into your Presenter output - but you could set Firefox up to allow for Flash content.
Yes, I have updated my flash but the larger problem is we can't control our customers and whether they have updated their flash/browser except to provide a link and suggestion for them to update.
I think the best method for user experience is to prevent presentation_html5.html and/or try to understand why our presentation doesn't render in that version?
In the meantime, we are disabling that version from the output.
I appreciate the reply and the link you referenced.
BB
Hi Bryan,
It would likely work if you were able to launch it in a different browser such as Chrome or Safari (on a Mac). You can see the browsers we support for Flash vs. HTML5 here.
I am getting ready to post a new thread related to the problematic implementation of Studio 13 Presenter and Quizmaker with respect to "supported platforms" and I found this thread. Here is a prime example of what I consider to be a major Articulate failing. An implementor is posting about quizmaker. The problem is that Firefox in flash is supported. Firefox in HTML 5 is not supported; however, having to deal with end user browsers is not dealt with by the software. Either Articulate should support HTML5 on Firefox or it should put up an error message telling the end user that they need to turn on Flash if they want to use Firefox.
Same goes for Androids. And iPads. And all the other platforms where the software appears to run just fine without any warning until it doesn't. Until it locked up with data corruptions in quizmaker. Until it doesn't resume properly and chooses to not request current updates from the LMS and just tells the LMS to reset the data.
Then the feedback is to force the server to use TinCan API. Or force the server to support SCORM over AICC. Or to force the user/implementors to deal with tracking the nuances of the browsers on which the application should or should not run. Or better yet, dump Presenter/Quizmaker and migrate your entire library to Storyline.
Its time for Articulate to finally get around to supporting HTML 5 on all platforms or to issue errors that users can see.
Hi Deborah,
It looks like you're discussing these issues with Emily as a part of your support case, so I'll defer to her for the continued assistance on these issues and what you're experiencing.
As far as continued and increased support for HTML5 across a number of platforms, our team is continuing to look at other options and avenues and want to ensure that it's the same experience across browsers. Since not all the browsers have implemented the same HTML5 standards our support is still limited to the browsers mentioned in our system requirements doc - and you may also want to look at a site such as HTML5test.com which does a good job comparing the different browsers to one another.
This discussion is closed. You can start a new discussion or contact Articulate Support.