Shortcuts are context-aware, in pdf (when pdf is opened with edge pdf-viewer) - CTRL + [ rotates PDF counter-clockwise 90° and CTRL + ] rotates PDF clockwise 90°, whereas in DevTools, CTRL + [ focuses the next panel CTRL + ] focuses the previous panel, both adhering to the persistent user-defined tool tabs order in activity bar.
But these two shortcuts have no global mapping and are currently unmapped in the standard browser context.
Keeping in parity with CTRL + [/] behavior in DevTools, I propose utilizing same two shortcuts in standard browser context (the one we use to browse webpages), CTRL + [ and CTRL + ] respectively initializes/launches DevTools with focus on index 0 and index -1 tool tab in the activity bar adhering to the persistent user-defined tool tabs order.
This creates consistent mental model, as the keys that navigate panels within DevTools would now launch DevTools to the user-specified first or last panel in Activity Bar right from webpage(s).
This new behavior would only aid the existing DevTools launch shortcuts (CTRL + SHIFT + I/J), that are hardcoded to specific panels (Elements and Console), which does not fully utilize the persistent user-defined tool tabs order in activity bar.
In professional/intense workflows, specifically those not centered on DOM manipulation (graphics, performance, or network heavy debugging) the forced Elements or Console creates interaction friction. automating the focus to the user's preferred first and last tool saves repetitive manual switching, which I personally found to be really really annoying.
Reference ->
Shortcuts are context-aware, in pdf (when pdf is opened with edge pdf-viewer) -
CTRL + [rotates PDF counter-clockwise 90° andCTRL + ]rotates PDF clockwise 90°, whereas inDevTools,CTRL + [focuses the next panelCTRL + ]focuses the previous panel, both adhering to the persistent user-defined tool tabs order inactivity bar.But these two shortcuts have no global mapping and are currently unmapped in the standard browser context.
Keeping in parity with
CTRL + [/]behavior inDevTools, I propose utilizing same two shortcuts in standard browser context (the one we use to browse webpages),CTRL + [andCTRL + ]respectively initializes/launchesDevToolswith focus onindex 0andindex -1tool tabin theactivity baradhering to the persistent user-defined tool tabs order.This creates consistent mental model, as the keys that navigate panels within
DevToolswould now launchDevToolsto the user-specified first or last panel inActivity Barright from webpage(s).This new behavior would only aid the existing
DevToolslaunch shortcuts (CTRL + SHIFT + I/J), that are hardcoded to specific panels (ElementsandConsole), which does not fully utilize the persistent user-defined tool tabs order inactivity bar.In professional/intense workflows, specifically those not centered on DOM manipulation (graphics, performance, or network heavy debugging) the forced
ElementsorConsolecreates interaction friction. automating the focus to the user's preferred first and last tool saves repetitive manual switching, which I personally found to be really really annoying.