On 2020/12/03 05:39:59, Justin Mclean <jus...@classsoftware.com> wrote:
> Hi,
>
> I notice on [1] it states this:
> In December, Chrome 55 will make HTML5 the default experience, except for
> sites which only support Flash
>
> Which I assume means a URL ending .swf?
>
> And on [2] it states:
> Since Adobe is no longer supporting Flash Player after the EOL Date, Adobe
> will block Flash content from running in Flash Player beginning January 12,
> 2021 to help secure users’ systems.
>
> If this is correct? If so that give a very limited window for "sites which
> only support Flash” to work.
>
> Does anyone know anything different?
>
> Thanks,
> Justin
>
> 1. https://blog.google/products/chrome/flash-and-chrome/
> 2. https://www.adobe.com/products/flashplayer/end-of-life.html
I'd be very interested in any insight into this ...
My current (developing) understanding is as follows:
1. Chrome will block loading the Flash plugin (1-Jan-2021)
2. Even if somehow loaded, the Flash player will not load swf. (12-Jan-2021)
Regarding point 1, as I understand it Chrome (Chromium?) calls home to get a
list of out-of-date, unacceptable/blockable plugins. And from 1/1/2021, this
list will contain all versions of Flash. So that means Chrome will not load
the plugin.
Regarding point 2, as I understand it, Adobe wants to cover itself because it
is no longer doing security updates, so it wants to stop any Flash content from
running on its players.
Our problem is that we have an intranet-ish Flex app which runs within Electron
and a local pepper flash player via DLL (ie. not downloading Flash). And we
thought we were safe from the apocalypse. We have suddenly woken up to the
fact that we are not, and that our application is just going to stop working.
It seems the only solution is to licence an alternative Flash plugin from
Harman (?sp)?
Does anyone have any other work around or insights?
