The latest versions of modern browsers such as Google Chrome and Firefox have begun blocking flash content by default.
What is Happening with Flash in Chrome?
On December 6th (2016), Google will release Chrome 55, giving more power to visitors of your site, allowing them to make a choice if they want to enable Flash or not by clicking the Flash object in the page. Previously, Flash became click-to-play when it was below a size threshold; in Chrome 55, Flash objects will not load if the user dismisses them. Chrome tracks the user’s decision per domain.
Our most recent version release, MediaCP 2.2.0.4 introduces some core changes to promote the use of HLS streaming technologies to be HTML 5 compatible including:
- Updating of JWPlayer to the latest version 7.10 (REQUIRES Premium to load HLS content)
- Updating of Flow Player to the latest version supporting HLS (FREE, no registration required)
- Added new Wowza Player (Free, requires registration) which supports HLS
- Embed code now prioritising the playlist.m3u8 file before the RTMP stream
- Wowza Streaming Engine CORS is enabled on all streaming services
You will note in the above list, that JWPlayer requires a Premium license to load HLS content and this is the biggest issue our customers will face with the upgrade. Unfortunately we are faced with an ultimatum to either:
- Set JWPlayer primary: flash, which is free however blocks many users from accessing streaming content as flash is being slowly blocked by modern browsers; or
- Set JWPlayer primary: html5, which requires a Premium JW Player license
Eventually, flash will be blocked by default for all Chrome and Firefox users so it makes sense to move to HTML5 early. If you do not wish to pay for a JW Player premium license key, we have added the Free Flow Player and Wowza Player alternatives into the latest release.
