-
Notifications
You must be signed in to change notification settings - Fork 894
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
Fix tab focus for ai optimize toast element #21635
base: trunk
Are you sure you want to change the base?
Conversation
#4372 Wrap close button with ForwardRef to be able to use with useRef.
…ocus-for-ai-optimize-toast-element
…ocus-for-ai-optimize-toast-element
… to the AIAssessmentFixesButton
updates Toast component to accept additional props
@Jordi-PV Please be aware that following packages have been abandoned and are not actively maintained anymore:
Please consider using the other packages instead. |
Pull Request Test Coverage Report for Build 26bee99b9f7b80ebab79aed0993ba90c6eb24a4bWarning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
…-optimize-toast-element
|
||
Toast.propTypes = { | ||
children: PropTypes.node, | ||
id: PropTypes.string.isRequired, | ||
role: PropTypes.string.isRequired, |
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.
Does this really need to be a required prop breaking API change?
You can already add it via the prop spread now. So you're saying noone may use a Tooltip without specifying a role
.
IMO this seems a bit overzealous for the purpose of an element
in our UI library.
Context
Summary
This PR can be summarized in the following changelog entry:
Relevant technical choices:
Test instructions
Test instructions for the acceptance test before the PR gets merged
This PR can be acceptance tested by following these steps:
Relevant test scenarios
Test instructions for QA when the code is in the RC
QA can test this PR by following these steps:
Impact check
This PR affects the following parts of the plugin, which may require extra testing:
UI changes
Other environments
[shopify-seo]
, added test instructions for Shopify and attached theShopify
label to this PR.Documentation
Quality assurance
Innovation
innovation
label.Fixes #