Refactor font variant components to use useId for checkbox IDs#69050
Refactor font variant components to use useId for checkbox IDs#69050
Conversation
|
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 If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
|
Thanks for the PR! The whole code looks good. @Mamaduka In this PR, do you know whether |
|
Size Change: -16 B (0%) Total Size: 1.84 MB
ℹ️ View Unchanged
|
|
The |
…ress#69050) Co-authored-by: torounit <[email protected]> Co-authored-by: Mamaduka <[email protected]> Co-authored-by: t-hamano <[email protected]> Co-authored-by: chiilog <[email protected]>
…ress#69050) Co-authored-by: torounit <[email protected]> Co-authored-by: Mamaduka <[email protected]> Co-authored-by: t-hamano <[email protected]> Co-authored-by: chiilog <[email protected]>
What?
Closes #68934
Why?
id contains font variants, but they are translated And because kebabCase is applied to the string, the translated string is lost, resulting in an invalid id in cases such as Japanese.
This problem can be solved by changing the id to be generated with useId.
Testing Instructions
Testing Instructions for Keyboard
Screenshots or screencast