search

leaningtech / cheerpj-meta

Run Java 8 applications, libraries, applets, Java Web Start, and Oracle Forms on the web without legacy plugins.
https://labs.leaningtech.com/cheerpj
459 stars 21 forks source link

java.awt.Button, java.awt.Choice, etc. do not work on mobile browsers #170

Open jiver18 opened 1 year ago

jiver18 commented 1 year ago

I am new to Cheerpj.

I have an existing applet that contains elements like java.awt.Choice, java.awt.Button, and java.awt.ScrollPane. These appear to function correctly on desktop browsers. However, they do not function on Safari on iPads or Chrome on Android.

The simplest example is that you cannot change the value of a java.awt.Choice drop down list. Clicking on the list has no effect when using Safari on iPad or Chrome on Android. Clicking on java.awt.Button elements also appears to have no effect. Ultimately the applet should pop up a java.awt.ScrollPane with embedded graphics.

alexp-sssup commented 1 year ago

Touch events are not correctly handled for AWT components, this can be fixed in principle but it has never been a priority since AWT interfaces are designed for desktop and work very poorly on mobile anyway.

Our current focus is fully on the upcoming CheerpJ 3.0, a new architecture designed to be faster, simpler to use and scalable to Java 9+. I'll keep this bug open, but we won't be able to schedule any work on it for the time being.

jiver18 commented 1 year ago

Thank you for the quick response. It is enough for me to know that it is a known issue.

On Thu, May 4, 2023 at 3:31 PM Alessandro Pignotti @.***> wrote:

Touch events are not correctly handled for AWT components, this can be fixed in principle but it has never been a priority since AWT interfaces are designed for desktop and work very poorly on mobile anyway.

Our current focus is fully on the upcoming CheerpJ 3.0, a new architecture designed to be faster, simpler to use and scalable to Java 9+. I'll keep this bug open, but we won't be able to schedule any work on it for the time being.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>