Summary
Migrate production call sites from the current SegmentedButton usage to the stabilized selector-family primitive after the demo/API/naming pass is complete.
This issue intentionally follows the first-pass selector-family work.
Why
Once the selector primitive name/API are reviewed and stabilized, the production call sites should align so the v2 frontend uses a coherent selector-family primitive instead of a partially local component.
Scope
Migrate and align production usage sites such as:
AgcPanelDspPanelRxAudioPanelRfFrontEnd- any thin wrappers using the same selector primitive
Review adjacent selector-specific wrappers such as AttenuatorControl and reduce coupling if needed, but keep the scope tight and reviewable.
Requirements
- preserve current keyboard navigation and accessibility
- preserve selected-state behavior for string and numeric values
- preserve or improve styling consistency with the Radio UI Control System
- keep migration narrow and low-risk once the primitive is ready
Non-goals
- do not expand into BandSelector redesign unless separately scoped
- do not redesign value controls or panel chrome here
- do not reopen primitive naming/API decisions already settled by the prior issue
Outcome
At the end of this issue, production selector usage should consistently rely on the stabilized selector-family primitive and its approved API.
Related
Summary
Migrate production call sites from the current
SegmentedButtonusage to the stabilized selector-family primitive after the demo/API/naming pass is complete.This issue intentionally follows the first-pass selector-family work.
Why
Once the selector primitive name/API are reviewed and stabilized, the production call sites should align so the v2 frontend uses a coherent selector-family primitive instead of a partially local component.
Scope
Migrate and align production usage sites such as:
AgcPanelDspPanelRxAudioPanelRfFrontEndReview adjacent selector-specific wrappers such as
AttenuatorControland reduce coupling if needed, but keep the scope tight and reviewable.Requirements
Non-goals
Outcome
At the end of this issue, production selector usage should consistently rely on the stabilized selector-family primitive and its approved API.
Related