4 ms·

Gmail is now overriding browser right-click to provide a custom contextual menu

23 points by doomlaser 13y ago

This is a clear example of a design anti-pattern that often crops up with new Google interfaces. There is no setting to turn it off, and it nukes the browser's standard right click contextual menu for opening links in new tabs and windows, copying urls, etc when clicking on messages. Designers, please just stop with this kind of thing. It's not acceptable to change the behavior of a standard. fundamental browser interface in your site design.

nickporter 13y ago
That's just like, your opinion, man.. It's called a context menu for a reason. It is a menu that offers options based on your current context. If you think of gmail as an application and not just a website, it makes sense no? That said, I think it would be better if the browser would expose an API that would let you manipulate the native context menu.
- Jasper_ 13y ago
  They do: http://davidwalsh.name/html5-context-menu http://davidwalsh.name/html5-context-menu
  - nickporter 13y ago
    Oh interesting, thanks for the link!
az 13y ago
Agreed.
sp332 13y ago
In Firefox, head to about:config and find dom.event.contextmenu.enabled, double-click it to turn it off. That way it will show the normal context menu on top of any custom menus.
ars 13y ago
This is really the browsers fault, not the designers. Right click is a useful way to interact with something, but it's unfortunate the browser only offers all or nothing. Either have a browser context menu, or override it and have nothing. We need a way to have both. I suggest the browser give the designer a fixed size box (size queryable at runtime) and the designer can put anything in there. This box shows up together with the regular context menu, but with a special border to mark it as part of the page.
d0m 13y ago
I understand your point and would agree for most parts, but I'm not sure how standard is that behavior. I.e. Before seeing your message, I've never really right-clicked on anything. Maybe to bring the web inspector on an element? What I often do that is I see more and more not working is the ctrl+click to open a link in a new tab. Oh, actually, if I ctrl+click and it doesn't work, I will usually right+click and "open in a new tab".. So, yeah, if both doesn't work, then I won't be happy.
- DharmaPolice 13y ago
  >Before seeing your message, I've never really right-clicked on anything. Really? I find myself using the right-click context menu all the time; "Open Link in New Window", "Save Image", "Copy" and (appropriately enough) "Search Google for x" I use multiple times an hour during normal web usage. Yes, I use keyboard shortcuts for these things as well, but if I'm on the phone or drinking from a cup then some shortcuts are awkward. Anyway, the most annoying thing about this sort of feature is that there's no obvious visual cues to help anticipate non-standard behaviour. I get the same mouse pointer icon when I hover over "Inbox", "Sent Items", etc that I do when hovering over my email subjects. Yet I get different behaviour when right-clicking either control. This makes for an unsatisfying user experience IMHO.
pestaa 13y ago
I've been thinking about this for some time now. If the browser is really to become the common platform for most applications in the future, shouldn't they be able to declare whatever interaction they desire? There are long articles on the internet why the right click is a suboptimal way to interact with anything on-screen, but users who need the contextual menu already learnt it. Can't we make those menus more useful?
tkjchjtkcj 13y ago
"it nukes the browser's standard right click contextual menu for opening links in new tabs and windows, copying urls, etc when clicking on messages." That is incorrect. It only appears to work for the message list (where the browser context menu is not necessary anyhow) but in the message itself the right click works as usual.
dylan8902 13y ago
There is new technology called 'Context Menus' designed to solve this problem, but is yet to be implemented in any browser. The idea being web apps can augment menu options to the existing browser menu. http://www.whatwg.org/specs/web-apps/current-work/multipage/interactive-elements.html#context-menus http://www.whatwg.org/specs/web-apps/current-work/multipage/...
rhythmvs 13y ago
They (designers) do it to keep you from sniffing their handycraft code with the inspector. (That’s a joke.) The browser is no webpage-viewer-app any longer. Especially not when the “page” is actually a full-fledged webapp. As soon as an app begins to be an app viewer, it’s really become an OS. (At least the Web is the OS, and browsers implement the frontend layer.) Imagine the right-click context menu on Windows or OSX would be the same, all times, in all apps. Not much “context”, no? One could claim those browser right-click context menus hadn’t to be there at all: at least, they’ve been “polyfills” with generic defaults, awaiting the (right, contextual) functionality being implemented by the webapps themselves. Granted, they were useful, back when web pages were just static hypertext documents and browsers were mere html viewers. Browsers will continue to play that schizofrenic role for some time, both as a document viewer, and as a UI renderer. But eventually we will need two separate “web surfing” apps. This is also what’s going on, I guess, when you here people complaining about pervasive javascript, progressive enhancement, and their demand that all web “pages” must support their no-js browser plugins indifferently. The Web is more than pages: we got webapps now.
pattle 13y ago
I actually like it
RexRollman 13y ago
The real answer is to stop using Gmail. And probably Google products in general.

