feat: fix LogOut modal position, and enhance its opening/closing logic #54
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ing logic to avoid manipulating DOM elements directly
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Related issues
Closes #18
Description
focus-trap-reactpackageLogOutmodal contents withFocusTrapto prevent users from focusing, interacting with, or tabbing to other elements outside of theLogOutmodalposition: fixedCSS rule tologOutso that it does not move when the user scrolls the pageLogOutmodal, so that we do not need to modify DOM elements directly, nor theirdisplayoropacityrules. It now works with a simple boolean statebackgroundwrapper withinLogOut, to give "opacity" to elements below the modallog-out-component.mov