Skip to content

feat: modernize RadioButton for MD3 - #5007

Open
burczu wants to merge 31 commits into
callstack:mainfrom
burczu:feat/radio-button-md3
Open

burczu wants to merge 31 commits into
callstack:mainfrom
burczu:feat/radio-button-md3

Conversation

@burczu

@burczu burczu commented Jun 19, 2026 •

Copy link
Copy Markdown

Motivation

RadioButton still shipped as two platform-specific implementations (RadioButtonAndroid, RadioButtonIOS) with the iOS variant rendering a checkmark glyph rather than a Material radio. This is inconsistent with the rest of the v6 MD3 work (Checkbox, Switch, TextInput, FAB) and diverges from the M3 radio button spec.

This PR unifies RadioButton into a single MD3 component that mirrors the modernized Checkbox structure (single component, tokens.ts, error prop, accessible={false} inner control), without pulling in Checkbox's reanimated/focus-ring machinery (out of scope — radio ships with none today).

Related issue

Closes #4938

What changed

  • Unified component — merged RadioButtonAndroid + RadioButtonIOS into a single MD3 RadioButton (Android impl as base). Dropped RadioButton.Android, RadioButton.IOS, RadioButtonIOS, and the RadioButton.Item mode prop.
  • Tokens — new RadioButton/tokens.ts (MD3 dims 20/10/2 + color roles); colors resolved via tokens in utils.
  • error prop — added to RadioButton and RadioButton.Item (ring + dot use theme.colors.error; disabled/custom colors take precedence).
  • Single animation path (reanimated) — collapsed two RN Animated.Values into one shared value and migrated to react-native-reanimated (matching Checkbox): dot scales in with overshoot on selection, keyed on checked so it also animates inside a RadioButton.Group. Uses theme.motion MD3 duration/easing tokens and respects reduce-motion.
  • Disabled opacity — the control now dims to 38% (selectionControlOpacity was previously computed but never applied).
  • Group perf — memoized the provider value + stabilized onValueChange with use-latest-callback; consumers switched from Context.Consumer to useContext.
  • Item a11y — inner control is accessible={false} + container importantForAccessibility="no-hide-descendants", so a screen reader sees one radio per row; dropped per-radio accessibilityLiveRegion; labelMaxFontSizeMultiplier=1.5 + ${testID}-text for CheckboxItem parity.
  • Docs/examples — updated examples (Group/Item, leading/trailing, error checked+unchecked, disabled); removed the iOS-mode demo and the RadioButtonAndroid/RadioButtonIOS doc pages.

Breaking changes

  • Removed RadioButton.Android, RadioButton.IOS, RadioButtonIOS (and RadioButtonAndroidProps/RadioButtonIOSProps exports).
  • Removed the RadioButton.Item mode prop.
  • error prop added (no visual change for existing usage).

Test plan

  • yarn typescript, yarn lint, yarn test (snapshots updated) — green.
  • yarn --cwd docs build — green.
  • Manually verified on iOS sim, Android emulator, and web: single selection, dot scale-in (standalone and in a Group), error (checked/unchecked), disabled dimming, leading/trailing, ripple, single a11y node per Item row.

Videos

radio_ios.mp4
radio_android.mp4
radio_web.mp4

@burczu
burczu marked this pull request as ready for review June 19, 2026 12:07
@burczu
burczu requested a review from satya164 June 19, 2026 12:15
@satya164
satya164 requested a review from Copilot June 28, 2026 16:21
@satya164

Copy link
Copy Markdown
Contributor

can you rebase the PR against main?

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR modernizes RadioButton for Material Design 3 by replacing the prior platform-specific implementations with a single unified component, introducing MD3 token-based sizing/color resolution, and aligning behavior (animation, error/disabled states, a11y, and group performance) with the library’s other MD3 selection controls.

Changes:

  • Unifies RadioButton into a single MD3 implementation (removing RadioButton.Android, RadioButton.IOS, and the RadioButton.Item mode prop) and migrates selection animation to react-native-reanimated.
  • Adds MD3 radio tokens + error support, applies disabled opacity consistently, and updates selection-control color resolution to use tokenized theme roles.
  • Improves RadioButton.Group context stability and updates tests/examples/docs accordingly (including removing platform-specific docs pages).

