Quantcast

Java plugin phase out timeline

classic Classic list List threaded Threaded
63 messages Options
1234
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Java plugin phase out timeline

Chris Peterson-12
On 1/2/2017 8:44 AM, [hidden email] wrote:
>> > How can I - based on browser user agent detection - tell the difference between a version 52 *release* and a version 52 *ESR* ?
>> > I want to guide the end user depending on the browser capability to support the Java plug-in.
>> > Thanks
>> > Peter
> I seem to have found the answer in https://bugzilla.mozilla.org/show_bug.cgi?id=1269807#c83 :
> "Unfortunately, you can't detect ESR from the server side because both ESR and non-ESR releases have the same User-Agent string."

As noted, there is no officially supported method to differentiate
between the ESR and regular non-ESR versions of Firefox 52 using
User-Agent detection on the server side. However, non-ESR Firefox 52 is
dropping support for Windows XP and Vista, while ESR 52 will continue to
support XP and Vista. So if a User-Agent string says the user is running
Firefox 52 and XP or Vista, then they are running ESR 52.

On the client side, you can make a good guess. If navigator.plugins has
zero or exactly one entry and it is Flash, then there is a good chance
the user is running ESR 52, since many people have other plugins such as
Adobe Acrobat Reader that would show up in ESR 52.
_______________________________________________
dev-tech-plugins mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-plugins
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Java plugin phase out timeline

peter.w.madsen
In reply to this post by Chris Peterson-12
> Firefox 52 ESR version will support Java until 2018 Q1. IE on Windows
> and Safari on macOS continue to support Java for now, too. I doubt
> Microsoft will ever remove Java support from IE, so it will likely be a
> long-term option.
>
> chris

Would you be able share information - here or in private communication - about how soon Release 52 will take effect in the end user experience?
- What time of the day will Release 52 be released in Central Europe Time zone (CET)?
- What will trigger the auto-update to v52 by end user (download/install/run) - Process in background? Launching Firefox? Opening new tab? Refresh?
- Is there any server side mechanism from you that will delay the update (by days/weeks) beyond the end user trigger to reduce the peak load on your server?

We are running a web service based on a Java applet, and we currently see some 10k unique users per day using Firefox v50 (90% Windows, 10% Mac) and a few v49, v48 and v47.
It is now clear that we will not be able to replace the Java applet in time before the release of Firefox v52 (March 7).
We have to prepare our support team for helping our Firefox users when Java stops working for them because of update to v52.
FYI: Our user agent statistics from December 2016 (total) shows v50.0 and practically no v50.1 though v50.1 was released in mid-December.

Thanks
Peter
_______________________________________________
dev-tech-plugins mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-plugins
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Java plugin phase out timeline

Chris Peterson-12
On 1/12/2017 4:34 AM, [hidden email] wrote:
> Would you be able share information - here or in private communication - about how soon Release 52 will take effect in the end user experience?
> - What time of the day will Release 52 be released in Central Europe Time zone (CET)?
> - What will trigger the auto-update to v52 by end user (download/install/run) - Process in background? Launching Firefox? Opening new tab? Refresh?
> - Is there any server side mechanism from you that will delay the update (by days/weeks) beyond the end user trigger to reduce the peak load on your server?

March 7 is the official release date for Firefox 52, but Mozilla uses
server-side throttling to slowly update only a few thousand users over
the first week or so. If we don't see any new bug reports from those
users, we unthrottle the update and all other users should automatically
receive the update within 24 hours of the next time they launch Firefox.
(Firefox pings the update server every 24 hours.)


> We are running a web service based on a Java applet, and we currently see some 10k unique users per day using Firefox v50 (90% Windows, 10% Mac) and a few v49, v48 and v47.
> It is now clear that we will not be able to replace the Java applet in time before the release of Firefox v52 (March 7).
> We have to prepare our support team for helping our Firefox users when Java stops working for them because of update to v52.
> FYI: Our user agent statistics from December 2016 (total) shows v50.0 and practically no v50.1 though v50.1 was released in mid-December.

New updates may get downloaded but not installed if users don't restart
their browser periodically. Also, there are some long-standing Firefox
bugs that cause some users to get "stuck" on older Firefox versions.
Anti-virus software can cause update problems, too.

