Closed Bug 1336815 Opened 7 years ago Closed 7 years ago

[e10s] Developer toolbox doesn't show up after restarting Firefox

Categories

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

51 Branch
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1345548

People

(Reporter: dehghani.m.c, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:51.0) Gecko/20100101 Firefox/51.0
Build ID: 20170125094131

Steps to reproduce:

Hit Shift+F2, type restart and hit Enter


Actual results:

Firefox got restart, but Developer toolbox doesn't show up after reloading, hitting Shift+F2 (or clicking on Developer Toolbox under Developer Icon from menu (wrench icon)) doesn't help.

If I close the browser & run that again, the Developer Toolbox is visible by default.

p.s: I reported this issue with Firefox 51, but it happens on 52.x too.


Expected results:

After restarting Developer toolbox must be visible, or at least show up after hitting Shift+F2 (or using menu)
Component: Untriaged → Developer Tools: Graphic Commandline and Toolbar
Summary: Developer toolbox doesn't show up after restarting Firefox → [e10s] Developer toolbox doesn't show up after restarting Firefox
@Mehdi: You say that the developer toolbox doesn't appear... do you mean the developer toolbar? The toolbox is where all of the tools like the markup view, CSS views etc. appear whereas the developer toolbar is the place you can type GCLI commands.

This works fine for me. Do you see any errors in the browser console?
Flags: needinfo?(dehghani.m.c)
Seems like this is intermittant and a good STR is in a duplicate bug.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Flags: needinfo?(dehghani.m.c)
Resolution: --- → DUPLICATE
@Michael, I'm sorry, I mean Developer Toolbar.
I didn't check browser console when it occurred. seems like you closed this one as duplicate of another one. hope the problem will be solved soon. thanks.
Product: Firefox → DevTools
Product: DevTools → DevTools Graveyard
You need to log in before you can comment on or make changes to this bug.