Reviewed changes

Copilot reviewed 23 out of 23 changed files in this pull request and generated 3 comments.

Show a summary per file
File Description
src/index.tsx Removes exported platform-specific RadioButton prop types.
src/components/RadioButton/utils.ts Updates selection-control color resolution to use RadioButton tokens and removes iOS-specific helper.
src/components/RadioButton/tokens.ts Introduces MD3 radio sizing + color-role tokens.
src/components/RadioButton/RadioButtonItem.tsx Removes mode, adds error, switches to useContext, and adjusts a11y/testID behavior.
src/components/RadioButton/RadioButtonGroup.tsx Memoizes context value and stabilizes onValueChange with use-latest-callback.
src/components/RadioButton/RadioButtonAndroid.tsx Deletes old Android-specific implementation.
src/components/RadioButton/RadioButtonIOS.tsx Deletes old iOS-specific implementation.
src/components/RadioButton/RadioButton.tsx Implements unified MD3 RadioButton with Reanimated dot-scale animation, tokenized sizes/colors, and updated a11y behavior.
src/components/RadioButton/index.ts Removes .Android/.IOS static exports from RadioButton.
src/components/tests/RadioButton/utils.test.tsx Updates tests to cover getSelectionControlColor including error/checked/unchecked cases.
src/components/tests/RadioButton/RadioButtonItem.test.tsx Removes platform-mode tests and adds a11y single-node assertion.
src/components/tests/RadioButton/RadioButtonGroup.test.tsx Adds test asserting stable context object across unrelated parent rerenders.
src/components/tests/RadioButton/RadioButton.test.tsx Simplifies snapshots to single unified RadioButton implementation.
src/components/tests/RadioButton/snapshots/RadioButtonItem.test.tsx.snap Updates snapshots for new unified control + a11y changes.
src/components/tests/RadioButton/snapshots/RadioButtonGroup.test.tsx.snap Updates snapshots for new unified control rendering.
src/components/tests/RadioButton/snapshots/RadioButton.test.tsx.snap Updates snapshots for unified control rendering.
example/src/Examples/RadioButtonItemExample.tsx Updates example to remove mode variants and demonstrate error/disabled states.
example/src/Examples/RadioButtonGroupExample.tsx Updates example usage to RadioButton (no platform statics).
example/src/Examples/RadioButtonExample.tsx Updates example states, adds error demos, and adjusts disabled label styling.
docs/versioned_docs/version-6.x/components/RadioButton/RadioButtonItem.mdx Removes documentation for the deleted mode prop.
docs/versioned_docs/version-6.x/components/RadioButton/RadioButtonIOS.mdx Removes iOS-specific docs page.
docs/versioned_docs/version-6.x/components/RadioButton/RadioButtonAndroid.mdx Removes Android-specific docs page.
docs/docusaurus.config.js Removes nav entries for the deleted platform-specific docs pages.

@burczu
burczu force-pushed the feat/radio-button-md3 branch from cb74fc8 to c0e1c18 Compare July 2, 2026 12:25
burczu added 5 commits July 2, 2026 14:33
- Fix accessibilityLabel variable reference (ariaLabel, not accessibilityLabel)
- Make sync render() calls async in RadioButton and RadioButtonItem tests
- Await rerender() in RadioButtonGroup stability test
- Use screen.queryAllByRole instead of destructuring from render result
- Update snapshots to reflect accessibilityRole instead of role prop
Nested ternary indentation left misaligned after conflict resolution.
RadioButtonAndroid and RadioButtonIOS were removed but the navigation
index still referenced them, breaking the docs build.
RadioButtonAndroid and RadioButtonIOS source mappings caused the docs
build to fail with ENOENT since the files no longer exist.
- Restore onPress type to (e: GestureResponderEvent) => void to match TouchableRipple
- Merge consumer style with container style, handling function-style props
- Guard RadioButtonItem label testID to avoid "undefined-text" when testID is not provided
Comment on lines +7 to +11
const sizes = {
ringSize: 20,
dotSize: 10,
outlineWidth: 2,
} as const;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what about adding an explicit state-layer size token & sizing touchable accordingly?

