789675 - Better integrate GCLI and the Web Console

Status: RESOLVED INCOMPLETE

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

Description

[Joe Walker [:jwalker]]

mrpollo opened https://github.com/mozilla/gcli/issues/61 which asks for keyboard accelerators to switch between the firefox command line and the web console. This seems like a reasonable request.

We should also consider this request in the wider context of removing the confusion between the firefox command line, web console, scratchpad, etc.

Comment 1

[Paul Rouget [:paul]]

Link is 404.

Comment 2

[Joe Walker [:jwalker]]

Original Text:

Navigation between the control elements can be a useful way of moving around between the JSTerm and the Web Console.

Examples (use cases):
Example 1.

Game canvas with resize event captured, on the JSTerm you change the window size "resize to 300 300" then you want to move to the Web Console to check on your variables, right now you can only do "console open" assuming its not already open, on which your only option is to click on the web console input field.
Image 1

Example 1 - Image 1
Image 2

Example 1 - Image 2
Example 2.

Again related to resize, once you resized you decide you want to change some properties on the of your html so you open the inspector "inspect body" if focus was passed to the style inspector we could potentially write the rules with the keyboard then navigate back to the JSTerm to either close the inspector and keep resizing or do another changes
Image 1

Example 2 - Image 1
Proposed key bindings:

a combination of either this could work

Move forward: Command + option + ]
Move backwards: Command + option + [

Comment 3

[Joe Walker [:jwalker]]

Attachment: image 1

Comment 4

[Joe Walker [:jwalker]]

Attachment: image 2

Comment 5

[Joe Walker [:jwalker]]

Attachment: image 3

Comment 6

[Joe Walker [:jwalker]]

New component triage. Filter on "Lobster Thermidor aux crevettes with a Mornay sauce"

Comment 11

[Firefox Bug Husbandry Bot]

Per bug 1491875, this component has been closed, and the affected code is being removed from Firefox. Closing this bug as incomplete.