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.
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
feat(react): remove focus-trap-react replacing with internally managed focus traps #1730
feat(react): remove focus-trap-react replacing with internally managed focus traps #1730
Changes from all commits
436c710
cfe2fd2
eb2beac
272a90a
2e1acbb
615b907
bf17a62
d5287d6
f52ebee
f794091
afa2bf9
51c9362
aeaba08
aac9243
771ea32
9c50da6
e15d27a
e7acc2c
72d7098
d72e20a
71cf0f3
960a7fc
9ba44b0
2892de7
75db09a
82421c5
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
nit - this use of
setTimeout
could probably benefit from a comment (I assume this is to wait for the dialog to be rendered, if so there may be a way to avoid setTimeout use)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.
I agree, but I wish I remembered why as it's been like this since it's initial implementation:
cauldron/packages/react/src/components/Dialog/index.tsx
Lines 65 to 66 in eb5def1
I'm taking an educated guess that it's queuing the focus to be on the next tick to prevent focus conflicts. We can add that as a comment if you feel that's useful?