fix: re-implement #3856 to improve correctness #3865
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
In #3856, I attempted to improve the correctness of
role="separator"
inuseAriaPropsForRole
, but @Conaclos pointed out that removing thePROPS
that I did may not be a great way to go about it. Instead, this PR is flipping the boolean on those props to make them not required. I'm having trouble understanding the macro code (I've admittedly never read a macro's code) to see if this is the case. Tests are passing here, so it seems this is right, but appreciate your guidance. 🙏@ematipico also pointed out that the most correct way to go about this would be to conditionalize the required-ness based on if the element is focusable. This was something I considered but didn't know how to go about. I'd be happy to attempt this but I might need some help or a pointer to a rule where a similar behavior is implemented to figure it out. Or, perhaps, is there a method somewhere to infer focusable-ness?
Test Plan
Test cases in
valid.jsx
andinvalid.jsx
.