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 165984 - lockdown key to disable context menus?
lockdown key to disable context menus?
Status: RESOLVED OBSOLETE
Product: epiphany
Classification: Core
Component: General
git master
Other Linux
: Normal enhancement
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on: 332968
Blocks:
 
 
Reported: 2005-02-01 22:52 UTC by Christian Persch
Modified: 2018-03-30 16:26 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Description Christian Persch 2005-02-01 22:52:50 UTC 
Split from bug 165550:
> Btw, do you think that a lockdown key for "disable-context-menu" could be 
> useful too?
Comment 1 Diego Escalante Urrelo (not reading bugmail) 2006-08-11 06:53:44 UTC 
As far as I see, context menues are anyway pretty useless if you have access to the keyboard, so blocking them would not offer any advantage.
Am I wrong?

(It would be intimidating anyway)
Comment 2 Reinout van Schouwen 2007-12-18 21:25:27 UTC 
The question is: what actions do you want to block by locking down the context menu?

If the admin disables the menu bar to prevent people from accessing the file system and the context menu still offers Save as on links, then we've failed in the eyes of the admin. 

Even more interesting: what if the admin wants to prevent people from setting nudie pictures as desktop background? This option is available from the context menu *only*, afaik. 

I think we should either have 'functional' lockdown keys that cover all  functionality that can be accessed via the context menu (disable_navigation, disable_filesystem_access) or we take the easy route and add the disable_context_menu key, as suggested in the bug description.
Comment 3 Michael Catanzaro 2018-03-25 17:47:20 UTC 
This is a mass NEEDINFO of all Epiphany bugs with no activity in the past three years. I'm going to be automatically closing old bugs to help us focus on current problems. If you feel this bug is still relevant with Epiphany 3.26 or newer, then please leave any comment here so that I know not to close this one.
Comment 4 Michael Catanzaro 2018-03-30 16:26:54 UTC 
This is a mass-close of old bugs currently in the NEEDINFO state.

If you think this bug is still relevant, please leave a comment.