Options for using Java after Firefox 52 release are switching to the
Firefox "ESR" version (Extended Support Release [1]) or using IE on
Windows and Safari on Mac.

[1] https://www.mozilla.org/en-US/firefox/organizations/
_______________________________________________
dev-tech-plugins mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-plugins
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Java plugin phase out timeline

peter.w.madsen
We appreciate your fast and detailed answer – it’s mission critical to us.
We have identified the same workaround options (IE and FF ESR) but in our experience, Safari is not a practical alternative for using Java. It requires an extra setting per web site – which is complicated to the average user – to allow write access to the file system for Java. Moreover it seems like Apple has now blocked that since Safari v 10.0.2 (released December 13, 2016), which is included in MAC OS updates.
So for our Mac (and Linux btw) users, Firefox ESR remains the only option for a browser with Java support.
/Peter
_______________________________________________
dev-tech-plugins mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-plugins
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Java plugin phase out timeline

peter.w.madsen
In reply to this post by Chris Peterson-12
Is it a fair assumption that you will not 'unthrottle' Firefox 52 before business hours (PST) on Monday, March 13 ?
Thanks,
Peter
_______________________________________________
dev-tech-plugins mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-plugins
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Java plugin phase out timeline

Benjamin Smedberg
No, that is not a fair assumption. We sometimes unthrottle as soon as
Thursday or Friday of release week, if there are no alerts from the
incoming data.

--BDS

On Fri, Jan 13, 2017 at 9:37 AM, <[hidden email]> wrote:

> Is it a fair assumption that you will not 'unthrottle' Firefox 52 before
> business hours (PST) on Monday, March 13 ?
> Thanks,
> Peter
> _______________________________________________
> dev-tech-plugins mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-tech-plugins
>
_______________________________________________
dev-tech-plugins mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-plugins
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Java plugin phase out timeline

mansourdidehban88
In reply to this post by bnafta
در چهارشنبه 24 فوریهٔ 2016، ساعت 17:00:21 (UTC+3:30)، [hidden email] نوشته:

> Hello, I have some use cases, which currently are "solved" with Java Applets:
>
> 1 - Control a Twain scanner. (kodak scanner i2800)
> 2 - Control a fingerprint reader (Nitgen Fingkey Hamster I DX).
> 3 - Control a barcode reader.
>
> All of these involve access dll's (or .so ) via JNI.
>
>
> What technology Firefox provides so I can migrate and continue to access/control hardware as i can now via dll's + JNI + Java Applets?
>
>
>
>
> --
> Fábio C. Barrionuevo da Luz
> Palmas - Tocantins - Brasil - América do Sul
>
>
> Em terça-feira, 23 de fevereiro de 2016 15:35:46 UTC-3, Chris Peterson  escreveu:
> > On 2/23/16 10:03 AM, Java Dev wrote:
> > > Hope all is well. The company I work for uses Java applets for our web products and we are currently planning our release schedules to replace Java applet tech, as it will affect many users in our product community and several products. As such, our dev team would like to better understand the "drop dead date" of when the Java plugin will stop working in Firefox.
> > >
> > > We are aware that the announcement was for end of 2016, but wanted to confirm if there is a more specific date other than 12/31/2016. Also, we would like to know if Firefox will follow a similar path as Chrome to provide a way to still manually enable the Java plugin for some time (disabled by default), perhaps even past end of 2016.
> >
> >
> > hi Alexandra, our tentative schedule is to remove NPAPI support in
> > Firefox 53 (which will be in the Firefox Nightly channel in November
> > 2016 and released in April 2017). These versions or dates are not
> > official or set in stone. They could conceivably be postponed if we need
> > to continue supporting NPAPI for some reason.
> >
> > The next Firefox ESR (Extended Support Release) version is 52 and will
> > receive security updates for a year. By removing NPAPI in Firefox 53,
> > the release *after* the ESR, users that need NPAPI support can continue
> > to switch to Firefox ESR 52 and keep using NPAPI plugins until May 2018.
> >
> >
> > chris

_______________________________________________
dev-tech-plugins mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-plugins
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Java plugin phase out timeline

