-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Font Library: buttons position and accessibility #58212
Conversation
Size Change: +16 B (0%) Total Size: 1.69 MB
ℹ️ View Unchanged
|
Flaky tests detected in 18dc984. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/7643044230
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks as described, and the Delete color and button spacing values are consistent with similar items elsewhere in the site editor. Nice improvement!
<CheckboxControl | ||
checked={ selected } | ||
onChange={ handleToggleActivation } | ||
__nextHasNoMarginBottom={ true } | ||
id={ checkboxId } | ||
label={ false } | ||
/> | ||
<FontFaceDemo fontFace={ face } text={ displayName } /> | ||
</Flex> | ||
</label> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unrelated to this PR: it's not okay to associate labels and form controls with both a for
attribute and by wrapping the form control within the label element. I do realize the intent is to make the whole row clickable but this is not okay.
I'm surprised the component allows to set the label prop to false
.
Also, we do have reusable components for good reasons. One of them is to make sure they're properly labeled. Hardcoding a <label>
element around the checkbox component that is supposed to internally handle its label defeats the purpose of having reusable components.
Thanks for working on this. I noticed an unrelated problem but I'll open a separate issue. |
What?
Why?
See #58083 for reference.
Testing Instructions
Screenshots:
Fixes: #58083