fix(useFocusWithin): correctly track the state when switching the focus of elements in the same container #4394
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.
Before submitting the PR, please make sure you do the following
fixes #123).Description
closes #4372 . When you switch the focus state of two descendant elements of the same container, the focus state of the container element will briefly turn into
false, however thefocus-withinpseudo-element behavior will not be like this.I used the element.prototype.matches during the
focusoutevent, sothat it will act like:focus-withinin this situationAdditional context