Closed
Bug 878412
Opened 12 years ago
Closed 11 years ago
Use F12 to open the Toolbox
Categories
(DevTools :: Framework, defect)
DevTools
Framework
Tracking
(Not tracked)
RESOLVED
FIXED
Firefox 25
People
(Reporter: rcampbell, Assigned: rcampbell)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [landed-in-fxteam])
Attachments
(3 files, 1 obsolete file)
4.79 KB,
patch
|
dcamp
:
review+
|
Details | Diff | Splinter Review |
4.36 KB,
patch
|
Details | Diff | Splinter Review | |
6.87 KB,
patch
|
Details | Diff | Splinter Review |
We need a single key to open the Devtools. I think we should use F12.
Comment 1•12 years ago
|
||
That conflicts with Firebug, which could be a bad idea if we want the two to coexist.
Comment 2•12 years ago
|
||
I agree with Simon of course.
Honza
Assignee | ||
Comment 3•12 years ago
|
||
Agreed, that's bad and we have a problem with it on Macs anyway that apparently still map F12 to Dashboard.
Shift-F12 if Firebug's installed?
Comment 4•12 years ago
|
||
Firebug binds Shift-F12 to "disable". Not sure how many people use it, but at least I do.
Comment 5•12 years ago
|
||
Here is how Firebug is using F12:
Win+Lin Mac
Open Firebug Panel F12 F12
Close Firebug Panel F12 F12
Deactivate Firebug Shift + F12 Shift + F12
Open Firebug in window Ctrl + F12 ⌘ + F12
See also:
https://getfirebug.com/wiki/index.php/Keyboard_and_Mouse_Shortcuts
Honza
Although I haven't played Quake et al in a very long time, my brain is hard-wired to hit the backtick/tilde key when wanting to open the browser console. I hit F12 reluctantly...
Even as a secondary key binding, it would make a great easter egg!
More info on origins of backtick for console:
http://en.wikipedia.org/wiki/Console_(video_game_CLI)
Comment 7•12 years ago
|
||
Can we consider Cmd-Opt-I? I know it's used by the inspector now, but parity with Chrome, no conflict with Firebug (I think).
Comment 8•12 years ago
|
||
(In reply to Heather Arthur [:harth] from comment #7)
> Can we consider Cmd-Opt-I? I know it's used by the inspector now, but parity
> with Chrome, no conflict with Firebug (I think).
The bad thing, imho, with Chrome's shortcuts is that none of the three is tool specific. Even Cmd Opt I opens the last opened tool.
If we are planning to let remain the Inspector's, Console's and Debugger's shortcuts as is, then we might not be able to use Cmd Opt I to toggle toolbox.
Comment 9•12 years ago
|
||
(In reply to Girish Sharma [:Optimizer] from comment #8)
> (In reply to Heather Arthur [:harth] from comment #7)
> > Can we consider Cmd-Opt-I? I know it's used by the inspector now, but parity
> > with Chrome, no conflict with Firebug (I think).
>
> The bad thing, imho, with Chrome's shortcuts is that none of the three is
> tool specific. Even Cmd Opt I opens the last opened tool.
To me that's good! I need a last-opened-tool shortcut.
> If we are planning to let remain the Inspector's, Console's and Debugger's
> shortcuts as is, then we might not be able to use Cmd Opt I to toggle
> toolbox.
Yes, the inspector shortcut would have to change.
Comment 10•12 years ago
|
||
(In reply to Heather Arthur [:harth] from comment #9)
> (In reply to Girish Sharma [:Optimizer] from comment #8)
> > (In reply to Heather Arthur [:harth] from comment #7)
> > > Can we consider Cmd-Opt-I? I know it's used by the inspector now, but parity
> > > with Chrome, no conflict with Firebug (I think).
> >
> > The bad thing, imho, with Chrome's shortcuts is that none of the three is
> > tool specific. Even Cmd Opt I opens the last opened tool.
>
> To me that's good! I need a last-opened-tool shortcut.
> > If we are planning to let remain the Inspector's, Console's and Debugger's
> > shortcuts as is, then we might not be able to use Cmd Opt I to toggle
> > toolbox.
>
> Yes, the inspector shortcut would have to change.
Yes we need that. I agree. But lets not change an already popular shortcut's behavior this drastically. Inspector and Console are very widely used, changing their shortcuts might be too much of a surprise for the user.
Comment 11•12 years ago
|
||
(In reply to Girish Sharma [:Optimizer] from comment #10)
> Yes we need that. I agree. But lets not change an already popular shortcut's
> behavior this drastically. Inspector and Console are very widely used,
> changing their shortcuts might be too much of a surprise for the user.
I don't think it's a drastic change. It'll still open the devtools window, and they could read the new Inspector shortcut on the menu. The tools really aren't that widely used right now, in my perception. ~15,000 inspector opens on Nightly/Aurora in the past week.
We need a shortcut for toggling the tools. It would be ideal to use the same shortcut as another popular set of tools. If F12, some part of the 3 million Firebug users would be very annoyed. I think that leaves Cmd+Opt+I .
Comment 12•12 years ago
|
||
(In reply to Heather Arthur [:harth] from comment #11)
> I don't think it's a drastic change. It'll still open the devtools window,
> and they could read the new Inspector shortcut on the menu. The tools really
> aren't that widely used right now, in my perception. ~15,000 inspector opens
> on Nightly/Aurora in the past week.
It would be awesome to have a similar number for Firebug and then we can compare to form a decision. [i.e The number of times Firebug got open using F12 in last week]
Comment 13•12 years ago
|
||
Nick mentioned that we could use F12 (in addition to Cmd-Opt-I), but make sure Firebug overrides it.
Comment 14•12 years ago
|
||
Bug for Ctrl+Shift+I/Cmd+Opt+I: bug 892168
Updated•12 years ago
|
Blocks: devtools-shortcuts
Assignee | ||
Comment 16•11 years ago
|
||
For the first pass of this, I'm going to add the F12 shortcut if Firebug is not present.
Blocks: 900061
Comment 17•11 years ago
|
||
I want F12 to work more than anything else in the entire world.
Assignee | ||
Comment 18•11 years ago
|
||
Attachment #784107 -
Flags: review?(dcamp)
Updated•11 years ago
|
Attachment #784107 -
Flags: review?(dcamp) → review+
Assignee | ||
Updated•11 years ago
|
Whiteboard: [land-in-fx-team]
Comment 19•11 years ago
|
||
landed in fx-team : https://hg.mozilla.org/integration/fx-team/rev/fa4afb7214ae
But .. no tests ?
Whiteboard: [land-in-fx-team] → [fixed-in-fx-team]
Updated•11 years ago
|
Status: NEW → ASSIGNED
Comment 20•11 years ago
|
||
Backed out for talos xperf regressions.
https://hg.mozilla.org/integration/fx-team/rev/9ce5efc16a8c
https://tbpl.mozilla.org/php/getParsedLog.php?id=26069958&tree=Fx-Team
Updated•11 years ago
|
Whiteboard: [fixed-in-fx-team]
Comment 21•11 years ago
|
||
for reference, the xperf regression was that we were accessing new files at startup (a perf regression) due to the addon manager being instantiated.
Assignee | ||
Comment 22•11 years ago
|
||
Assignee | ||
Comment 23•11 years ago
|
||
Attachment #785098 -
Attachment is obsolete: true
Comment 24•11 years ago
|
||
Comment on attachment 785102 [details] [diff] [review]
bug-878412-F12 v2b
Review of attachment 785102 [details] [diff] [review]:
-----------------------------------------------------------------
::: browser/devtools/framework/gDevTools.jsm
@@ +415,5 @@
> + * @return promise
> + */
> + _isFirebugInstalled: function DT_isFirebugInstalled() {
> + let bootstrappedAddons = Services.prefs.getCharPref("extensions.bootstrappedAddons");
> + return bootstrappedAddons.indexOf("firebug@software.joehewitt.com") != -1;
return bootstrappedAddons.contains("firebug@software.joehewitt.com");
Assignee | ||
Comment 25•11 years ago
|
||
whatever. Quit harshin' my code. :P
Comment 26•11 years ago
|
||
Rebased
Comment 27•11 years ago
|
||
https://tbpl.mozilla.org/?tree=Fx-Team&rev=79edca22de3f
https://hg.mozilla.org/integration/fx-team/rev/79edca22de3f
Whiteboard: [landed-in-fxteam]
Comment 28•11 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 25
Updated•7 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•