Home Dashboard Directory Help

PointerEnter and PointerLeave stop firing for mouse after subtree under cursor is removed from the DOM by Brandon Paddock


Status: 

Closed
 as Fixed Help for as Fixed


Type: Bug
ID: 1853548
Opened: 9/30/2015 12:19:09 PM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

Removing an element subtree from the DOM while the mouse cursor is over said subtree causes Edge (and WWAHost for Win10 apps, where I first encountered this) to no longer fire PointerEnter and PointerLeave events to *any* elements until the mouse cursor leaves the window. Note this does not seem to repro if a single element (with no sub elements) under the cursor is removed.

In my testing this is observed on my Surface Pro 3 with Win10 Insider Preview 10547, but not on a desktop (non-touch) PC running 10240 (publicly released build) so seems to be a somewhat recent regression, or possibly only repros on touch machines or something like that.
Details
Sign in to post a comment.
Posted by Microsoft on 12/9/2015 at 11:50 AM
Hello Brandon Paddock,

This issue appears to be no longer repro in TH2 November Update (10586)

Best regards,
The MS Edge Team
Posted by Brandon Paddock on 10/6/2015 at 3:04 AM
FYI, this bug also affects mouseenter/mouseleave events, which also go missing. I've made several attempts at a workaround but haven't come up with one yet. I do hope this gets fixed soon as it really breaks my app.
Posted by Microsoft on 9/30/2015 at 1:27 PM
Hello Brandon Paddock,

Thank you for your feedback. We will be investigating this issue further.

Best regards,
The Microsoft Edge Team
Sign in to post a workaround.