Closed
Bug 945916
Opened 11 years ago
Closed 5 years ago
F3 should jump to next result when doing text search in the debugger
Categories
(DevTools :: Debugger, defect, P3)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: jaws, Unassigned)
References
(Blocks 1 open bug)
Details
STR:
Open the Browser Debugger and load a script
Do a search for some text in the script that appears multiple times
Hit F3
ER:
Moves to the next search result
AR:
Nothing happens. It does move if you hit Enter, but F3 is the keybinding used in SublimeText (not sure how common it is outside of Sublime). Tested with Nightly 12/3/2013 on Win7.
Updated•11 years ago
|
Priority: -- → P3
Updated•10 years ago
|
Summary: Hitting F3 while performing a text search within a script should move to the next result → F3 should jump to next result when doing text search in the debugger
Updated•10 years ago
|
Blocks: dbg-frontend
In the Inspector it is ctrl+g and shift+ctrl+g (backwards) instead of F3. This is nowhere surfaced, I just know from Bug 1256658
I think that F3 is better known than ctrl+g but most important: it should be consistent (whithin devtools and with Firefox nativ search behaviour too)
Updated•6 years ago
|
Product: Firefox → DevTools
Comment 2•6 years ago
|
||
We already use ctrl+g and enter. Are there other examples of F3 being used within devtools?
Comment 3•5 years ago
|
||
Feel free to share your thoughts on F3. Closing for the time being.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•