mansourdidehban88
In reply to this post by Java Dev
در سه‌شنبه 23 فوریهٔ 2016، ساعت 21:33:41 (UTC+3:30)، Java Dev نوشته:

> Hello,
>
> Hope all is well. The company I work for uses Java applets for our web products and we are currently planning our release schedules to replace Java applet tech, as it will affect many users in our product community and several products. As such, our dev team would like to better understand the "drop dead date" of when the Java plugin will stop working in Firefox.
>
> We are aware that the announcement was for end of 2016, but wanted to confirm if there is a more specific date other than 12/31/2016. Also, we would like to know if Firefox will follow a similar path as Chrome to provide a way to still manually enable the Java plugin for some time (disabled by default), perhaps even past end of 2016.
>
> We want our users to use Firefox instead of other browsers, especially since we have had to run through some hoops to get our corporate clients to switch from IE to Firefox for our web applications. For some reason, some corporations are resistant to running browsers other than IE and it took some convincing on our part.
>
> Your response is greatly appreciated. We would prefer our user community still use Firefox and not switch to IE, while we are working through converting our web products to web based technology and away from the Java plugin. We are concerned that if they switch to IE again, while we work to replace Java applets, their IT departments might not approve going back again to Firefox.
>
> Best Regards,
> Alexandra
>
> P.S. If you are interested, more information about our company and products is available at www.7thonline.com.

_______________________________________________
dev-tech-plugins mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-plugins
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Java plugin phase out timeline

mansourdidehban88
In reply to this post by bnafta
در چهارشنبه 24 فوریهٔ 2016، ساعت 20:55:58 (UTC+3:30)، Mikael Haltali نوشته:

> Hi,
> the best solution currently is js-ctypes which enables you to build an
> extension that calls a custom dll written in C
> That's what my team is currently doing to migrate a NPAPI plugin.
> Documentation is good but the only drawback currently is the lack of end to
> end examples.
> Here is a link to official documentation
> https://developer.mozilla.org/en-US/docs/Mozilla/js-ctypes
>
> Hope this helps
>
> On Wed, Feb 24, 2016 at 2:30 PM, <[hidden email]> wrote:
>
> > Hello, I have some use cases, which currently are "solved" with Java
> > Applets:
> >
> > 1 - Control a Twain scanner. (kodak scanner i2800)
> > 2 - Control a fingerprint reader (Nitgen Fingkey Hamster I DX).
> > 3 - Control a barcode reader.
> >
> > All of these involve access dll's (or .so ) via JNI.
> >
> >
> > What technology Firefox provides so I can migrate and continue to
> > access/control hardware as i can now via dll's + JNI + Java Applets?
> >
> >
> >
> >
> > --
> > Fábio C. Barrionuevo da Luz
> > Palmas - Tocantins - Brasil - América do Sul
> >
> >
> > Em terça-feira, 23 de fevereiro de 2016 15:35:46 UTC-3, Chris Peterson
> > escreveu:
> > > On 2/23/16 10:03 AM, Java Dev wrote:
> > > > Hope all is well. The company I work for uses Java applets for our web
> > products and we are currently planning our release schedules to replace
> > Java applet tech, as it will affect many users in our product community and
> > several products. As such, our dev team would like to better understand the
> > "drop dead date" of when the Java plugin will stop working in Firefox.
> > > >
> > > > We are aware that the announcement was for end of 2016, but wanted to
> > confirm if there is a more specific date other than 12/31/2016. Also, we
> > would like to know if Firefox will follow a similar path as Chrome to
> > provide a way to still manually enable the Java plugin for some time
> > (disabled by default), perhaps even past end of 2016.
> > >
> > >
> > > hi Alexandra, our tentative schedule is to remove NPAPI support in
> > > Firefox 53 (which will be in the Firefox Nightly channel in November
> > > 2016 and released in April 2017). These versions or dates are not
> > > official or set in stone. They could conceivably be postponed if we need
> > > to continue supporting NPAPI for some reason.
> > >
> > > The next Firefox ESR (Extended Support Release) version is 52 and will
> > > receive security updates for a year. By removing NPAPI in Firefox 53,
> > > the release *after* the ESR, users that need NPAPI support can continue
> > > to switch to Firefox ESR 52 and keep using NPAPI plugins until May 2018.
> > >
> > >
> > > chris
> > _______________________________________________
> > dev-tech-plugins mailing list
> > [hidden email]
> > https://lists.mozilla.org/listinfo/dev-tech-plugins
> >

