When Firefox drops Java applet support, how will I run old Java applets?
up vote
11
down vote
favorite
Java applets are soon to be killed off forever. I understand why we shouldn't make new ones. But what will happen to old ones? There are still Java applets that people may use, and there's no guarantee that anyone will be willing or able to port them to JavaScript.
For example, this online computer music book has a lot of Java applets that explain and visualize certain digital audio concepts. Another course I'm taking uses a lot of Java applets to visualize computational geometry ideas. When Firefox drops NPAPI support, that's it, we've cut off this great reference material to all but those willing to jump through arcane technological hoops.
The following possible solutions don't always fit the bill:
Just use FireFox Won't be possible after 2016.
Port it or rewrite it May not be open source, or it may not be practical to do so (e.g. lack of domain knowledge).
Ask the original author to do it They may have stopped supporting it years ago. Doesn't make it any less effective at, say, tracing out the steps for Delaunay triangulations.
Find an alternative If none exist, we're back to the second option. If the only ones that do exist aren't browser-based, all bets are off for convenience (which is the whole point of browser apps).
Is there currently (or will there be within a year) a convenient, cross-platform way to run existing Java applets once all the major Web browsers drop NPAPI support?
Note that:
- Actually so in-browser isn't critical, but it should still be cross-platform. Ideally I wouldn't have to download extra software (after all, I already do have a JVM installed).
- No, I'm not suggesting we re-open the security holes that Chrome and Firefox are trying to close.
- If there are alternative Web browsers out there designed specifically for legacy Java applet support (or at least with no plans to drop existing NPAPI support), I would be okay with that.
browser compatibility java-applet browser-plugin npapi
asked Nov 12 '15 at 20:16
JesseTG
196213
|
show 5 more comments
up vote
11
down vote
favorite
Java applets are soon to be killed off forever. I understand why we shouldn't make new ones. But what will happen to old ones? There are still Java applets that people may use, and there's no guarantee that anyone will be willing or able to port them to JavaScript.
For example, this online computer music book has a lot of Java applets that explain and visualize certain digital audio concepts. Another course I'm taking uses a lot of Java applets to visualize computational geometry ideas. When Firefox drops NPAPI support, that's it, we've cut off this great reference material to all but those willing to jump through arcane technological hoops.
The following possible solutions don't always fit the bill:
Just use FireFox Won't be possible after 2016.
Port it or rewrite it May not be open source, or it may not be practical to do so (e.g. lack of domain knowledge).
Ask the original author to do it They may have stopped supporting it years ago. Doesn't make it any less effective at, say, tracing out the steps for Delaunay triangulations.
Find an alternative If none exist, we're back to the second option. If the only ones that do exist aren't browser-based, all bets are off for convenience (which is the whole point of browser apps).
Is there currently (or will there be within a year) a convenient, cross-platform way to run existing Java applets once all the major Web browsers drop NPAPI support?
Note that:
- Actually so in-browser isn't critical, but it should still be cross-platform. Ideally I wouldn't have to download extra software (after all, I already do have a JVM installed).
- No, I'm not suggesting we re-open the security holes that Chrome and Firefox are trying to close.
- If there are alternative Web browsers out there designed specifically for legacy Java applet support (or at least with no plans to drop existing NPAPI support), I would be okay with that.
browser compatibility java-applet browser-plugin npapi
asked Nov 12 '15 at 20:16
JesseTG
196213
2
What’s wrong with using an old browser for old websites?
– Daniel B
Nov 12 '15 at 20:17
Why should I have to? Especially since older builds may not always be available or easy to produce (e.g. will last year's build of Firefox run on the machine I have in five years?).
– JesseTG
Nov 12 '15 at 20:19
Technically speaking the why is because of security. Current browsers shouldn't be made insecure. As for how this can be handled, many ways, check with the Firefox developers to determine what their plans are
– Ramhound
Nov 12 '15 at 20:28
2
I don't know how viable a solution it is, but the Java JDK has a debugging tool calledappletviewerthat may work.
– heavyd
Nov 12 '15 at 20:57
2
@JesseTG “Why should I have to?” Because they’re, you know, old? If you truly need old software and your current environment can’t run it, you could use a virtual machine.
– Daniel B
Nov 12 '15 at 22:21
|
show 5 more comments
up vote
11
down vote
favorite
up vote
11
down vote
favorite
Java applets are soon to be killed off forever. I understand why we shouldn't make new ones. But what will happen to old ones? There are still Java applets that people may use, and there's no guarantee that anyone will be willing or able to port them to JavaScript.
For example, this online computer music book has a lot of Java applets that explain and visualize certain digital audio concepts. Another course I'm taking uses a lot of Java applets to visualize computational geometry ideas. When Firefox drops NPAPI support, that's it, we've cut off this great reference material to all but those willing to jump through arcane technological hoops.
The following possible solutions don't always fit the bill:
Just use FireFox Won't be possible after 2016.
Port it or rewrite it May not be open source, or it may not be practical to do so (e.g. lack of domain knowledge).
Ask the original author to do it They may have stopped supporting it years ago. Doesn't make it any less effective at, say, tracing out the steps for Delaunay triangulations.
Find an alternative If none exist, we're back to the second option. If the only ones that do exist aren't browser-based, all bets are off for convenience (which is the whole point of browser apps).
Is there currently (or will there be within a year) a convenient, cross-platform way to run existing Java applets once all the major Web browsers drop NPAPI support?
Note that:
- Actually so in-browser isn't critical, but it should still be cross-platform. Ideally I wouldn't have to download extra software (after all, I already do have a JVM installed).
- No, I'm not suggesting we re-open the security holes that Chrome and Firefox are trying to close.
- If there are alternative Web browsers out there designed specifically for legacy Java applet support (or at least with no plans to drop existing NPAPI support), I would be okay with that.
browser compatibility java-applet browser-plugin npapi
asked Nov 12 '15 at 20:16
JesseTG
196213
Java applets are soon to be killed off forever. I understand why we shouldn't make new ones. But what will happen to old ones? There are still Java applets that people may use, and there's no guarantee that anyone will be willing or able to port them to JavaScript.
For example, this online computer music book has a lot of Java applets that explain and visualize certain digital audio concepts. Another course I'm taking uses a lot of Java applets to visualize computational geometry ideas. When Firefox drops NPAPI support, that's it, we've cut off this great reference material to all but those willing to jump through arcane technological hoops.
The following possible solutions don't always fit the bill:
Just use FireFox Won't be possible after 2016.
Port it or rewrite it May not be open source, or it may not be practical to do so (e.g. lack of domain knowledge).
Ask the original author to do it They may have stopped supporting it years ago. Doesn't make it any less effective at, say, tracing out the steps for Delaunay triangulations.
Find an alternative If none exist, we're back to the second option. If the only ones that do exist aren't browser-based, all bets are off for convenience (which is the whole point of browser apps).
Is there currently (or will there be within a year) a convenient, cross-platform way to run existing Java applets once all the major Web browsers drop NPAPI support?
Note that:
- Actually so in-browser isn't critical, but it should still be cross-platform. Ideally I wouldn't have to download extra software (after all, I already do have a JVM installed).
- No, I'm not suggesting we re-open the security holes that Chrome and Firefox are trying to close.
- If there are alternative Web browsers out there designed specifically for legacy Java applet support (or at least with no plans to drop existing NPAPI support), I would be okay with that.
browser compatibility java-applet browser-plugin npapi
browser compatibility java-applet browser-plugin npapi
asked Nov 12 '15 at 20:16
JesseTG
196213
asked Nov 12 '15 at 20:16
JesseTG
196213
edited Nov 12 '15 at 20:34
asked Nov 12 '15 at 20:16
JesseTG
196213
asked Nov 12 '15 at 20:16
JesseTG
196213
asked Nov 12 '15 at 20:16
JesseTG
196213
196213
2
What’s wrong with using an old browser for old websites?
– Daniel B
Nov 12 '15 at 20:17
Why should I have to? Especially since older builds may not always be available or easy to produce (e.g. will last year's build of Firefox run on the machine I have in five years?).
– JesseTG
Nov 12 '15 at 20:19
Technically speaking the why is because of security. Current browsers shouldn't be made insecure. As for how this can be handled, many ways, check with the Firefox developers to determine what their plans are
– Ramhound
Nov 12 '15 at 20:28
2
I don't know how viable a solution it is, but the Java JDK has a debugging tool calledappletviewerthat may work.
– heavyd
Nov 12 '15 at 20:57
2
@JesseTG “Why should I have to?” Because they’re, you know, old? If you truly need old software and your current environment can’t run it, you could use a virtual machine.
– Daniel B
Nov 12 '15 at 22:21
|
show 5 more comments
2
What’s wrong with using an old browser for old websites?
– Daniel B
Nov 12 '15 at 20:17
Why should I have to? Especially since older builds may not always be available or easy to produce (e.g. will last year's build of Firefox run on the machine I have in five years?).
– JesseTG
Nov 12 '15 at 20:19
Technically speaking the why is because of security. Current browsers shouldn't be made insecure. As for how this can be handled, many ways, check with the Firefox developers to determine what their plans are
– Ramhound
Nov 12 '15 at 20:28
2
I don't know how viable a solution it is, but the Java JDK has a debugging tool calledappletviewerthat may work.
– heavyd
Nov 12 '15 at 20:57
2
@JesseTG “Why should I have to?” Because they’re, you know, old? If you truly need old software and your current environment can’t run it, you could use a virtual machine.
– Daniel B
Nov 12 '15 at 22:21
2
2
What’s wrong with using an old browser for old websites?
– Daniel B
Nov 12 '15 at 20:17
What’s wrong with using an old browser for old websites?
– Daniel B
Nov 12 '15 at 20:17
Why should I have to? Especially since older builds may not always be available or easy to produce (e.g. will last year's build of Firefox run on the machine I have in five years?).
– JesseTG
Nov 12 '15 at 20:19
Why should I have to? Especially since older builds may not always be available or easy to produce (e.g. will last year's build of Firefox run on the machine I have in five years?).
– JesseTG
Nov 12 '15 at 20:19
Technically speaking the why is because of security. Current browsers shouldn't be made insecure. As for how this can be handled, many ways, check with the Firefox developers to determine what their plans are
– Ramhound
Nov 12 '15 at 20:28
Technically speaking the why is because of security. Current browsers shouldn't be made insecure. As for how this can be handled, many ways, check with the Firefox developers to determine what their plans are
– Ramhound
Nov 12 '15 at 20:28
2
2
I don't know how viable a solution it is, but the Java JDK has a debugging tool called
appletviewer that may work.– heavyd
Nov 12 '15 at 20:57
I don't know how viable a solution it is, but the Java JDK has a debugging tool called
appletviewer that may work.– heavyd
Nov 12 '15 at 20:57
2
2
@JesseTG “Why should I have to?” Because they’re, you know, old? If you truly need old software and your current environment can’t run it, you could use a virtual machine.
– Daniel B
Nov 12 '15 at 22:21
@JesseTG “Why should I have to?” Because they’re, you know, old? If you truly need old software and your current environment can’t run it, you could use a virtual machine.
– Daniel B
Nov 12 '15 at 22:21
|
show 5 more comments
4 Answers
4
active
oldest
votes
up vote
8
down vote
accepted
The Java Developers Kit (JDK) has a utility that is designed for debugging applets. The tool is called appletviewer and is run like this:
<PATH_TO_JDK>binappletviewer.exe <url_to_page_with_applet>
I'm not sure how viable of an option this is, but it should allow you to see many applets without using a browser.
edited Nov 12 '15 at 22:21
Daniel B
32.8k75985
answered Nov 12 '15 at 21:41
heavyd
49.8k12122155
add a comment |
up vote
3
down vote
According this post some browsers will extend support for NPAPI for a while:
What are the timelines for browsers' plugin support?
Individual browser vendors have been updating their plans regularly. Here's a snapshot of what some browser vendors have stated as of today:
Microsoft Internet Explorer (IE)
Microsoft has indicated that they intend to continue to offer plug-in support in IE.
Microsoft Edge
Microsoft Edge was released in Windows 10 without Browser Helper Object (BHO, aka. plugin) support. Microsoft has no plans to add plugin support to Edge.
Mozilla Firefox Extended Support Release (ESR)
Mozilla indicated in early 2016 that Firefox ESR 52 will be the last version to offer NPAPI (and JRE) support. Firefox ESR 52 is targeted for release in April 2017 and will be supported until May 2018.
Mozilla Firefox Rapid Release
Mozilla intends to remove NPAPI support from the Firefox 53 Rapid Release version targeted for release in April 2017.
Apple Safari for Mac OS
Safari offers Internet plug-in support for Mac OS users. Apple has not made any statements about deprecating plugin support for Mac OS users.
Alphabet (Google) Chrome for Windows
Chrome offered support for plugins until version 45, released in September 2015. They removed NPAPI support in later Chrome releases.
answered Dec 20 '16 at 21:31
Rafael Trestini
311
IE and Firefox ESR do still work, woot. superuser.com/questions/1213341/… and safari does still too (if you manually turn it on) woot
– rogerdpack
May 1 at 0:20
add a comment |
up vote
0
down vote
Although the official Firefox is not supporting NPAPI, there are supported and updated forks of Firefox code/engine, all of them are very stable projects, have a big community and are receiving security updates frequently.
List of updated forks of Firefox supporting NPAPI:
Waterfox 56 (updated and based in FF56)
Basilisk 201804 (updated and based in FF52)
Palemoon 27 (updated and based in FF27 UI-preAustralis)
By the way, there are also unofficial forks of Basilisk and Palemoon for Windows XP(I will not include reference because at the moment this project is not so stable as previous options)
answered May 8 at 16:38
Daniel Perez
445
add a comment |
up vote
-2
down vote
I found an extension for Chrome called CheerpJ Applet Runner that seems to be at least somewhat effective at making Java applets viewable now that browsers aren't supporting NPAPI. You can access it here: https://chrome.google.com/webstore/detail/cheerpj-applet-runner/bbmolahhldcbngedljfadjlognfaaein/related?hl=en
answered Nov 21 at 2:33
hagenaue
1
New contributor
hagenaue is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
8
down vote
accepted
The Java Developers Kit (JDK) has a utility that is designed for debugging applets. The tool is called appletviewer and is run like this:
<PATH_TO_JDK>binappletviewer.exe <url_to_page_with_applet>
I'm not sure how viable of an option this is, but it should allow you to see many applets without using a browser.
edited Nov 12 '15 at 22:21
Daniel B
32.8k75985
answered Nov 12 '15 at 21:41
heavyd
49.8k12122155
add a comment |
up vote
8
down vote
accepted
The Java Developers Kit (JDK) has a utility that is designed for debugging applets. The tool is called appletviewer and is run like this:
<PATH_TO_JDK>binappletviewer.exe <url_to_page_with_applet>
I'm not sure how viable of an option this is, but it should allow you to see many applets without using a browser.
edited Nov 12 '15 at 22:21
Daniel B
32.8k75985
answered Nov 12 '15 at 21:41
heavyd
49.8k12122155
add a comment |
up vote
8
down vote
accepted
up vote
8
down vote
accepted
The Java Developers Kit (JDK) has a utility that is designed for debugging applets. The tool is called appletviewer and is run like this:
<PATH_TO_JDK>binappletviewer.exe <url_to_page_with_applet>
I'm not sure how viable of an option this is, but it should allow you to see many applets without using a browser.
edited Nov 12 '15 at 22:21
Daniel B
32.8k75985
answered Nov 12 '15 at 21:41
heavyd
49.8k12122155
The Java Developers Kit (JDK) has a utility that is designed for debugging applets. The tool is called appletviewer and is run like this:
<PATH_TO_JDK>binappletviewer.exe <url_to_page_with_applet>
I'm not sure how viable of an option this is, but it should allow you to see many applets without using a browser.
edited Nov 12 '15 at 22:21
Daniel B
32.8k75985
answered Nov 12 '15 at 21:41
heavyd
49.8k12122155
edited Nov 12 '15 at 22:21
Daniel B
32.8k75985
edited Nov 12 '15 at 22:21
Daniel B
32.8k75985
edited Nov 12 '15 at 22:21
Daniel B
32.8k75985
32.8k75985
answered Nov 12 '15 at 21:41
heavyd
49.8k12122155
answered Nov 12 '15 at 21:41
heavyd
49.8k12122155
answered Nov 12 '15 at 21:41
heavyd
49.8k12122155
49.8k12122155
add a comment |
add a comment |
up vote
3
down vote
According this post some browsers will extend support for NPAPI for a while:
What are the timelines for browsers' plugin support?
Individual browser vendors have been updating their plans regularly. Here's a snapshot of what some browser vendors have stated as of today:
Microsoft Internet Explorer (IE)
Microsoft has indicated that they intend to continue to offer plug-in support in IE.
Microsoft Edge
Microsoft Edge was released in Windows 10 without Browser Helper Object (BHO, aka. plugin) support. Microsoft has no plans to add plugin support to Edge.
Mozilla Firefox Extended Support Release (ESR)
Mozilla indicated in early 2016 that Firefox ESR 52 will be the last version to offer NPAPI (and JRE) support. Firefox ESR 52 is targeted for release in April 2017 and will be supported until May 2018.
Mozilla Firefox Rapid Release
Mozilla intends to remove NPAPI support from the Firefox 53 Rapid Release version targeted for release in April 2017.
Apple Safari for Mac OS
Safari offers Internet plug-in support for Mac OS users. Apple has not made any statements about deprecating plugin support for Mac OS users.
Alphabet (Google) Chrome for Windows
Chrome offered support for plugins until version 45, released in September 2015. They removed NPAPI support in later Chrome releases.
answered Dec 20 '16 at 21:31
Rafael Trestini
311
IE and Firefox ESR do still work, woot. superuser.com/questions/1213341/… and safari does still too (if you manually turn it on) woot
– rogerdpack
May 1 at 0:20
add a comment |
up vote
3
down vote
According this post some browsers will extend support for NPAPI for a while:
What are the timelines for browsers' plugin support?
Individual browser vendors have been updating their plans regularly. Here's a snapshot of what some browser vendors have stated as of today:
Microsoft Internet Explorer (IE)
Microsoft has indicated that they intend to continue to offer plug-in support in IE.
Microsoft Edge
Microsoft Edge was released in Windows 10 without Browser Helper Object (BHO, aka. plugin) support. Microsoft has no plans to add plugin support to Edge.
Mozilla Firefox Extended Support Release (ESR)
Mozilla indicated in early 2016 that Firefox ESR 52 will be the last version to offer NPAPI (and JRE) support. Firefox ESR 52 is targeted for release in April 2017 and will be supported until May 2018.
Mozilla Firefox Rapid Release
Mozilla intends to remove NPAPI support from the Firefox 53 Rapid Release version targeted for release in April 2017.
Apple Safari for Mac OS
Safari offers Internet plug-in support for Mac OS users. Apple has not made any statements about deprecating plugin support for Mac OS users.
Alphabet (Google) Chrome for Windows
Chrome offered support for plugins until version 45, released in September 2015. They removed NPAPI support in later Chrome releases.
answered Dec 20 '16 at 21:31
Rafael Trestini
311
IE and Firefox ESR do still work, woot. superuser.com/questions/1213341/… and safari does still too (if you manually turn it on) woot
– rogerdpack
May 1 at 0:20
add a comment |
up vote
3
down vote
up vote
3
down vote
According this post some browsers will extend support for NPAPI for a while:
What are the timelines for browsers' plugin support?
Individual browser vendors have been updating their plans regularly. Here's a snapshot of what some browser vendors have stated as of today:
Microsoft Internet Explorer (IE)
Microsoft has indicated that they intend to continue to offer plug-in support in IE.
Microsoft Edge
Microsoft Edge was released in Windows 10 without Browser Helper Object (BHO, aka. plugin) support. Microsoft has no plans to add plugin support to Edge.
Mozilla Firefox Extended Support Release (ESR)
Mozilla indicated in early 2016 that Firefox ESR 52 will be the last version to offer NPAPI (and JRE) support. Firefox ESR 52 is targeted for release in April 2017 and will be supported until May 2018.
Mozilla Firefox Rapid Release
Mozilla intends to remove NPAPI support from the Firefox 53 Rapid Release version targeted for release in April 2017.
Apple Safari for Mac OS
Safari offers Internet plug-in support for Mac OS users. Apple has not made any statements about deprecating plugin support for Mac OS users.
Alphabet (Google) Chrome for Windows
Chrome offered support for plugins until version 45, released in September 2015. They removed NPAPI support in later Chrome releases.
answered Dec 20 '16 at 21:31
Rafael Trestini
311
According this post some browsers will extend support for NPAPI for a while:
What are the timelines for browsers' plugin support?
Individual browser vendors have been updating their plans regularly. Here's a snapshot of what some browser vendors have stated as of today:
Microsoft Internet Explorer (IE)
Microsoft has indicated that they intend to continue to offer plug-in support in IE.
Microsoft Edge
Microsoft Edge was released in Windows 10 without Browser Helper Object (BHO, aka. plugin) support. Microsoft has no plans to add plugin support to Edge.
Mozilla Firefox Extended Support Release (ESR)
Mozilla indicated in early 2016 that Firefox ESR 52 will be the last version to offer NPAPI (and JRE) support. Firefox ESR 52 is targeted for release in April 2017 and will be supported until May 2018.
Mozilla Firefox Rapid Release
Mozilla intends to remove NPAPI support from the Firefox 53 Rapid Release version targeted for release in April 2017.
Apple Safari for Mac OS
Safari offers Internet plug-in support for Mac OS users. Apple has not made any statements about deprecating plugin support for Mac OS users.
Alphabet (Google) Chrome for Windows
Chrome offered support for plugins until version 45, released in September 2015. They removed NPAPI support in later Chrome releases.
answered Dec 20 '16 at 21:31
Rafael Trestini
311
answered Dec 20 '16 at 21:31
Rafael Trestini
311
answered Dec 20 '16 at 21:31
Rafael Trestini
311
answered Dec 20 '16 at 21:31
Rafael Trestini
311
311
IE and Firefox ESR do still work, woot. superuser.com/questions/1213341/… and safari does still too (if you manually turn it on) woot
– rogerdpack
May 1 at 0:20
add a comment |
IE and Firefox ESR do still work, woot. superuser.com/questions/1213341/… and safari does still too (if you manually turn it on) woot
– rogerdpack
May 1 at 0:20
IE and Firefox ESR do still work, woot. superuser.com/questions/1213341/… and safari does still too (if you manually turn it on) woot
– rogerdpack
May 1 at 0:20
IE and Firefox ESR do still work, woot. superuser.com/questions/1213341/… and safari does still too (if you manually turn it on) woot
– rogerdpack
May 1 at 0:20
add a comment |
up vote
0
down vote
Although the official Firefox is not supporting NPAPI, there are supported and updated forks of Firefox code/engine, all of them are very stable projects, have a big community and are receiving security updates frequently.
List of updated forks of Firefox supporting NPAPI:
Waterfox 56 (updated and based in FF56)
Basilisk 201804 (updated and based in FF52)
Palemoon 27 (updated and based in FF27 UI-preAustralis)
By the way, there are also unofficial forks of Basilisk and Palemoon for Windows XP(I will not include reference because at the moment this project is not so stable as previous options)
answered May 8 at 16:38
Daniel Perez
445
add a comment |
up vote
0
down vote
Although the official Firefox is not supporting NPAPI, there are supported and updated forks of Firefox code/engine, all of them are very stable projects, have a big community and are receiving security updates frequently.
List of updated forks of Firefox supporting NPAPI:
Waterfox 56 (updated and based in FF56)
Basilisk 201804 (updated and based in FF52)
Palemoon 27 (updated and based in FF27 UI-preAustralis)
By the way, there are also unofficial forks of Basilisk and Palemoon for Windows XP(I will not include reference because at the moment this project is not so stable as previous options)
answered May 8 at 16:38
Daniel Perez
445
add a comment |
up vote
0
down vote
up vote
0
down vote
Although the official Firefox is not supporting NPAPI, there are supported and updated forks of Firefox code/engine, all of them are very stable projects, have a big community and are receiving security updates frequently.
List of updated forks of Firefox supporting NPAPI:
Waterfox 56 (updated and based in FF56)
Basilisk 201804 (updated and based in FF52)
Palemoon 27 (updated and based in FF27 UI-preAustralis)
By the way, there are also unofficial forks of Basilisk and Palemoon for Windows XP(I will not include reference because at the moment this project is not so stable as previous options)
answered May 8 at 16:38
Daniel Perez
445
Although the official Firefox is not supporting NPAPI, there are supported and updated forks of Firefox code/engine, all of them are very stable projects, have a big community and are receiving security updates frequently.
List of updated forks of Firefox supporting NPAPI:
Waterfox 56 (updated and based in FF56)
Basilisk 201804 (updated and based in FF52)
Palemoon 27 (updated and based in FF27 UI-preAustralis)
By the way, there are also unofficial forks of Basilisk and Palemoon for Windows XP(I will not include reference because at the moment this project is not so stable as previous options)
answered May 8 at 16:38
Daniel Perez
445
answered May 8 at 16:38
Daniel Perez
445
answered May 8 at 16:38
Daniel Perez
445
answered May 8 at 16:38
Daniel Perez
445
445
add a comment |
add a comment |
up vote
-2
down vote
I found an extension for Chrome called CheerpJ Applet Runner that seems to be at least somewhat effective at making Java applets viewable now that browsers aren't supporting NPAPI. You can access it here: https://chrome.google.com/webstore/detail/cheerpj-applet-runner/bbmolahhldcbngedljfadjlognfaaein/related?hl=en
answered Nov 21 at 2:33
hagenaue
1
New contributor
hagenaue is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
-2
down vote
I found an extension for Chrome called CheerpJ Applet Runner that seems to be at least somewhat effective at making Java applets viewable now that browsers aren't supporting NPAPI. You can access it here: https://chrome.google.com/webstore/detail/cheerpj-applet-runner/bbmolahhldcbngedljfadjlognfaaein/related?hl=en
answered Nov 21 at 2:33
hagenaue
1
New contributor
hagenaue is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
-2
down vote
up vote
-2
down vote
I found an extension for Chrome called CheerpJ Applet Runner that seems to be at least somewhat effective at making Java applets viewable now that browsers aren't supporting NPAPI. You can access it here: https://chrome.google.com/webstore/detail/cheerpj-applet-runner/bbmolahhldcbngedljfadjlognfaaein/related?hl=en
answered Nov 21 at 2:33
hagenaue
1
New contributor
hagenaue is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I found an extension for Chrome called CheerpJ Applet Runner that seems to be at least somewhat effective at making Java applets viewable now that browsers aren't supporting NPAPI. You can access it here: https://chrome.google.com/webstore/detail/cheerpj-applet-runner/bbmolahhldcbngedljfadjlognfaaein/related?hl=en
answered Nov 21 at 2:33
hagenaue
1
New contributor
hagenaue is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Nov 21 at 2:33
hagenaue
1
New contributor
hagenaue is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Nov 21 at 2:33
hagenaue
1
answered Nov 21 at 2:33
hagenaue
1
1
New contributor
hagenaue is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
hagenaue is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
hagenaue is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f999778%2fwhen-firefox-drops-java-applet-support-how-will-i-run-old-java-applets%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
What’s wrong with using an old browser for old websites?
– Daniel B
Nov 12 '15 at 20:17
Why should I have to? Especially since older builds may not always be available or easy to produce (e.g. will last year's build of Firefox run on the machine I have in five years?).
– JesseTG
Nov 12 '15 at 20:19
Technically speaking the why is because of security. Current browsers shouldn't be made insecure. As for how this can be handled, many ways, check with the Firefox developers to determine what their plans are
– Ramhound
Nov 12 '15 at 20:28
2
I don't know how viable a solution it is, but the Java JDK has a debugging tool called
appletviewerthat may work.– heavyd
Nov 12 '15 at 20:57
2
@JesseTG “Why should I have to?” Because they’re, you know, old? If you truly need old software and your current environment can’t run it, you could use a virtual machine.
– Daniel B
Nov 12 '15 at 22:21