On 3/5/25 16:14, Neal Gompa wrote:
On Wed, Mar 5, 2025 at 6:38 AM Imobach Gonzalez Sosa <igonzalezs...@suse.com> wrote:Hi all,While discussing how to prevent users "escaping" from the kiosk mode (see [1] and [2]), we started questioning whether we should use a kiosk at all. These days, users are familiar with browsers, so I don't know which benefits the kiosk brings. OK, it looks like and application... so what? We will find more corner cases and need to put more effort into hiding the browser for, IMHO, a marginal benefit. What do you think? Regards, Imo [1] https://github.com/agama-project/agama/issues/2112 [2] https://github.com/agama-project/agama/issues/1509 PS: it could start in full-screen mode if we want to avoid seeing the browser from the very beginning.Why are you using Firefox for this? Why not use a simple WebKitGTK shell runner instead? Cockpit has one that can be reused. * Launcher: https://github.com/cockpit-project/cockpit/blob/main/src/ws/cockpit-desktop.in * Runner: https://github.com/cockpit-project/cockpit/blob/main/src/client/cockpit-client Being a browser window is more useful in live environments (which Agama does not support), full-screen kiosk on top of Weston would make sense leveraging this.
I discuss this topic also with Anaconda guys and basically agreement was that main reason is beside firefox stability also its performance as usually during our testing we find that with complex js page ( which agama and also web anaconda is ) firefox eats less memory and perform better. There is other benefits like development ecosystem around, but it is not so important. Also so far all our attempts to try some lightweight browser on top of wayland compositor ends with graphical glitches that was out of our area of expertise. So really unless we have maintainer in SUSE that can maintain it for all supported architecture I do not see way how to use it and support it.
Josef
OpenPGP_0x5795B05DBC562F48.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