_______________________________________________
dev-tech-plugins mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-plugins
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Java plugin phase out timeline

mansourdidehban88
In reply to this post by Chris Peterson-12
در سه‌شنبه 23 فوریهٔ 2016، ساعت 22:05:46 (UTC+3:30)، Chris Peterson نوشته:

> On 2/23/16 10:03 AM, Java Dev wrote:
> > Hope all is well. The company I work for uses Java applets for our web products and we are currently planning our release schedules to replace Java applet tech, as it will affect many users in our product community and several products. As such, our dev team would like to better understand the "drop dead date" of when the Java plugin will stop working in Firefox.
> >
> > We are aware that the announcement was for end of 2016, but wanted to confirm if there is a more specific date other than 12/31/2016. Also, we would like to know if Firefox will follow a similar path as Chrome to provide a way to still manually enable the Java plugin for some time (disabled by default), perhaps even past end of 2016.
>
>
> hi Alexandra, our tentative schedule is to remove NPAPI support in
> Firefox 53 (which will be in the Firefox Nightly channel in November
> 2016 and released in April 2017). These versions or dates are not
> official or set in stone. They could conceivably be postponed if we need
> to continue supporting NPAPI for some reason.
>
> The next Firefox ESR (Extended Support Release) version is 52 and will
> receive security updates for a year. By removing NPAPI in Firefox 53,
> the release *after* the ESR, users that need NPAPI support can continue
> to switch to Firefox ESR 52 and keep using NPAPI plugins until May 2018.
>
>
> chris

_______________________________________________
dev-tech-plugins mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-plugins
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Java plugin phase out timeline

mansourdidehban88
In reply to this post by mansourdidehban88
در جمعه 20 ژانویهٔ 2017، ساعت 12:37:22 (UTC+3:30)، [hidden email] نوشته:

> در چهارشنبه 24 فوریهٔ 2016، ساعت 20:55:58 (UTC+3:30)، Mikael Haltali نوشته:
> > Hi,
> > the best solution currently is js-ctypes which enables you to build an
> > extension that calls a custom dll written in C
> > That's what my team is currently doing to migrate a NPAPI plugin.
> > Documentation is good but the only drawback currently is the lack of end to
> > end examples.
> > Here is a link to official documentation
> > https://developer.mozilla.org/en-US/docs/Mozilla/js-ctypes
> >
> > Hope this helps
> >
> > On Wed, Feb 24, 2016 at 2:30 PM, <[hidden email]> wrote:
> >
> > > Hello, I have some use cases, which currently are "solved" with Java
> > > Applets:
> > >
> > > 1 - Control a Twain scanner. (kodak scanner i2800)
> > > 2 - Control a fingerprint reader (Nitgen Fingkey Hamster I DX).
> > > 3 - Control a barcode reader.
> > >
> > > All of these involve access dll's (or .so ) via JNI.
> > >
> > >
> > > What technology Firefox provides so I can migrate and continue to
> > > access/control hardware as i can now via dll's + JNI + Java Applets?
> > >
> > >
> > >
> > >
> > > --
> > > Fábio C. Barrionuevo da Luz
> > > Palmas - Tocantins - Brasil - América do Sul
> > >
> > >
> > > Em terça-feira, 23 de fevereiro de 2016 15:35:46 UTC-3, Chris Peterson
> > > escreveu:
> > > > On 2/23/16 10:03 AM, Java Dev wrote:
> > > > > Hope all is well. The company I work for uses Java applets for our web
> > > products and we are currently planning our release schedules to replace
> > > Java applet tech, as it will affect many users in our product community and
> > > several products. As such, our dev team would like to better understand the
> > > "drop dead date" of when the Java plugin will stop working in Firefox.
> > > > >
> > > > > We are aware that the announcement was for end of 2016, but wanted to
> > > confirm if there is a more specific date other than 12/31/2016. Also, we
> > > would like to know if Firefox will follow a similar path as Chrome to
> > > provide a way to still manually enable the Java plugin for some time
> > > (disabled by default), perhaps even past end of 2016.
> > > >
> > > >
> > > > hi Alexandra, our tentative schedule is to remove NPAPI support in
> > > > Firefox 53 (which will be in the Firefox Nightly channel in November
> > > > 2016 and released in April 2017). These versions or dates are not
> > > > official or set in stone. They could conceivably be postponed if we need
> > > > to continue supporting NPAPI for some reason.
> > > >
> > > > The next Firefox ESR (Extended Support Release) version is 52 and will
> > > > receive security updates for a year. By removing NPAPI in Firefox 53,
> > > > the release *after* the ESR, users that need NPAPI support can continue
> > > > to switch to Firefox ESR 52 and keep using NPAPI plugins until May 2018.
> > > >
> > > >
> > > > chris
> > > _______________________________________________
> > > dev-tech-plugins mailing list
> > > [hidden email]
> > > https://lists.mozilla.org/listinfo/dev-tech-plugins
> > >

