User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:56.0) Gecko/20100101 Firefox/56.0 Build ID: 20170825011442 Steps to reproduce: Version: Firefox Developer Edition 56.0b4 Category: Proposal I wanted to open the Inspector from the context menu to have a look at a specific item within the page. Due to my muscle brain I went for the last item in the menu. Actual results: ... but, of course, the new screenshot mode as been entered. Expected results: ... instead of opening the inspector. Proposal: As long as I remember, it was the last item in the context menu, so it is a somewhat learned behaviour. Furthermore, the position of the menu item is consistent with all other major browsers, which is valuable for frontend devs. Under the assumption that a user (developer) more frequently wants to inspect an element rather then taking a screenshot, I propose to make the menu item called "Inspect Element" the last one again. E.g. by switch the position of "Take a Screenshot" and "Inspect Element".
Status: UNCONFIRMED → NEW
Has STR: --- → yes
Component: Developer Tools: Inspector → Menus
Ever confirmed: true
Severity: normal → enhancement
Priority: -- → P3
Summary: [Proposal] Make "Inspect Element" last item again in context (or: remove "Take a Screenshot" from last position) → [Proposal] Make "Inspect Element" last item again in context menu (or: remove "Take a Screenshot" from last position)
From an extensions point-of-view, I would have no issue move Inspect Element back to the bottom. When I talked to Markus Jaritz about it, he thought it might make sense to move all of the "developer" related item to the bottom, with extension menu items just above that. He proposed: Quick navigation icons --- Website specific html menu elements --- Browser provided functionality --- Extension provided functionality --- Developer functionality (source, info, inspect) I have also heard from John Gruen that having the Screenshots menu item at the bottom is their biggest complaint (from developers who expect Inspect Element to be there). Following Markus's suggestion would move Screenshots to above the developer related items, since Screenshots is implemented as an extension.
John, I'm pretty sure this bug is wontfix as the positioning of the Screenshots item was very intentional. Can you confirm? If possible it would be nice to add a link to where the decision was made.
No, this bug is correctly filed. It's actually a follow on of discussion that came out of this issue: https://bugzilla.mozilla.org/show_bug.cgi?id=1325758 FWIW, we've seen a lot of feedback from Screenshots users requesting that we do the work outlined in this bug.
mconca, still getting complaints about this, should we move components to WebExtensions?
I'm going to pass the buck (needinfo) along to Andy to see if this bug should be owned by his team.
Flags: needinfo?(mconca) → needinfo?(amckay)
If the bug is to move WebExtensions context menus insertions up the list, then sure. Although this will break everyone's workflow, again. This is probably a pretty simple bug about changing how the menus are attached somewhere in https://searchfox.org/mozilla-central/source/browser/components/extensions/ext-menus.js#39 Similar this is bug 1325758, which wanted to specify the specific insertion point for each context menu. That was rejected. This is similar to bug 1393108, which also wanted to move it away from the bottom.
> If the bug is to move WebExtensions context menus insertions up the list, then sure. Although this will break everyone's workflow, again. Sounds correct, per mconca's proposal of moving the menu above the Developer Tools section.
You need to log in before you can comment on or make changes to this bug.