-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
URLInput: Fix incorrect classname for suggestions #66714
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. |
Size Change: +3 B (0%) Total Size: 1.82 MB
ℹ️ View Unchanged
|
Flaky tests detected in 7d595d4. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/11664485377
|
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.
Good catch, @t-hamano!
Thanks for the review! |
What?
Fixes the invalid 'undefined__suggestions' CSS class that was generated when no
className
prop was passed to theURLInput
component.Why?
We need to check if the class name exists.
Testing Instructions
It's a little difficult to test the
URLInput
component directly, so please test it with theImageURLInputUI
component, which uses it internally.undefined__suggestions
does not exist.Additionally, make the following changes and test that the class name is applied as before.
If you perform the same operation, the suggestion should have the CSS class
test__suggestions
applied.