Re: Java plugin phase out timeline

Sorry, I forgot to answer your other question:

On 7/18/16 3:54 PM, Suril Patel wrote:
> So looking at what you shared - effective March 7th, the patients who's FF
> automatically updates would not be able to sign in.
>
> 1)  Is there a transitional version planned prior to that, where upon
> update - all plugins default to a blacklist?  In other words, is there
> suppose a v51 - where upon update, VidyoWeb gets blacklisted and we need to
> send out instructions to patients to unblock or whitelist VidyoWeb?   (We
> are investigating a long term solution that is not dependent on NPAPI - but
> I just want to understand, in case management wants keep the NPAPI track
> open until the end - how we can manage messaging to users on the site and
> appropriately detect the browser to handle the various scenarios here)

As far as I understand, there will not be a transitional Firefox release 
that blacklists plugins by default. The plan is to support all plugins 
in 51 and then remove them in 52.

If Mozilla does remove NPAPI in Firefox 52 (and WebRTC VidyoWeb is not 
an option), you could ask Firefox users to stick with Firefox 51, but 
that workaround is probably no simpler than asking them to install 
Firefox ESR. The simplest solution would probably be to recommend they 
log into Chrome for video conferencing.

btw, if you find problems with VidyoWeb's WebRTC in Firefox that do not 
affect Chrome, please let us/me know! We want to make sure that option 
works seamlessly for everyone.

chris