2 ms·

It's been that way in Firefox for as long as I can remember (user since Firefox started). I believe the actual intent is that the right click menu is a "contex

by Steltek 11y ago

It's been that way in Firefox for as long as I can remember (user since Firefox started). I believe the actual intent is that the right click menu is a "context" menu and not a shortcut menu. In this, case, the context is that you have text highlighted. Without a selection, the context is the page.

kazinator 11y ago
(Yet somehow, the NoScript add-on's command ends up on all these menus, haha!) Here is a point also: if you make a selection in one tab, and switch to another tab, the selection in the original tab persists. Yet in the other tab, the context menu is that of the page. This underscores the page versus selection semantics. Yet, it would probably be more effective if the context menu were the same, just with certain things greyed out based on state. For instance in, oh, Notepad on Windows (let's drag out that user interface superstars, why don't we) if you have text selected then the context menu enables Cut. If you don't have text selected, then Cut is still there, but greyed out. Hey look, it is that way in this very Firefox edit box that I'm typing in. The fact that we don't see "Cut" in the page context menu is just as bad as that we don't see the backbutton when there is a selection. Seeing a disabled Cut lets us know that we can select something and then Cut will be available. On that topic, here is another thing: the page context menu has Select All. That makes it clear that the context menu has a relationship to selections.
SmellyGeekBoy 11y ago
Agreed, It seems to work the same way in Chrome as well. I'm not sure what the problem is?
- reitanqild 11y ago
  It seems to work the same way in Chrome as well. I'm not sure what the problem is? The problem is for some of us (fast typist/clickers) it breaks consistency. Suddenly, out of the blue, for no good reason, the user interface changes and my plan of action fails. No big deal but it is part of death by thousand papercuts. The reason is so non-intuitive that people has made it all the way to reporting it on bugzilla[0] without clear steps to reproduce..! . A second unrelated problem with your argument: "... It seems to work the same way in Chrome as well". For some of us FF/FF-flone users that is not a very convincing argument. : ) [0]: https://bugzilla.mozilla.org/show_bug.cgi?id=1144394 https://bugzilla.mozilla.org/show_bug.cgi?id=1144394

by Steltek 11y ago

kazinator 11y ago

(Yet somehow, the NoScript add-on's command ends up on all these menus, haha!) Here is a point also: if you make a selection in one tab, and switch to another tab, the selection in the original tab persists. Yet in the other tab, the context menu is that of the page. This underscores the page versus selection semantics. Yet, it would probably be more effective if the context menu were the same, just with certain things greyed out based on state. For instance in, oh, Notepad on Windows (let's drag out that user interface superstars, why don't we) if you have text selected then the context menu enables Cut. If you don't have text selected, then Cut is still there, but greyed out. Hey look, it is that way in this very Firefox edit box that I'm typing in. The fact that we don't see "Cut" in the page context menu is just as bad as that we don't see the backbutton when there is a selection. Seeing a disabled Cut lets us know that we can select something and then Cut will be available. On that topic, here is another thing: the page context menu has Select All. That makes it clear that the context menu has a relationship to selections.

SmellyGeekBoy 11y ago

Agreed, It seems to work the same way in Chrome as well. I'm not sure what the problem is?

reitanqild 11y ago
It seems to work the same way in Chrome as well. I'm not sure what the problem is? The problem is for some of us (fast typist/clickers) it breaks consistency. Suddenly, out of the blue, for no good reason, the user interface changes and my plan of action fails. No big deal but it is part of death by thousand papercuts. The reason is so non-intuitive that people has made it all the way to reporting it on bugzilla[0] without clear steps to reproduce..! . A second unrelated problem with your argument: "... It seems to work the same way in Chrome as well". For some of us FF/FF-flone users that is not a very convincing argument. : ) [0]: https://bugzilla.mozilla.org/show_bug.cgi?id=1144394 https://bugzilla.mozilla.org/show_bug.cgi?id=1144394