Skip to content
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

[MouseEvent algorithms] Boundary event dispatch needs to be tied to native down and up events #383

Open
mustaqahmed opened this issue Sep 17, 2024 · 1 comment

Comments

@mustaqahmed
Copy link
Member

mustaqahmed commented Sep 17, 2024

Mouse boundary event (mouseenter/leave/over/out) dispatch is currently tracked using the state variable last_mouse_element. The variable is checked and updated only in Section 3.4.3.15. handle native mouse move.

Native mousedown and mouseup events should check and update the variable too: a mousedown always follows a mouseenter and mouseover to the same target in all major browsers.

Possible solution

Rewrite Section 3.4.4. Mouse Event Order into a method named updateElementUnderMouse which will check and update the variable and fire all required boundary events. Call this from native mouse event handlers.

@mustaqahmed
Copy link
Member Author

FYI: @garykac @flackr @smaug----

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant