1631254 - When a DevTools panel created by an extension is closed and reopened, it defaults to the console panel

Status: NEW

(WebExtensions :: Developer Tools, defect, P3)

Description

[Deleted Account]

User Agent: Mozilla/5.0 (X11; CrOS x86_64 12739.111.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.162 Safari/537.36

Steps to reproduce:

1. Open a DevTools panel created by an extension.
2. Close then reopen the toolbox.

Actual results:

Defaults to console panel.

Expected results:

Should go back to the extension panel.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Comment 2

[Daniel Orban]

Hello,
Could you please add the steps on how to open the DevTools panel created by the extension and also which extension you use to reproduce the issue?
Thank you!

Comment 3

[Deleted Account]

(In reply to Daniel Oran from comment #2)

Hello,
Could you please add the steps on how to open the DevTools panel created by the extension and also which extension you use to reproduce the issue?
Thank you!

I tested with Site Compatibility Tools but any DevTools extension does this.

Steps to reproduce:

1. Download any DevTools extension. An example of one of these is Site Compatibility Tools.
2. Open the toolbox and select the extension's panel.
3. Close and reopen the toolbox.
4. When the toolbox is reopened, it defaults to the console panel instead of the extension panel.

Comment 4

[Daniel Orban]

Thank you @Nicohumor!
I have managed to reproduce the issue on the latest Nightly (77.0a1/20200428100141), Beta (76.0/20200427162639), Release (75.0/20200403170909) under Windows 10 Pro 64-bit.
The Toolbox is reopened to the "Console" panel by default when the extension panel is selected before closing. The issue is not reproducible to the other panels (eg. if you select the "Memory" panel, the same panel is selected after reopening).

Comment 5

[Luca Greco [:rpl] [:luca] [:lgreco]]

Unfortunately this is not as easy as it would be if the devtools panel would be declared in the extension manifest, the manifest just specify a devtools_page (which is an invisible page, similar to a background page, but 1-1 with the particular devtools toolbox) and the devtools_page may or may not create a devtools panel (even asynchronously) after it has been loaded.

Needinfo-ing myself to take a look into possible way to handle this (and then discuss about it with the DevTools team)

Comment 6

[Deleted Account]

(In reply to Luca Greco [:rpl] [:luca] [:lgreco] from comment #5)

Unfortunately this is not as easy as it would be if the devtools panel would be declared in the extension manifest, the manifest just specify a devtools_page (which is an invisible page, similar to a background page, but 1-1 with the particular devtools toolbox) and the devtools_page may or may not create a devtools panel (even asynchronously) after it has been loaded.

Needinfo-ing myself to take a look into possible way to handle this (and then discuss about it with the DevTools team)

Then how about loading the script when the panel is closed instead of opened?

Comment 7

[Firefox Bug Husbandry Bot]

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (non,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)