-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove usage of Applet/JAppelt and AppletInfo #383
Comments
+1, please provide PR |
👍 for me too |
I would not consider removing Applet support until at least December 2030. Java 8 supports applets natively and via JNLP. Applets can still be run in the IE 11 browser via Edge and IE compatibility mode. Java 8's extended support ends December 2030. See page https://www.oracle.com/java/technologies/java-se-support-roadmap.html for details. Although the browser Java Plugin is no longer formally supported, JNLP (aka Java web start) is until December 2030. Applets can be deployed through JNLP. |
If part of the user base is still using Applets, then I'm content with keeping them for as long as long as they are functional. But I don't know how realistic it is, to keep supporting them until 2030. The final decision will probably be made by Oracle, when they decide to remove those classes from the JDK. They still seem to be contained in the upcoming Java 21, but once they are gone, I'm leaning towards keeping WB compatible with the latest Java version, rather than trying to keep Applets alive... But I suppose that's something that can be discussed again, when that time has come. |
The Applet/JApplet class has been marked as deprecated back in Java 9 and marked for removal in Java 17. Given that most browsers dropped their support for Java plugins, we should remove the corresponding code from WB.
See JEP 398 for reference.
From the original Oracle whitepaper:
The text was updated successfully, but these errors were encountered: