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 139849 - Print should be on the page context menu in epiphany
Print should be on the page context menu in epiphany
Status: RESOLVED INVALID
Product: epiphany
Classification: Core
Component: Interface
unspecified
Other All
: Normal enhancement
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on: 332968
Blocks:
 
 
Reported: 2004-04-12 21:31 UTC by Christian Rose
Modified: 2012-12-11 17:09 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description Christian Rose 2004-04-12 21:31:41 UTC
"Print" should probably be a menu item present on the right click page context
menu in Epiphany.

Currently, "Print" seems to not be present as an option when right-clicking on a
page. Printing to get a hard copy of what's currently being rendered on screen
is arguably one of the most fundamental features of a web browser, and while
Epiphany's goal of keeping menus short and easy to navigate is a very good one,
it can probably be effectively argued that Printing still belongs on the menu.

As for an actual use case where this lack of a Print menu item caused problems,
I'll describe the one of my mom, a case which I happened to observe today. She
used an Internet banking application, and one of the detailed account pages
opens by javascript in a smaller window without menus, toolbars and status bars.
She wanted to get a hard copy as usual of the contents of the screen for her own
notes, but this to her proved not possible since there was no Print option on
the only available menu, the right click one. I knew about the Ctrl+P shortcut,
but she naturally didn't. Still, I doubt she'll remember it, and I'm not sure
it's fair to ask that she should.
Comment 1 Christian Persch 2004-06-01 13:39:48 UTC
Once we've decided if we _want_ this, it's easy to fix.
However I'm not sure we need this, wouldn't it be better if we fixed bug 141999
instead? Then you could activate the menubar even when it's hidden, and choose
print from the usual location.
Comment 2 Christian Rose 2004-06-01 19:48:30 UTC
You're suggesting that the mom-type users should learn to first use the hidden
"F10" shortcut for bringing forward the toolbar, in order to be able to get a
hard copy of a page?
That solution would perhaps work for geeks and otherwise computer-savvy people,
but certainly not for mom-type users. I'm amazed she even knew about right
click, but talking about remembering hidden keyboard shortcuts is so much
another galaxy for her occasional computer usage that it's almost amusing.
Comment 3 Marco Pesenti Gritti 2004-06-01 23:09:56 UTC
I guess it's matter of deciding which features are worth to expose in the
document context menu.
Possibilities:

Print
Send To
Zoom In/Out
Find
Page Source

Of these the only really necessary one (in the case of no menubar) seem to
actually Print.

For some reason I still feel Print in the menubar a bit odd. But I dont have a
rational excuse for it ;) Maybe because no other app does it ...

Another thing I'm unsure is about printing being a fundamental feature. I think
it was decided to not have a toolbar button to not encourage people to print
webpages and I sort of agree with that feeling. Though I guess that doesnt
exclude the fact that some times is absolutely necessary for user to print a
page and we should make possible to do it also for no menubar popups.

CCing clarkbw to see if he has an opinion. This sounds like a good candidate for
ui review ;)
Comment 4 Christian Persch 2004-08-23 15:18:09 UTC
-> Interface
Comment 5 Christian Persch 2004-10-13 10:53:23 UTC
Mass reassigning of Epiphany bugs to epiphany-maint@b.g.o
Comment 6 Reinout van Schouwen 2005-12-30 01:43:29 UTC
This isn't gnome-love but usability, it needs ui-review so it's not an easy fix.
Bryan could you give a comment please?
Comment 7 Christian Persch 2006-02-03 13:38:09 UTC
-> 1.12 due to feature and UI freeze.
Comment 8 Christian Persch 2006-08-17 14:04:34 UTC
Mass changing target 2.16 -> 2.18
Comment 9 Christian Persch 2007-03-12 12:25:12 UTC
Moving to 2.20 target due to feature and UI freeze for 2.18.
Comment 10 Christian Persch 2007-08-27 20:42:55 UTC
Moving Severity:enhancement bugs off of 2.20 target.
Comment 11 Reinout van Schouwen 2007-12-18 21:29:35 UTC
Bryan: ping?
Comment 12 Diego Escalante Urrelo (not reading bugmail) 2012-12-11 17:09:17 UTC
We are going to clean the context menus. This is not going in :P.