[Field] The initial value is not validated and the validation is inconsistent

[nsmag]

Bug report

Current behavior

Field does not validate the initial value and the validation is inconsistent and incorrect.

With this code:

<Field.Root>
  <Field.Label>Email</Field.Label>
  <Field.Control type="email" defaultValue="not_an_email@" />
</Field.Root>

<Field.Root>
  <Field.Label>Email</Field.Label>
  <Field.Control type="email" value="not_an_email@" />
</Field.Root>

The root div initially has only data-filled. When I focus then blur without typing anything, it gets data-valid. But if I type something (to make it dirty) and revert back to old value, it gets data-invalid. The input always has :invalid pseudo-class in these scenarios.

Expected behavior

• Field should validate the initial value (I'm not sure if this behavior is intended or not).
• The validation should be consistent between dirty value and non-dirty value.

Base UI version

v1.0.0-alpha.8

Which browser are you using?

Chrome

Which OS are you using?

Mac OS

[atomiks]

Field should validate the initial value (I'm not sure if this behavior is intended or not).

This one is expected - it only validates on blur by default, but it requires it to have been marked dirty to reduce error noise, however this should probably only apply to required validation (to check empty values) rather than anything else

The validation should be consistent between dirty value and non-dirty value.

This one looks like a bug, addressing how required validation works should also fix this

[mj12albert]

Field should validate the initial value

I was thinking if there was a realistic use-case for this and came across: https://github.com/orgs/react-hook-form/discussions/10267#discussioncomment-5784152

Another example could be when loading a shopping cart, the saved quantity/available quantity of something has changed so the initial value is invalid

Could the validate function be exposed with actionsRef so it can be called arbitrarily?