Closed Bug 697142 Opened 13 years ago Closed 8 years ago

GCLI should allow node selection to pick between multiple matches

Categories

(DevTools Graveyard :: Graphic Commandline and Toolbar, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: jwalker, Unassigned)

Details

Mihai:
> When the selector I write matches multiple elements I just get an inline
> message that tells me how many matches have been found. I think most often
> users will type selectors that match multiple elements (this is really the
> most common use-case). Allow us to select the node we want from keyboard and
> from mouse (display the list and allow up/down through the list). If I press
> Enter inspect the node I picked, if I don't press up/down ... just select
> the first match.
> 
> Writing document.querySelector() is more productive in this case. Even
> querySelectorAll() because I can just type querySelectorAll()[2] to select
> the third match.
Moving GCLI bugs to Developer Tools: Console. Filter on 'baked beans are off'.
Component: Developer Tools → Developer Tools: Console
Triage. Filter on PEGASUS.
Priority: -- → P3
No longer blocks: GCLI-FUTURE
New component triage. Filter on "Lobster Thermidor aux crevettes with a Mornay sauce"
Component: Developer Tools: Console → Developer Tools: Graphic Commandline and Toolbar
Resetting priorities because these P* levels are very out of date.
Sorry for the bug spam. Filter on Lobster Thermidor
Priority: P3 → --
Triage. Filter on Lobster Thermidor.
Nice idea, but no need to keep on file.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Product: Firefox → DevTools
Product: DevTools → DevTools Graveyard
You need to log in before you can comment on or make changes to this bug.