current 20dp ring with 8dp margins produces 36dp state layer, while MD3 defines radio state layer as 40dp.
modernized Checkbox component already uses the same 40dp state-layer token (source)

so could we change it to:

Suggested change
const sizes = {
ringSize: 20,
dotSize: 10,
outlineWidth: 2,
} as const;
const sizes = {
ringSize: 20,
dotSize: 10,
outlineWidth: 2,
stateLayerSize: 40,
} as const;

and use like that in RadioButton.tsx:

const {
  ringSize,
  dotSize,
  outlineWidth: OUTLINE_WIDTH,
  stateLayerSize,
} = RadioButtonTokens;

const styles = StyleSheet.create({
  container: {
    width: stateLayerSize,
    height: stateLayerSize,
    borderRadius: stateLayerSize / 2,
    alignItems: 'center',
    justifyContent: 'center',
  },
  radio: {
    height: ringSize,
    width: ringSize,
    borderRadius: ringSize / 2,
    borderWidth: OUTLINE_WIDTH,
  },
});

…into feat/radio-button-md3

# Conflicts:
#	src/components/RadioButton/RadioButtonAndroid.tsx
#	src/components/RadioButton/RadioButtonIOS.tsx
#	src/components/RadioButton/RadioButtonItem.tsx

@MikitasK MikitasK left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • updated radio-button state layer to MD3 specified 40dp size while keeping visible ring centered at 20dp
  • added reusable stateLayerSize token & removed previous margin-based state-layer sizing
  • made nested visual control inside RadioButton.Item non-focusable with focusable={false} and tabIndex={-1} keeping outer item as the only interactive radio
  • added regression coverage for 40dp state layer & updated affected accessibility & component snapshots

@JKobrynski

Copy link
Copy Markdown
Collaborator

@MikitasK is this ready for another review?

@JKobrynski JKobrynski left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add a ### RadioButton entry to docs/6.x/docs/guides/migration.md. The iOS variant drew a checkmark, so anyone on it gets a visibly different control. #5059 has a ### Checkbox section covering the identical removals that would work as the template, but it skips RadioButton and still lists RadioButton.Android / RadioButton.IOS as live. Worth syncing with @mikolajadamowicz on which PR carries it.

@JKobrynski

Copy link
Copy Markdown
Collaborator

We've settled the 48dp question: controls grow to 48dp rather than getting an invisible tap area. Could touchTarget.ts go, with RadioButton growing its box like Checkbox does in #5104? The Checkbox change here can go too, since #5104 covers it.

@MikitasK

Copy link
Copy Markdown
Contributor

We've settled the 48dp question: controls grow to 48dp rather than getting an invisible tap area. Could touchTarget.ts go, with RadioButton growing its box like Checkbox does in #5104? The Checkbox change here can go too, since #5104 covers it.

updated RadioButton to use 48x48dp layout box instead of hitSlop. also removed touchTarget.ts, its tests & Checkbox changes covered by #5104

@satya164

Copy link
Copy Markdown
Contributor

Review by Claude

The press and hover state layer covers the whole 48dp touch target. The MD3 radio state layer is 40dp, and the new 40dp stateLayer view in RadioButton.tsx paints nothing. Each screenshot shows the "Error (Checked)" radio on the Radio Button example screen.

iOS

Steps: open Radio Button, press and hold the "Error (Checked)" radio.
What happens: the highlight is a 48pt circle around the 20pt ring.
What should happen: a 40pt state layer, as the spec and Checkbox use.

iOS, pressed: 48pt highlight

(via Claude, verify if it makes sense)

Android

Steps: open Radio Button, press and hold the "Error (Checked)" radio.
What happens: the ripple is a 48dp circle (126px at 2.625x density).
What should happen: a 40dp ripple.

Android, pressed: 48dp ripple

(via Claude, verify if it makes sense)

Web

Steps: open /radio, hover the "Error (Checked)" radio.
What happens: the hover overlay is a 48px circle.
What should happen: a 40px state layer.

Web, hovered: 48px overlay

(via Claude, verify if it makes sense)

@satya164 satya164 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review by Claude

See the inline comments. (via Claude, verify if it makes sense)

Comment thread docs/6.x/docs/guides/migration.md Resolved
Comment thread docs/src/data/screenshots.ts Resolved
@MikitasK

MikitasK commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

Review by Claude

The press and hover state layer covers the whole 48dp touch target. The MD3 radio state layer is 40dp, and the new 40dp stateLayer view in RadioButton.tsx paints nothing. Each screenshot shows the "Error (Checked)" radio on the Radio Button example screen.

iOS

Steps: open Radio Button, press and hold the "Error (Checked)" radio. What happens: the highlight is a 48pt circle around the 20pt ring. What should happen: a 40pt state layer, as the spec and Checkbox use.

iOS, pressed: 48pt highlight

(via Claude, verify if it makes sense)

Android

Steps: open Radio Button, press and hold the "Error (Checked)" radio. What happens: the ripple is a 48dp circle (126px at 2.625x density). What should happen: a 40dp ripple.

Android, pressed: 48dp ripple

(via Claude, verify if it makes sense)

Web

Steps: open /radio, hover the "Error (Checked)" radio. What happens: the hover overlay is a 48px circle. What should happen: a 40px state layer.

Web, hovered: 48px overlay

(via Claude, verify if it makes sense)

good catch, thanks 🙏
fixed that ☑️

image image

@Doberjohn Doberjohn added this to the 6.0.0 milestone Oct 30, 2026
@Doberjohn

Copy link
Copy Markdown
Collaborator

This also fixes #4775 (the duplicate tab stop in RadioButton.Item), so could you add Fixes #4775 to the description? #5050 has the same fix and closes when this merges.

@MikitasK

MikitasK commented Nov 4, 2026

Copy link
Copy Markdown
Contributor

This also fixes #4775 (the duplicate tab stop in RadioButton.Item), so could you add Fixes #4775 to the description? #5050 has the same fix and closes when this merges.

nice finding 👍
the only thing is that I don't have permission to edit this PR's description since @burczu is the owner
@burczu when you'd have time, could you pls update PR description according to @Doberjohn comment 🙏

@Doberjohn Doberjohn modified the milestones: 6.0.0, 6.0.0-beta.0 Nov 12, 2026
@Doberjohn Doberjohn added the needs pickup Work that has been started but needs someone to pick it up and continue. label Nov 18, 2026
@Doberjohn Doberjohn removed the needs pickup Work that has been started but needs someone to pick it up and continue. label Nov 18, 2026
@jacekAtCK

Copy link
Copy Markdown
Collaborator

/review

@apex-sentinel-staging

Copy link
Copy Markdown

Apex Sentinel · ✅ Approve · review of e51f07f

3 finding(s): 3 minor.

🟡 Minor (3)

Where Finding
src/components/RadioButton/RadioButton.tsx:260 RadioButton no longer sets aria-live, so selection changes stop being announced
docs/component-docs.config.ts:8 screenshotsV6 deletes the RadioButton.Item screenshot from the v6 docs; its stated 5.x justification doesn't hold
docs/src/data/screenshots.ts:107 v5-only screenshots entries removed from the shared map used by the 5.x doc generator
Not in the reviewers' prompt (3 files)
  • src/components/__tests__/RadioButton/__snapshots__/RadioButton.test.tsx.snap: generated or a lockfile, so its lines were left out
  • src/components/__tests__/RadioButton/__snapshots__/RadioButtonGroup.test.tsx.snap: generated or a lockfile, so its lines were left out
  • src/components/__tests__/RadioButton/__snapshots__/RadioButtonItem.test.tsx.snap: generated or a lockfile, so its lines were left out

Reviewed with this repository's own Sentinel configuration (c8c3a3945ccb).

💬 Talking to Sentinel

In a finding's thread, reply with:

Command What it does
@apex-sentinel-staging note <context> Adds context; Sentinel re-checks the cited code
@apex-sentinel-staging pivot <why> Says the finding is wrong; Sentinel re-checks the cited code
@apex-sentinel-staging like Marks the finding as useful
@apex-sentinel-staging dislike <why> Marks it as not useful, so it is not raised again

On this conversation, comment @apex-sentinel-staging review to run a full review once again.

@apex-sentinel-staging apex-sentinel-staging Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Apex Sentinel: 3 new findings on e51f07f. The verdict and the full list are in the summary comment.

Comment on lines +260 to +270

const handlePressOut = React.useCallback(
(e: GestureResponderEvent) => {
setPressed(false);
onPressOut?.(e);
},
[onPressOut]
);

// When `accessible={false}` is passed (typically by `RadioButton.Item`,
// which owns the a11y tree for the wrapped row), suppress our own role and

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Minor · RadioButton no longer sets aria-live, so selection changes stop being announced

A screen reader user toggling a standalone RadioButton via an external control (pointerEvents="none") no longer hears the checked state change because accessibilityProps only emits role, aria-disabled and aria-checked—the aria-live="polite" the platform-specific predecessors set is gone. The v6 migration guide's RadioButton section does not mention this removal.

Suggested change

Restore aria-live="polite" on the standalone control (outside the accessible === false branch), or state in the RadioButton section of docs/6.x/docs/guides/migration.md that per-radio live-region announcements were removed.

Details

Also raised here

Also raised at this location by persona react-native-paper: RadioButton drops the aria-live announcement the platform variants had — RadioButtonAndroid/RadioButtonIOS both set aria-live="polite" on their touchable; the new single implementation's accessibilityProps (RadioButton.tsx 273-280) sets only role, aria-disabled and aria-checked, so a standalone radio that flips state via an external status prop is no longer announced. The modernized Checkbox in this checkout still emits 'aria-live': 'polite' as const for exactly that case (src/components/Checkbox/Checkbox.tsx 232), so add it for parity — or say so in the migration note, which currently doesn't mention the change.

Also raised at this location by persona senior-developer: Standalone RadioButton lost aria-live="polite"; screen readers no longer announce checked changes — A standalone <RadioButton> that a group or parent flips programmatically (e.g. status updated from a network load, or a RadioButton.Group value change) is no longer announced: both removed implementations set aria-live="polite" on their TouchableRipple (RadioButtonAndroid/RadioButtonIOS), and the new accessibilityProps block emits only role/aria-disabled/aria-checked. The component the PR says it mirrors, Checkbox, still ships 'aria-live': 'polite' in the same block (src/components/Checkbox/Checkbox.tsx:227), so this is a divergence from the stated model, not just a removal. The PR description scopes the live-region drop to "Item a11y", where the inner control is accessible={false} anyway, but it silently applies to the standalone radio too, and migration.md's RadioButton section doesn't mention it.

persona: maintainability, react-native-paper, senior-developer, javascript

Useful? Reply @apex-sentinel-staging like, or @apex-sentinel-staging dislike <why> if it is not.

Reply @apex-sentinel-staging note ... to add context, or @apex-sentinel-staging pivot ... if it is wrong — I will re-check the cited code.

Comment on lines +8 to +14
// 6.x-only overrides: the v5 iOS radio assets show a control this release
// removes, but `generate-5x-docs.ts` still renders them from the shared map.
const screenshotsV6: Record<string, unknown> = {
...screenshots,
'RadioButton.Group': 'screenshots/radio-button-group-android.gif',
};
delete screenshotsV6['RadioButton.Item'];

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Minor · screenshotsV6 deletes the RadioButton.Item screenshot from the v6 docs; its stated 5.x justification doesn't hold

Deleting screenshotsV6['RadioButton.Item'] removes the only entry that render.ts:130 looks up by doc.title, so the v6 RadioButton.Item page now renders no <ScreenshotTabs> at all. The comment's justification—that 5.x iOS radio assets are still rendered from the shared map—is incorrect because generate-5x-docs.ts builds its custom fields from the archived 5.x branch's own docs/docusaurus.config.js and docs/src/data/screenshots.js and never imports component-docs.config.ts. The RadioButton.Group override also replaces Android/iOS tab data with a single string.