23 points by doomlaser 13y ago

nickporter 13y ago

That's just like, your opinion, man.. It's called a context menu for a reason. It is a menu that offers options based on your current context. If you think of gmail as an application and not just a website, it makes sense no? That said, I think it would be better if the browser would expose an API that would let you manipulate the native context menu.

Jasper_ 13y ago
They do: http://davidwalsh.name/html5-context-menu http://davidwalsh.name/html5-context-menu
- nickporter 13y ago
  Oh interesting, thanks for the link!

az 13y ago

Agreed.

sp332 13y ago

In Firefox, head to about:config and find dom.event.contextmenu.enabled, double-click it to turn it off. That way it will show the normal context menu on top of any custom menus.

ars 13y ago

This is really the browsers fault, not the designers. Right click is a useful way to interact with something, but it's unfortunate the browser only offers all or nothing. Either have a browser context menu, or override it and have nothing. We need a way to have both. I suggest the browser give the designer a fixed size box (size queryable at runtime) and the designer can put anything in there. This box shows up together with the regular context menu, but with a special border to mark it as part of the page.

d0m 13y ago

I understand your point and would agree for most parts, but I'm not sure how standard is that behavior. I.e. Before seeing your message, I've never really right-clicked on anything. Maybe to bring the web inspector on an element? What I often do that is I see more and more not working is the ctrl+click to open a link in a new tab. Oh, actually, if I ctrl+click and it doesn't work, I will usually right+click and "open in a new tab".. So, yeah, if both doesn't work, then I won't be happy.

DharmaPolice 13y ago
>Before seeing your message, I've never really right-clicked on anything. Really? I find myself using the right-click context menu all the time; "Open Link in New Window", "Save Image", "Copy" and (appropriately enough) "Search Google for x" I use multiple times an hour during normal web usage. Yes, I use keyboard shortcuts for these things as well, but if I'm on the phone or drinking from a cup then some shortcuts are awkward. Anyway, the most annoying thing about this sort of feature is that there's no obvious visual cues to help anticipate non-standard behaviour. I get the same mouse pointer icon when I hover over "Inbox", "Sent Items", etc that I do when hovering over my email subjects. Yet I get different behaviour when right-clicking either control. This makes for an unsatisfying user experience IMHO.

pestaa 13y ago

I've been thinking about this for some time now. If the browser is really to become the common platform for most applications in the future, shouldn't they be able to declare whatever interaction they desire? There are long articles on the internet why the right click is a suboptimal way to interact with anything on-screen, but users who need the contextual menu already learnt it. Can't we make those menus more useful?

tkjchjtkcj 13y ago

"it nukes the browser's standard right click contextual menu for opening links in new tabs and windows, copying urls, etc when clicking on messages." That is incorrect. It only appears to work for the message list (where the browser context menu is not necessary anyhow) but in the message itself the right click works as usual.

dylan8902 13y ago

There is new technology called 'Context Menus' designed to solve this problem, but is yet to be implemented in any browser. The idea being web apps can augment menu options to the existing browser menu. http://www.whatwg.org/specs/web-apps/current-work/multipage/interactive-elements.html#context-menus http://www.whatwg.org/specs/web-apps/current-work/multipage/...

rhythmvs 13y ago

They (designers) do it to keep you from sniffing their handycraft code with the inspector. (That’s a joke.) The browser is no webpage-viewer-app any longer. Especially not when the “page” is actually a full-fledged webapp. As soon as an app begins to be an app viewer, it’s really become an OS. (At least the Web is the OS, and browsers implement the frontend layer.) Imagine the right-click context menu on Windows or OSX would be the same, all times, in all apps. Not much “context”, no? One could claim those browser right-click context menus hadn’t to be there at all: at least, they’ve been “polyfills” with generic defaults, awaiting the (right, contextual) functionality being implemented by the webapps themselves. Granted, they were useful, back when web pages were just static hypertext documents and browsers were mere html viewers. Browsers will continue to play that schizofrenic role for some time, both as a document viewer, and as a UI renderer. But eventually we will need two separate “web surfing” apps. This is also what’s going on, I guess, when you here people complaining about pervasive javascript, progressive enhancement, and their demand that all web “pages” must support their no-js browser plugins indifferently. The Web is more than pages: we got webapps now.

pattle 13y ago

I actually like it

RexRollman 13y ago

The real answer is to stop using Gmail. And probably Google products in general.