After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 702433 - Add kiosk mode GSetting
Add kiosk mode GSetting
Status: RESOLVED INVALID
Product: epiphany
Classification: Core
Component: General
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks: 702432
 
 
Reported: 2013-06-17 09:34 UTC by Manuel Rego Casasnovas
Modified: 2013-11-28 07:13 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Manuel Rego Casasnovas 2013-06-17 09:34:52 UTC
For the moment we will add a new boolean setting "kiosk-mode" to enable/disable it. Default value will be FALSE.
Comment 1 Claudio Saavedra 2013-06-24 14:21:21 UTC
I think it would be useful to define what exactly would a kiosk mode in Epiphany comprise, and get the designers in the loop to know how does this fit into a general GNOME lockdown mode.
Comment 2 Manuel Rego Casasnovas 2013-06-25 10:53:43 UTC
(In reply to comment #1)
> I think it would be useful to define what exactly would a kiosk mode in
> Epiphany comprise, and get the designers in the loop to know how does this fit
> into a general GNOME lockdown mode.

This specific bug is only related to add the GSetting to enable disable this mode. At least it seems a valid approach for the first steps during the initial development.

Let's move the general discussion to the meta-bug #702432 about the kiosk mode, I'll post a new message there and add the relevant people to CC. Claudio, thanks for the feedback anyway :-)
Comment 3 Manuel Rego Casasnovas 2013-11-28 07:13:45 UTC
This setting seems to not be needed as it'd be just the same than enable different settings (homepage, only 1 tab/window, fullscreen, etc.) and the specific list of settings to enable/disable might vary in different use cases.

Closing as INVALID.