In discussing this with our clients and wider in the NZ Government Totara User Group we found an absence of awareness of the problem and its scale. It seems the core problem is that web & IT folk think Flash is a historical problem and L&D folk & LMS administrators don’t have much visibility of the mass of Flash content still inside their SCORM packages.
Particularly vulnerable are sites which have been using Totara for a few years and have in the past been tied to IE as an organisationally mandated browser. We’re calling it the Flash Apocalypse.
How to assess the scale of the problem?
We’ve built a Flash apocalypse report and released via the Moodle.org plug-in page: https://moodle.org/plugins/report_apocalypse
It works on Totara 2.9 and above and your partner shouldn’t have any trouble installing it in your site. For more information do read Dan Marsden’s blog post on this.
Flash EoL support - summary by browser:
- Chrome: currently sites require specific approval to run Flash on first visit. Mid-2019 Flash player is disabled.
- Firefox: currently users are choose which sites are allowed to use Flash. Mid-2019 Flash player is disabled.
- Internet Explorer: currently has no restrictions. Flash player will be removed mid-2019, but users will be able to re-install the Flash player plug-in. It is our view that many corporate IT departments will not allow this – don’t forget that from 2015, IE was officially 'discontinued' software. It has no new features and is only maintained on the versions of Windows it shipped with (albeit this includes Win7, and Win10).
- Edge: currently sites need to be trusted and then require specific approval to run Flash. Mid-2019 Flash player is disabled, but can be re-enabled but will require 'per-use' approval. It's not clear if Edge's re-release in 2019 as a Chrome distribution will impact this but its unlikely to improve Flash support.
Cheers
Austen