Thomas Mäder

Turns out in `browser/hosted-plugin.ts#acceptPlugin()`, sometimes returns false for a bunch of plugins.

I finally got to the bottom of this: the problem came with the introduction of back-end plugins: there is a `Deferred` in `hosted-plugin-deployer-handler.ts` called `backendPluginsMetadataDeferred`. Since headless plugins are deployed...

The fact that `TabGroups.activeTabGroup` can be undefined causes an Exception at startup in the `typescript-language-features` 1.88.1 version

In principle, I'd argue that the VS Code folks are dead wrong, because their own typing says the only thing you can create a `Range` with is an `instanceof Position`...

We can close this one once we have reached VS Code 1.89, then. Thanks for the analysis.

The trouble is that the `openRootMenu` function does not take such a parameter. @sdirix maybe another patch we can propose once we move to Lumino.

@planger did you already have an idea on how to fix this in Phosphor menu case?

I've been able to hack the phosphor menu code to handle the multi-window case. Still a ways to go, but in principle, it should work. The necessary changes probably need...

Didn't we have a repo where "community-supported" packages would live after removing them from the main repo?

Btw: when I write "blockers" the meaning is "blocking adoption of Theia as the main dev platform for Theia", not that you can't use Theia at all.