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
Fire mouseenter and mouseleave events #27413
Conversation
Heads up! This PR modifies the following files:
|
da48ee5
to
d26b9a5
Compare
r? @nox |
cb849aa
to
962e620
Compare
The code looks correct but this will probably need changes to the test expectations. @bors-servo try=wpt |
Fire mouseenter and mouseleave events The PR primarily consists of changes for: - Fixing the order in which `mousemove` events are fired. - Firing `mouseenter` and `mouseleave` events. --- - [x] `./mach build -d` does not report any errors - [x] `./mach test-tidy` does not report any errors - [x] These changes fix #26958 - [ ] There are tests for these changes
☀️ Test successful - status-taskcluster |
Aha, we didn't enable
You can add it after this stuff to keep things alphabetical:
|
I think pointerevents is unrelated to mouse events? |
I have included some manual tests I'd used to verify mouse events' order. |
I've checked locally and everything looks good now AFAICT. @bors-servo r+ |
📌 Commit de20715 has been approved by |
☀️ Test successful - status-taskcluster |
The PR primarily consists of changes for:
mousemove
events are fired.mouseenter
andmouseleave
events../mach build -d
does not report any errors./mach test-tidy
does not report any errors