On 3/5/25 4:14 PM, Neal Gompa wrote:
On Wed, Mar 5, 2025 at 6:38 AM Imobach Gonzalez Sosa
<[email protected]> 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.
For SLE we need to use something that is part of the distribution and
that is fully supported by the SUSE maintenance team.
* 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
If we would go that way (which implies finding a maintainer for the
package, the YaST Team does not want to commit for LTS maintainership),
we would likely not use something based on Python. After all, the whole
GTK minibrowser is only 1k lines of C code.
Cheers.
--
Ancor González Sosa
YaST Team at SUSE Software Solutions