⚠️ Check this patch before you commit it: the review doubted it would be right as written.

Suggested change
// 6.x-only overrides: the v5 iOS radio assets show a control this release
// removes, but `generate-5x-docs.ts` still renders them from the shared map.
const screenshotsV6: Record<string, unknown> = {
...screenshots,
'RadioButton.Group': 'screenshots/radio-button-group-android.gif',
};
delete screenshotsV6['RadioButton.Item'];
const screenshotsV6: Record<string, unknown> = {
...screenshots,
'RadioButton.Group': 'screenshots/radio-button-group-android.gif',
};
Details

Also raised here

Also raised at this location by persona react-native-paper: V6 RadioButton.Item doc page loses its screenshot, RadioButton keeps a v5 asset — docs/component-docs.config.ts deletes 'RadioButton.Item' from screenshotsV6, so the generated 6.x RadioButton.Item page renders no screenshot at all even though the component changed its row height (52→64dp) and a11y structure in this PR — the one place a reviewer would see the new row. Meanwhile the RadioButton entry still points at screenshots/radio-enabled.android.png / radio-disabled.android.png, captures of the 36dp control this PR replaced with the 48dp one. Ship refreshed v6 assets (or keep an explicit entry) for both pages instead of dropping one and reusing the other's stale image.

persona: senior-developer, react-native-paper

Useful? Reply @apex-sentinel-staging like, or @apex-sentinel-staging dislike <why> if it is not.

Reply @apex-sentinel-staging note ... to add context, or @apex-sentinel-staging pivot ... if it is wrong — I will re-check the cited code.

Comment on lines 107 to 112
Modal: 'screenshots/modal.gif',
ProgressBar: 'screenshots/progress-bar.png',
RadioButton: {
'Android (enabled)': 'screenshots/radio-enabled.android.png',
'Android (disabled)': 'screenshots/radio-disabled.android.png',
'iOS (enabled)': 'screenshots/radio-enabled.ios.png',
'iOS (disabled)': 'screenshots/radio-disabled.ios.png',
},
'RadioButton.Android': {
enabled: 'screenshots/radio-enabled.android.png',
disabled: 'screenshots/radio-disabled.android.png',
},

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Minor · v5-only screenshots entries removed from the shared map used by the 5.x doc generator

This PR deletes RadioButton.Android, RadioButton.IOS, RadioButton.Item-iOS, and RadioButton: Android/iOS (enabled|disabled) from docs/src/data/screenshots.ts, which is the shared map consumed by both the 6.x rspress config and the 5.x docs pipeline; the 5.x pages referencing those keys now render with missing images. The new screenshotsV6 + delete screenshotsV6['RadioButton.Item'] approach is exactly what the 6.x-only override exists to avoid — the deletions should be 6.x-only too.

Details

Also raised here

Also raised at this location by persona react-native-paper: Shared screenshot map loses the iOS radio assets the v5 docs still need — The v5 RadioButton documentation loses its iOS screenshots: docs/scripts/generate-5x-docs.ts builds its custom fields from the raw screenshots export (screenshots: screenshotsModule.screenshots, line 161), not from the new screenshotsV6 override, and this diff deleted RadioButton['iOS (enabled)'], RadioButton['iOS (disabled)'], 'RadioButton.Android' and 'RadioButton.IOS' entries from that shared export. The comment above screenshotsV6 in docs/component-docs.config.ts states the intent is the opposite — that generate-5x-docs.ts should keep rendering the v5 iOS assets from the shared map. Keeping the removed keys in src/data/screenshots.ts and deleting them only in screenshotsV6 achieves that; as written the v5 5.x pages that still document RadioButton.IOS render without a screenshot.

persona: javascript, react-native-paper

Useful? Reply @apex-sentinel-staging like, or @apex-sentinel-staging dislike <why> if it is not.

Reply @apex-sentinel-staging note ... to add context, or @apex-sentinel-staging pivot ... if it is wrong — I will re-check the cited code.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

refactor(radio-button): modernize selection model and improve MD3 compliance

7 participants