_______________________________________________
dev-tech-plugins mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-plugins
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Java plugin phase out timeline

mansourdidehban88
In reply to this post by Java Dev
در سه‌شنبه 23 فوریهٔ 2016، ساعت 21:33:41 (UTC+3:30)، Java Dev نوشته:

> Hello,
>
> Hope all is well. The company I work for uses Java applets for our web products and we are currently planning our release schedules to replace Java applet tech, as it will affect many users in our product community and several products. As such, our dev team would like to better understand the "drop dead date" of when the Java plugin will stop working in Firefox.
>
> We are aware that the announcement was for end of 2016, but wanted to confirm if there is a more specific date other than 12/31/2016. Also, we would like to know if Firefox will follow a similar path as Chrome to provide a way to still manually enable the Java plugin for some time (disabled by default), perhaps even past end of 2016.
>
> We want our users to use Firefox instead of other browsers, especially since we have had to run through some hoops to get our corporate clients to switch from IE to Firefox for our web applications. For some reason, some corporations are resistant to running browsers other than IE and it took some convincing on our part.
>
> Your response is greatly appreciated. We would prefer our user community still use Firefox and not switch to IE, while we are working through converting our web products to web based technology and away from the Java plugin. We are concerned that if they switch to IE again, while we work to replace Java applets, their IT departments might not approve going back again to Firefox.
>
> Best Regards,
> Alexandra
>
> P.S. If you are interested, more information about our company and products is available at www.7thonline.com.

_______________________________________________
dev-tech-plugins mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-plugins
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Java plugin phase out timeline

daniel.eggerstorfer
In reply to this post by Java Dev
Hi

Our company has also a Java Applet (of course with NPAPI) in place.

according to this page: https://support.mozilla.org/t5/Problems-with-add-ons-plugins-or/Why-do-Java-Silverlight-Adobe-Acrobat-and-other-plugins-no/ta-p/31069
Also the ESR 52 64bit Version is blocking Java.

As far as I understood this posts here and the Information:

on 64bit both 52 Versions (*release* and *ESR*) are blocking Java Applets
on 32bit only the *release* 52 is blocking Java.

Is that correct?

Additional is/was there any 64bit Version which is supporting Java NPAPI?

best regards
Daniel
_______________________________________________
dev-tech-plugins mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-plugins
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Java plugin phase out timeline

Chris Peterson-12
On 3/9/2017 1:24 AM, [hidden email] wrote:

> Our company has also a Java Applet (of course with NPAPI) in place.
>
> according to this page: https://support.mozilla.org/t5/Problems-with-add-ons-plugins-or/Why-do-Java-Silverlight-Adobe-Acrobat-and-other-plugins-no/ta-p/31069
> Also the ESR 52 64bit Version is blocking Java.
>
> As far as I understood this posts here and the Information:
>
> on 64bit both 52 Versions (*release* and *ESR*) are blocking Java Applets
> on 32bit only the *release* 52 is blocking Java.
>
> Is that correct?

That's correct. Flash and Silverlight are the only 64-bit NPAPI plugins
that we supported with 64-bit Firefox. Java is allowed on 32-bit ESR and
blocked on 32-bit release.

