Test/konami easter egg mouse interactivity - #7354
Closed
adityapandey4621 wants to merge 2 commits into
Closed
Conversation
Contributor
|
👋 Hey @adityapandey4621! Thanks for your interest in contributing to CommitPulse! 🙏 Unfortunately, this PR has been automatically closed because you are not assigned to the linked issue #7015 — test(KonamiEasterEgg-mouse-interactivity): verify Interactive Tooltips, Cursor Hovers & Touch Event Propagation (Variation 5). To avoid this in the future, please follow these steps:
We look forward to your contribution once you're assigned! 🚀 |
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.
Description
Fixes #7015
I've added the new isolated testing file
components/KonamiEasterEgg.mouse-interactivity.test.tsxto handle the Interactive Tooltips, Cursor Hovers & Touch Event Propagation scenarios for theKonamiEasterEggcomponent.Here's exactly what I did:
mouseenter/hoverevents to guarantee that bringing the mouse over the overlay doesn't accidentally trigger unwanted side-effects or crashes.pointer-events-noneproperly.pointer-events-nonelayer into the background naturally, rather than being eaten by the overlay.cursor-pointer).mouseleaveevents and used fake timers to prove that the overlay only disappears strictly based on the configured timeout, not prematurely from mouse movements.Pillar
Visual Preview
(N/A — This is a frontend testing infrastructure PR)
Checklist before requesting a review:
CONTRIBUTING.mdfile.localhost:3000/api/streak?user=YOUR_USERNAME).npm run formatandnpm run lintlocally and resolved all errors (CI will fail otherwise).feat(themes): ...,fix(calculate): ...).README.mdif I added a new theme or URL parameter.