UI: Mark Autocomplete, Field, and Fieldset as recommended

[mirka]

What?

Marks Autocomplete, Field, and Fieldset from @wordpress/ui as recommended for use in a WordPress environment.

Why?

Autocomplete has been reviewed for style consistency, overlays compatibility, and API completeness. Field and Fieldset are the recommended companions for labeling and grouping form controls, and are often necessary alongside Autocomplete.

BaseControl remains recommended for now. It will eventually be superseded by Field, but there is not yet a direct replacement for BaseControl.VisualLabel, which is the majority use case for BaseControl. We'll probably want to add a Field.VisualLabel to cover this, since a normal Field.Label carries semantics and can only be used within a Field.Root.

How?

• Adds Autocomplete, Field, and Fieldset to the @wordpress/ui allow-list in the use-recommended-components ESLint rule.
• Updates the Storybook stories: sets componentStatus to recommended and adds the manifest tag for the @wordpress/ui components.
• Updates the Storybook manifest snapshot and prop description allowlist for the newly manifest-listed components.

Testing Instructions

1. Open Storybook and confirm Autocomplete, Field, and Fieldset show as recommended in the component status.
2. Confirm BaseControl still shows as recommended.

[github-actions]

Size Change: 0 B

Total Size: 7.75 MB

_{compressed-size-action}

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: mirka <0mirka00@git.wordpress.org>
Co-authored-by: ciampo <mciampini@git.wordpress.org>
Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[ciampo]

Same comment as #81658 re. adding accessible labels.

Separately, I'm not sure we should advertise using type="url" in Autocomplete.Input (and potentially rendering that same compnent as textarea) as it seems that the official aria spec permits combobox on input type="text", while URL inputs and textareas permit only textbox 🤔 Base UI does it, but it may warrant a deeper look.

Finally, is the Storybook manifest missing Fieldset.Legend, Fieldset.Description, and Fieldset.Details ? (and potentially root props too?)

[mirka]

Same comment as #81658 re. adding accessible labels.

I'll add some broad guidance here for this pass (fefc612), and follow up to point to labeling guidance in each of the primitives, and maybe add aria-labels for the general examples. (reference)

Separately, I'm not sure we should advertise using type="url" in Autocomplete.Input (and potentially rendering that same compnent as textarea) as it seems that the official aria spec permits combobox on input type="text", while URL inputs and textareas permit only textbox 🤔 Base UI does it, but it may warrant a deeper look.

TIL! Fixed. Also removed the type prop on the Input subcomponents for both combobox families.

Finally, is the Storybook manifest missing Fieldset.Legend, Fieldset.Description, and Fieldset.Details ? (and potentially root props too?)

Fixed 👍

[ciampo]

LGTM 🚀

Good to merge once remaining feedback is addressed

[ciampo]

Consumers would still be able to use render, eg doing render={ <Input type="url" /> } or render={ <textarea /> }.

Depending on how much we wan to enforce this, we may want to make the render type stricter, and / or force the type to text at runtime

[Mamaduka]

Nice. I'll follow up with a few refactoring changes, like #76986 (comment), once this is merged.