If switching from 32-bit Firefox to ESR is too cumbersome for your
company, you might consider "jumping into" IE just when you need to open
your Java applet. IE will continue to support NPAPI plugins for a long time.

chris
_______________________________________________
dev-tech-plugins mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-plugins
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Java plugin phase out timeline

ashokagrawal51
In reply to this post by Java Dev
On Tuesday, February 23, 2016 at 11:33:41 PM UTC+5:30, Java Dev wrote:

> Hello,
>
> Hope all is well. The company I work for uses Java applets for our web products and we are currently planning our release schedules to replace Java applet tech, as it will affect many users in our product community and several products. As such, our dev team would like to better understand the "drop dead date" of when the Java plugin will stop working in Firefox.
>
> We are aware that the announcement was for end of 2016, but wanted to confirm if there is a more specific date other than 12/31/2016. Also, we would like to know if Firefox will follow a similar path as Chrome to provide a way to still manually enable the Java plugin for some time (disabled by default), perhaps even past end of 2016.
>
> We want our users to use Firefox instead of other browsers, especially since we have had to run through some hoops to get our corporate clients to switch from IE to Firefox for our web applications. For some reason, some corporations are resistant to running browsers other than IE and it took some convincing on our part.
>
> Your response is greatly appreciated. We would prefer our user community still use Firefox and not switch to IE, while we are working through converting our web products to web based technology and away from the Java plugin. We are concerned that if they switch to IE again, while we work to replace Java applets, their IT departments might not approve going back again to Firefox.
>
> Best Regards,
> Alexandra
>
> P.S. If you are interested, more information about our company and products is available at www.7thonline.com.

_______________________________________________
dev-tech-plugins mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-plugins
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Java plugin phase out timeline

judithq67
In reply to this post by Java Dev
On Tuesday, February 23, 2016 at 10:03:41 AM UTC-8, Java Dev wrote:

> Hello,
>
> Hope all is well. The company I work for uses Java applets for our web products and we are currently planning our release schedules to replace Java applet tech, as it will affect many users in our product community and several products. As such, our dev team would like to better understand the "drop dead date" of when the Java plugin will stop working in Firefox.
>
> We are aware that the announcement was for end of 2016, but wanted to confirm if there is a more specific date other than 12/31/2016. Also, we would like to know if Firefox will follow a similar path as Chrome to provide a way to still manually enable the Java plugin for some time (disabled by default), perhaps even past end of 2016.
>
> We want our users to use Firefox instead of other browsers, especially since we have had to run through some hoops to get our corporate clients to switch from IE to Firefox for our web applications. For some reason, some corporations are resistant to running browsers other than IE and it took some convincing on our part.
>
> Your response is greatly appreciated. We would prefer our user community still use Firefox and not switch to IE, while we are working through converting our web products to web based technology and away from the Java plugin. We are concerned that if they switch to IE again, while we work to replace Java applets, their IT departments might not approve going back again to Firefox.
>
> Best Regards,
> Alexandra
>
> P.S. If you are interested, more information about our company and products is available at www.7thonline.com.

My website uses Java to view my cameras, both with Trendnet Cloudview and Amcrest. What are we supposed to do now except avoid Firefox?
_______________________________________________
dev-tech-plugins mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-plugins
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Java plugin phase out timeline

Christian Rottler
You might want to switch from its Rapid Release (commonly just known as
"Firefox") to the Extended Support Release (ESR) which will continue to
support NPAPI-based plugins until next year / around the end of June 2018
according to my schedule.

This should give you some more time to look for an alternative.

Regards,
Chris

On 22 March 2017 at 15:15, <[hidden email]> wrote:

