Scrolling with Mouse Wheel Without Moving Mouse Never Triggers :hover styles or MouseOver/MouseOut Events Even Though Pointer Is Over Different Elements

Issue #7970659 • Assigned to Bogdan B.

Details

Author
Bryan C.
Created
Jun 23, 2016
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
14.14371
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

Scrolling with Mouse Wheel Without Moving Mouse Never Triggers :hover styles or MouseOver/MouseOut Events Even Though Pointer Is Over Different Elements.

  1. Open Any Web Page with a :hover effect on some of the elements.
  2. Point your mouse at one of the elements to trigger the :hover style change.
  3. Scroll the mouse wheel without moving the mouse

You would expect the :hover style to be disabled once the mouse is no longer over the element, but it doesn’t. I get that this can slow down scrolling to do it with every pixel change, but there should at least be an interval where it’s updated… or at the very worst, it should update when scrolling stops. Currently it never updates. Ineterestingly, the mouse cursor does update after scrolling stops to the pointer hand or the default arrow (depending on if your mouse is over a link or not when you stop scrolling). However CSS :hover changes don’t fire until the mouse is actually moved.

Attachments

0 attachments

    Comments and activity

    • Ideally the mouse move event would fire when scrolling with a mouse wheel to reflect the new x/y coordinates of the mouse relative to the document, and all CSS/javascript event handlers would update accordingly.

    • So apparently there’s a bug in the comments on this issues site where hitting “add comment” submits twice.

    • Microsoft Edge Team

      Changed Assigned To to “Ibrahim O.”

      Changed Assigned To to “Travis L.”

      Changed Assigned To to “Rico M.”

      Changed Assigned To to “Bogdan B.”

    • This is still a problem in build 14388. Pretty obvious on sites with big mouse-over hit zones, like the homepage of www.wonderhowto.com

    • Still broken in 14393

    • Still a problem in 14393.51

    • Still a problem in 14393.82

    • Still a problem in 14393.187. Chrome and Firefox do not have this problem.

    • Still a problem in 14971.

    • Still a problem in 14986. Do the Edge PMs even care about all these bugs? Or only new features? I’m honestly getting ready to give up on this browser. Had such high hopes, too.

    You need to sign in to your Microsoft account to add a comment.

    Sign in