[meta] Accidental use of F12
Categories
(DevTools :: General, task)
Tracking
(Not tracked)
People
(Reporter: Honza, Unassigned)
References
(Depends on 3 open bugs)
Details
(Keywords: meta)
Tracking bug for all F12 related work
Honza
|
||
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'DevTools::Netmonitor' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
|
||
Updated•3 years ago
|
Might I ask why there has been no progress in fixing this problem? For, is it not an easy win, so to speak? Let me explain.
Mozilla wants to increase the appeal of Firefox to less technical users. This change would do that (by removing something that presumably puts such user off). At the same time, an annoyance for savvier users would be removed. Is there a worry that developers would be upset if, say, <shift> were added to the shortcut? Can a discussion at least not be had?
|
|
||
Comment 4•2 years ago
•
|
||
(In reply to JN from comment #3)
Might I ask why there has been no progress in fixing this problem? For, is it not an easy win, so to speak? Let me explain.
Mozilla wants to increase the appeal of Firefox to less technical users. This change would do that (by removing something that presumably puts such user off). At the same time, an annoyance for savvier users would be removed. Is there a worry that developers would be upset if, say, <shift> were added to the shortcut? Can a discussion at least not be had?
Sorry for the lack of updates, we are definitely working on this in the coming weeks and implementation should start soon.
As to "why no progress": team is small, and even if we want for this to happen it is not a top priority compared to breaking bugs, mandatory refactor etc...
Is there a worry that developers would be upset if, say, <shift> were added to the shortcut? Can a discussion at least not be had?
We want to keep the F12 shortcut available, because it's the main entry point for devtools and we don't want to create friction for users already relying on this. But we think that making the F12 shortcut optional and adding an onboarding step for new users is a good compromise and that's what we are going to implement. Edge implemented something similar a few months ago, and it seems like a good approach.
Thanks. Just what is being implemented, though? The asking of new users whether or not they want F12 to behave as it does at present?
'[W]e are definitely working on this in the coming weeks and implementation should start soon.' I am not on the 'developer' edition of Firefox and yet I feel that time is falsifying that claim.
I, and I imagine many other users, continue to be vexed by the problem. New users who hit F12 accidentally will wonder what has happened (and there are reports of that on the web) and experienced users, especially those on laptops, will continue to hit the wrong key by accident and get irritated as a result.
|
|
||
Comment 9•11 months ago
|
||
Hi,
This is still in the team's backlog, but I didn't have time to implement this yet and this is not really high priority.
I would also really like this to make progress, and I'm sorry about that.
Just what is being implemented, though? The asking of new users whether or not they want F12 to behave as it does at present?
There are two main things we want to add:
- show an onboarding popup for first time users when they press F12 so that they can decide if it should open DevTools or not
- add an option in DevTools settings (and Firefox settings potentially) to decide if F12 should open devtools or not
Description
•