> On Tuesday, February 23, 2016 at 10:03:41 AM UTC-8, Java Dev wrote:
> > Hello,
> >
> > Hope all is well. The company I work for uses Java applets for our web
> products and we are currently planning our release schedules to replace
> Java applet tech, as it will affect many users in our product community and
> several products. As such, our dev team would like to better understand the
> "drop dead date" of when the Java plugin will stop working in Firefox.
> >
> > We are aware that the announcement was for end of 2016, but wanted to
> confirm if there is a more specific date other than 12/31/2016. Also, we
> would like to know if Firefox will follow a similar path as Chrome to
> provide a way to still manually enable the Java plugin for some time
> (disabled by default), perhaps even past end of 2016.
> >
> > We want our users to use Firefox instead of other browsers, especially
> since we have had to run through some hoops to get our corporate clients to
> switch from IE to Firefox for our web applications. For some reason, some
> corporations are resistant to running browsers other than IE and it took
> some convincing on our part.
> >
> > Your response is greatly appreciated. We would prefer our user community
> still use Firefox and not switch to IE, while we are working through
> converting our web products to web based technology and away from the Java
> plugin. We are concerned that if they switch to IE again, while we work to
> replace Java applets, their IT departments might not approve going back
> again to Firefox.
> >
> > Best Regards,
> > Alexandra
> >
> > P.S. If you are interested, more information about our company and
> products is available at www.7thonline.com.
>
> My website uses Java to view my cameras, both with Trendnet Cloudview and
> Amcrest. What are we supposed to do now except avoid Firefox?
> _______________________________________________
> dev-tech-plugins mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-tech-plugins
>
_______________________________________________
dev-tech-plugins mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-plugins
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: [EXTERNAL] - Re: Java plugin phase out timeline

Peter Weinstein
Hi



I'm looking for Webextensions help.





I have a Webextension which launches a native app using

the chrome.runtime.sendNativeMessage(...) API.



This extension normally invokes an already running process to get some

work done; noramlly the end result is to download a document from a

server and start a Microsoft Office Application (e.g. WinWord.exe) to

edit/review.



The extension returns immediately.



However, there is a problem. If the long-running application is not

actually running, then it is started. But when the extension gets a

response message, it kills the native application, and every process

created by it.



This is unexpected (by me); Chrome behavior differs.



Is this expected behavior by you? Is it documented? Is there a

mechanism for my native application to launch a task which continues

to run after the native application has returned to Firefox, and

exited?


_______________________________________________
dev-tech-plugins mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-plugins
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [EXTERNAL] - Re: Java plugin phase out timeline

Benjamin Smedberg
This is not the right list for this question: it should be asked on the
[hidden email] mailing list. However I will give you a link to the
documentation which includes a specific warning about this behavior:
https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Native_messaging#Closing_the_native_app

--BDS


On Wed, Apr 12, 2017 at 1:40 PM, Peter Weinstein <[hidden email]>
wrote:

> Hi
>
>
>
> I'm looking for Webextensions help.
>
>
>
>
>
> I have a Webextension which launches a native app using
>
> the chrome.runtime.sendNativeMessage(...) API.
>
>
>
> This extension normally invokes an already running process to get some
>
> work done; noramlly the end result is to download a document from a
>
> server and start a Microsoft Office Application (e.g. WinWord.exe) to
>
> edit/review.
>
>
>
> The extension returns immediately.
>
>
>
> However, there is a problem. If the long-running application is not
>
> actually running, then it is started. But when the extension gets a
>
> response message, it kills the native application, and every process
>
> created by it.
>
>
>
> This is unexpected (by me); Chrome behavior differs.
>
>
>
> Is this expected behavior by you? Is it documented? Is there a
>
> mechanism for my native application to launch a task which continues
>
> to run after the native application has returned to Firefox, and
>
> exited?
>
>
> _______________________________________________
> dev-tech-plugins mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-tech-plugins
>
_______________________________________________
dev-tech-plugins mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-plugins
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Java plugin phase out timeline

l.guzman.g
In reply to this post by judithq67
El miércoles, 22 de marzo de 2017, 8:25:21 (UTC-6), Christian Rottler escribió:
> You might want to switch from its Rapid Release (commonly just known as
> "Firefox") to the Extended Support Release (ESR) which will continue to
> support NPAPI-based plugins until next year / around the end of June 2018
> according to my schedule.

In México the Tax Administration Service (SAT, on Spanish) uses Java for their platform for all the tax payers, i always used/recommend Firefox for clients in order to use their services. Now, aside from the ESR i believe we are confined to IE.

>
> This should give you some more time to look for an alternative.
It does, thanks.

>
> Regards,
> Chris

Best,
Luis
_______________________________________________
dev-tech-plugins mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-tech-plugins
1234
Loading...