[Bug]: Controls not showing on first load in 8.5.0 (web components)

[tbz]

Describe the bug

When upgrading from 8.4 to 8.5.0 in our Lit/web components project we noticed that the controls panel was empty for every story.
When you opened the story a second time the controls would show up as expected/as it did in 8.4.

I can reproduce the same problem in the example project you get when running npx storybook@latest init in an empty folder, and also in the default stackblitz.

Reproduction link

https://stackblitz.com/github/storybookjs/sandboxes/tree/next/lit-vite/default-ts/after-storybook?embed=1&file=README.md

Reproduction steps

1. If you show the mobile experience, resize window/frame to get the desktop experience
2. Click on the story Button > Secondary
3. If not visible, expand the addons panel

Expected result:
Controls show up

Result:
Controls do not show up

Workaround:
Click on another story and then click on Button > Secondary again. The controls are now visible.

System

Storybook Environment Info:

  System:
    OS: Windows 10 10.0.19045
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
  Binaries:
    Node: 20.18.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.8.2 - C:\Program Files\nodejs\npm.CMD <----- active
  Browsers: {}
  npmPackages:
    @storybook/addon-essentials: ^8.5.0 => 8.5.0 
    @storybook/blocks: ^8.5.0 => 8.5.0 
    @storybook/test: ^8.5.0 => 8.5.0 
    @storybook/web-components: ^8.5.0 => 8.5.0 
    @storybook/web-components-vite: ^8.5.0 => 8.5.0
    storybook: ^8.5.0 => 8.5.0

Additional context

No response

[corbanbrook]

I am experiencing the same thing.

Controls pane show:

"Interactive story playground
Controls give you an easy to use interface to test your components. Set your story args and you'll see controls appearing here automatically."

Clicking on the Actions tab and then back to the Controls tab causes the controls to load properly.

[corbanbrook]

Also note that if you initialize a storybook project via:

pnpx storybook@latest init

when running in dev mode with npm run storybook I notice the same broken behavior on the Button story example.