Closed
Bug 855641
Opened 13 years ago
Closed 9 years ago
Error Console: Accel+F should focus the filter bar
Categories
(Toolkit Graveyard :: Error Console, defect)
Toolkit Graveyard
Error Console
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: alfredkayser, Unassigned)
References
Details
Why not change the key from Alt-F to the more usual Ctrl-F? (or use both?)
Ctrl-F is used in many programs and within the Mozilla apps as the search key. Using Alt-F is a strange deviation from the standard.
Comment 1•13 years ago
|
||
Alt-F is exposed to the user (as of bug 801266) whereas there's no place to expose Ctrl-F, as the error console doesn't have a menu bar.
Comment 2•13 years ago
|
||
Of course, that doesn't mean we can't support it in the back for muscle memory (similar to the way we support both Accel+Y and Accel+Shift+Z for "Undo" and Accel+G and F3 for "Find Again").
The terminology here was kind of wonky. Accel+F *is* Ctrl+/Cmd+F; accel is not the same as Alt/"the accesskey modifier". Also, we don't have to (and shouldn't) _replace_ it. We can have both.
Summary: Error Console: Replace Accel-F with Command-F → Error Console: Accel+F should focus the filter bar
Comment 3•9 years ago
|
||
The Error Console has been removed in favor of the Browser Console (see Bug 1278368), and the component is going to be removed. If this bug is also relevant in the Browser Console, please reopen and move this into Firefox -> Developer Tools: Console.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Comment 4•9 years ago
|
||
I am mass-reopening and re-componenting every single one of the Toolkit:Error Console bugs that appear to have been closed without anyone even *glancing* at whether they were relevant to the Browser Console.
If you want to close a whole bunch of old bugs -- FOR ANY REASON -- it is YOUR RESPONSIBILITY to check EVERY SINGLE ONE OF THEM and make sure they are no longer valid. Do not push that work onto the bug reporters.
(It's okay to close bugs that haven't been touched in years when they don't have enough information for you to figure out whether the problem is still relevant to the current software - the reporter probably isn't coming back to clarify. But that is the ONLY situation where it is okay.)
(I'm going to have to do this in two steps because of the way the "change several bugs at once" form works. Apologies for the extra bugspam.)
Status: RESOLVED → REOPENED
Component: Error Console → Developer Tools: Console
Product: Toolkit → Firefox
Resolution: WONTFIX → ---
Version: unspecified → Trunk
Comment 5•9 years ago
|
||
Doesn't translate to browser console, so resolving
Status: REOPENED → RESOLVED
Closed: 9 years ago → 9 years ago
Component: Developer Tools: Console → Error Console
Product: Firefox → Toolkit
Resolution: --- → WONTFIX
| Assignee | ||
Updated•9 years ago
|
Product: Toolkit → Toolkit Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•