[Bug]: Unwanted 'reset' option on globals

[mrginglymus]

Describe the bug

Since 10.1 (possibly 10.0?) my toolbar globals have had a new 'Reset selection` option.

Clicking this sets the global value to the string _reset, which is obviously undesirable.

I would expect it to either

1. set it to defaultValue
2. set it to the initial value
3. set it to undefined
4. not be there

Reproduction link

https://stackblitz.com/edit/github-w91nbsqm?file=.storybook%2Fpreview.ts,src%2Fstories%2FConfigure.mdx,.storybook%2Fmain.ts&preset=node

Reproduction steps

No response

System

-

Additional context

No response

[dosubot]

This is a bug in the current implementation. The 'Reset selection' option in the toolbar sets the global value to the string _reset, but nothing in the codebase recognizes this as a signal to revert to the default or initial value. Instead, it just writes _reset into your globals, which is not intended behavior. The expected approach would be to set the value to undefined, which would trigger a reset to the initial value as managed by the global state logic. Right now, there is no built-in way to configure or remove the reset option, or to have it set the value to the initial/default value as you described.

You can track for updates in future releases or consider patching your local ToolbarMenuSelect to set undefined instead of '_reset' as a workaround.
For reference, see the implementation details here and here.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[Sidnioulz]

I'm not sure this is a regression vs an old quirk we haven't ironed out. The _reset behaviour occurred in Storybook < 10 but reset options weren't visible by default.

I need to check:

• Did I accidentally switch reset options to on by default for global tools?
• Was there any change in the handling of _reset within the core package? Was it handled and removed, or was it never handled?
• What happens if I replace _reset with something else?

[mrginglymus]

My top preference would be to have the reset removed (or the abilityy to remove it) - even if it worked as expected, it doesn't offer much utility.

[shilman]

@mrginglymus @Sidnioulz This is a bug. I'd prefer a fix to the underlying problem. But agree with the fix of removing the reset UI if we don't have a fix for that now.