[UI] fix: prevent play with logs popup from closing when moving mouse to it#5589
Open
Vidi0 wants to merge 1 commit into
Open
[UI] fix: prevent play with logs popup from closing when moving mouse to it#5589Vidi0 wants to merge 1 commit into
Vidi0 wants to merge 1 commit into
Conversation
Contributor
Author
|
It seems like the failed tests are unrelated to the changes in this PR |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When hovering over the small arrow next to the play button, the play with logs button appears. However, there is a small gap between the arrow and the play with logs button. Therefore, when moving the mouse slow enough towards it, it closes.
Fix the bug by adding a transparent css object that appears when the arrow is hovered over and fills the gap between the arrow and the play with logs button.
alt-play-bug.mp4
alt-play-fix.mp4
Warning: AI was used to help me write this PR. I decided to keep the AI-generated comments because it isn't obvious why the css object is needed, but feel free to ask for removal.
Use the following Checklist if you have changed something on the Backend or Frontend: