Closed mirka closed 1 day ago
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: tyxla <tyxla@git.wordpress.org>
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.
Size Change: +33 B (0%)
Total Size: 1.81 MB
Filename | Size | Change |
---|---|---|
build/components/index.min.js |
227 kB | +31 B (+0.01%) |
build/editor/index.min.js |
106 kB | +2 B (0%) |
Flaky tests detected in 2124cd42e902a05fec057c6df8dc4dbcc6aa7dda. Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.
đ Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/11579855301 đ Reported issues:
/test/e2e/specs/editor/various/taxonomies.spec.js
Part of #65751
What?
Deprecate the 36px default size on
Radio
, which is a subcomponent of the deprecatedRadioGroup
component.Why?
Technically we could do this without a formal deprecation, since RadioGroup is already deprecated. But due to one remaining usage in the app (#66569), we haven't been able to log a deprecation warning for the component yet, meaning that many existing consumers may not even know this component is deprecated.
Given the circumstances, I think it's reasonable for the size change to have an opt-in grace period like the other components.
Testing Instructions
See Storybook for
RadioGroup
.