Popup windows don't work in weston kiosk mode

[Christopher Schnick]

As an update to this, it seems like the setAutoHide(true) method for 
PopupWindows causes this. When excplicitly using setAutoHide(false), the 
problem is fixed. Sadly, some skins like ComboBoxPopupControl set this 
to true without an option to change this.

I was able to fix this issue by calling setAutoHide(false) when possible 
and using reflection to fix the other cases where skins set it implicitly.

On 20/12/2025 7:36 AM, Christopher Schnick wrote:
> Over the last few days, I have been experimenting with the new Android 
> Linux terminal: 
> https://www.zdnet.com/article/how-to-use-the-new-linux-terminal-on-android/. 
> It uses a somewhat customized weston wayland setup in kiosk mode to 
> make it work on the phone screen.
>
> JavaFX applications run fine on it, and the performance is actually 
> decent. The only thing that does not work are PopupMenus. They don't 
> register mouse clicks (the events sent are normal mouse events, so no 
> touchscreen mode here). The system is designed for a touchscreen, so 
> there are no mouse move events or anything like that sent. Only mouse 
> button events are sent. When using the actual phone touch screen, it 
> also only sends mouse button events.
>
> When clicking on any popup menu, it just closes without registering 
> the click. The only exception when it works is if the parent node of 
> the popup window is behind the click location. I recorded a video to 
> showcase the problem. The only time the click registers is at the end 
> when the button that opens the menu is behind the open PopupMenu where 
> it is clicked. The "Set default" menu item works one time if it is 
> clicked right on top of the "..." button, but does not work if the 
> click location does not hit the "..." button.
>
> If anyone has an idea of what to do with this problem, let me know. I 
> can test things, I just don't know how one would get started 
> troubleshooting this issue.
>
> Best
> Christopher Schnick