Extensions which add Devtools panels/etc no longer do so as of Edge Dev 116.0.1908.0

[planetarian]

Not sure if this is the correct place for this, but here's the issue:

Verified:
Works on Edge Stable 114.0.1823.43
Fails on Edge Dev 116.0.1908.0
Fails on Edge Canary 116.0.1917.0

Extensions which implement custom devtools items (via chrome.devtools.panels.create/etc) no longer do so.

Verified with the following extensions:

Knockoutjs context debugger https://chrome.google.com/webstore/detail/knockoutjs-context-debugg/oddcpmchholgcjgjdnfjmildmlielhof

Should have a top-level devtools tab:

...as well as a sub-tab within Elements:

KanColle Command Center 改 https://chrome.google.com/webstore/detail/kancolle-command-center-%E6%94%B9/hkgmldnainaglpjngpajnnjfhpdjkohh

Should have a primary viewer tab:

...as well as a secondary API monitor tab you can enable:

None of the above appear on the affected Dev/Canary versions, despite other aspects of those plugins functioning normally.

I am unable to locate any console errors that might be produced by this.

AB#45067287

[captainbrosset]

Thanks so much for filing this and providing details.
I'll make sure the dev team knows about this and we'll get back to you here with more details once we have them.

[captainbrosset]

Quick update: the team was already aware and is working on it right now.

[captainbrosset]

A fix is on its way, but in the meantime, you can try launching Edge from the command line and passing the following parameter: --disable-features=DevToolsTabTarget. This should fix the issue temporarily.

[kretschmannj]

I think I'm seeing the same issue. I installed the LetXPath extension which adds a new LetXPath devtool tab but only in the first tab. Any subsequent tabs that I open are missing the LetXPath devtool tab. I've updated Edge, reinstalled the extension but to no avail. I also discovered that if I duplicate the first tab rather than creating a new tab then the devtools LetXPath tab will show.

[captainbrosset]

According to our internal bug tracker, the original issue has been fixed. So you might be having a different (but related) issue.
Just in case, could you please create a new issue on this repo? This way I can close this one and our team can start working on the new one.