Add and remove classes to fix dropdown positioning issues #304
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
cirdes
approved these changes
Jun 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
In our project, we encountered some positioning issues when using other components inside the dropdown.
We rendered a button with a tooltip inside a dropdown item, but the tooltip wasn't displayed correctly:
To fix this, we removed the
overflow-hiddenclass from the dropdown. After that, the tooltip displayed as expected:In another case, a Skeleton component was appearing on top of the dropdown. After some investigation, we discovered that the z-index class needed to be applied directly to the root element of the dropdown to ensure proper stacking.