Transient preferences lost when view popped out

[colin-grant-work]

Description

In recent versions of VSCode, webviews, including Memory Inspector windows, can be popped out into floating windows. However, when Memory Inspector windows are popped out, local preference settings made through the advanced configuration are lost.

How to reproduce:

1. Open a memory inspector window and load some memory.
2. Use the advanced configuration dialog to modify local settings (e.g. groups per row - easily visible)
3. Drag the tab outside of the current VSCode window and drop it to create a new floating window.
4. Observe that the groups per row setting reverts to the original default and the local setting is lost.

Expected behavior

4. The local setting should be retained and respected.

At the moment, the values of the inputs are retained, so potentially whatever mechanism we're using to retain that information could be used.

Environment

• OS: Linux
• Browser: Desktop VSCode (Chromium)
• Theia or VS Code Version: VSCode 1.89

Additional information