Open Bug 892157 (devtools-shortcuts) Opened 11 years ago Updated 1 month ago

[meta] Keyboard shortcuts

Categories

(DevTools :: General, task)

x86
macOS
task

Tracking

(Not tracked)

People

(Reporter: fitzgen, Unassigned)

References

(Depends on 15 open bugs)

Details

(Keywords: meta)

This is a meta bug for all of the changes mentioned in the "hot, hot, hotkeys" thread on the mailing list.

TLDR: We should improve and clean up our keyboard shortcut situation!
Depends on: 892168
Depends on: 892180
Depends on: 892185
Depends on: 891556
No longer depends on: 892180
Depends on: 892188
Depends on: 879219
Depends on: 892192
Depends on: 892195
Depends on: 892217
Depends on: 878412
Depends on: 892233
Depends on: 892266
Depends on: 892268
Depends on: 892274
Depends on: 892275
Depends on: 892277
Depends on: 892278
Depends on: 892280
Depends on: 892282
Depends on: 892286
Depends on: 879028
Depends on: 892289
Depends on: 900271
Depends on: 888587
Alias: devtools-shortcuts
Depends on: 907310
Depends on: 907311
Depends on: 907316
Depends on: 907317
Depends on: 934088
Depends on: 923971
Depends on: 962665
Depends on: 967044
No longer depends on: 967044
Depends on: 977191
Depends on: 930313
Depends on: 1003153
Depends on: 1116951
Product: Firefox → DevTools
Summary: [meta] Keyboard shortcuts clean up → [meta] Keyboard shortcuts
Severity: normal → S3
Depends on: 1439740
Depends on: 1660823

Shouldn't bug 1660823 rather be marked as a duplicate of this one and its blocking bugs be moved to here? Or do you want to keep it as a tracker for Debugger shortcut issues? In that case, I suggest to rename that bug (and move all blockers that are more general to this one here).

As this meta-bug covers bugs and features, I changed its type to "task".

Sebastian

Type: defect → task
Flags: needinfo?(odvarko)

Good call, I renamed the debugger meta to "Debugger Keyboard shortcuts". I think we can keep it, it nicely separates Debugger shortcuts and it blocks this meta so it won't be forgotten.

Flags: needinfo?(odvarko)
You need to log in before you can comment on or make changes to this bug.