[number field] `onValueChange` not triggered on input blur (focusout) since v1.0.0-beta.1

[log7422]

Bug report

Current behavior

After upgrading from

"@base-ui-components/react": "1.0.0-beta.2"

to

"@base-ui-components/react": "1.0.0-beta.3"

the onValueChange callback signature has changed:

// before
event?: Event

// now
eventDetails: NumberField.Root.ChangeEventDetails

This change itself is fine, however I lost access to the focusout event.

When I increment/decrement the value via the NumberField controls, the onValueChange callback is triggered as expected.

But when I type a value directly into the input and then blur/lose focus (focusout), the onValueChange callback is not triggered anymore.

This breaks the previous behavior where changes were detected after editing the input manually and leaving the field.

Expected behavior

The onValueChange callback should also be triggered when the user enters a value manually and then blurs the input (focusout), not only when incrementing/decrementing.

Reproducible example

A minimal reproduction showing the difference between 1.0.0-beta.2 and 1.0.0-beta.3:
[CodeSandbox/StackBlitz link here if available]

Base UI version

@base-ui-components/react: 1.0.0-beta.3

[mj12albert]

This was a breaking change in beta.3 and the event is now in eventDetails.event, is this your issue? @log7422

[atomiks]

@log7422 the onValueChange callback no longer fires if the value didn't change on blur - is this your issue?

https://codesandbox.io/p/sandbox/hungry-cdn-sq6kwm

It still fires on blur if the value changed though. Do you have a repro where it doesn't?

Screen.Recording.2025-09-12.at.4.45.33.am.mov

[mj12albert]

the onValueChange callback no longer fires if the value didn't change on blur

This is the same behavior in beta.2 though, focus->blur without changing the value doesn't fire onValueChange

[log7422]

Thank you very much for your quick replies 🙏 and sorry for the confusion in my initial report regarding the version.

After running additional tests, I realized that I made a mistake: the issue is not introduced in 1.0.0-beta.3, but has actually been present since 1.0.0-beta.1.

When I downgrade my project to 1.0.0-beta.0, everything works correctly again.

The problem I am still experiencing is that the onValueChange event is no longer triggered when the value is changed by typing directly into the input and then blurring the field (focusout). Incrementing/decrementing with the controls still works as expected.

For now, I’ll temporarily keep my project on 1.0.0-beta.0 while I continue investigating on my side if this might be related to another package conflict.

Thanks again for your help and sorry for the earlier incorrect information!

[atomiks]

@log7422 thanks for the additional info. Though given the event is called in the CodeSandbox in beta.3 in the common scenarios, I'm not sure why it wouldn't be triggering for you. What is your locale / any custom formatting options used?

The changes in beta.1 are here - most likely the cause would be "Ensure onValueChange is called with already-formatted parsed value (#1905)", specifically the changes in the onBlur handler.

Also I'm curious if this PR preview release fixes it for you: #2725 (comment). I added a commit that should fix it: cf250f2

[github-actions]

This fix will be available in the next npm release of Base UI.

In the meantime, you can try it out on our Canary release channel:

npm i https://pkg.pr.new/@base-ui-components/react@2725