Preview controls could not be applied. The static default fixture remains available.
§01
Contract
Semantics first
Anatomy
Uses input type=search and a native button; label, description, and error IDs remain explicit.
Consumer classes, styles, and data attributes may extend the surface, but required roles, IDs, relationships, and handlers remain owned by the component.
Keyboard
Tab focuses the search field and then the visible clear button.
Native text-editing and search-field keys are preserved.
Enter follows the surrounding form contract; the clear button activates with Enter/Space and returns focus to the input.
§02
Public surface
API & styling
Props
id
Explicit IDs override stable generated IDs.
class / style
Consumer additions compose with required styles.
ref
Element or callback where focus control is expected.
children
Typed content; raw HTML strings are never rendered.
Slots & events
children
Primary content slot.
onChange
Typed value plus a small reason object when state changes.
import SearchField from 'PRIVATE_BETA_PACKAGE_COORDINATE_REDACTED/SearchField';
<SearchField>Frauthy content</SearchField>
Astroisland
---
import SearchField from 'PRIVATE_BETA_PACKAGE_COORDINATE_REDACTED/SearchField';
---
<SearchField client:visible>Frauthy content</SearchField>
§04
Verification
Evidence record
Scheduled
Automated
Batch D form tests cover controlled/default input, clear and reset reasons, labels/descriptions/errors, disabled/read-only state, and focus restoration.
Target
Brand 1.0.0-next.0 matrix
Last verified
Pending integrated G2 run
Required
Assistive technology
Pending VoiceOver/Safari and NVDA/Firefox search-field role, clear-label, and error announcement verification.
Desktop
VoiceOver/Safari · NVDA/Firefox
Touch
Required for touch-centric behavior
Open
Known issues
The component does not debounce or submit searches; those policies belong to the consumer.
§05
Editorial guidance
Do / don’t
Do
Keep the visible label persistent and localize the clear action.
Don’t
Do not use placeholder text as the only label or trigger network requests without an explicit loading state.
There is no stable predecessor for this explicit compiled subpath. The v1 compatibility layer remains tested separately; visual and API diffs begin with the next prerelease.