Bug 305856

Summary: REGRESSION (iOS 26.2?): pointerenter fires incorrectly after removing overlapping element
Product: WebKit Reporter: bitbof
Component: UI EventsAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: thorton, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: Safari 26   
Hardware: iPhone / iPad   
OS: iOS 26   
Attachments:
Description Flags
How this bug affects Kleki.com version 0.9.10.4 none

bitbof
Reported 2026-01-20 10:54:26 PST
Created attachment 478079 [details] How this bug affects Kleki.com version 0.9.10.4 This happens on the latest iPadOS and iOS version (26.2) in Safari. It did not occur before. Steps: - Demonstration page: https://bitbof.github.io/browser-bug-demos/2026-01-20-safari-pointer-leave/ - Have an element that sits on top of another element which has a pointerenter/pointerleave listener via JS - Make the top element disappear on click (tap) - Tap on the top element Expected: - The last event firing for the lower element will be pointerleave Actual: - The last event firing for the lower element is pointerenter This can break JS-based hover logic in certain cases. E.g. for my web app Kleki.com (version 0.9.10.4) a menu that closes on click now only triggers a pointerenter event for an unrelated element, resulting in a stuck state. Illustration attached.
Attachments
How this bug affects Kleki.com version 0.9.10.4 (58.20 KB, image/png)
2026-01-20 10:54 PST, bitbof 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
bitbof
Comment 1 2026-01-20 11:06:15 PST
Now that I think about it, the lower element should not even receive the pointerenter event.
Radar WebKit Bug Importer
Comment 2 2026-01-21 18:02:32 PST
<rdar://problem/168632829>
Tim Horton
Comment 3 2026-01-22 10:46:01 PST
*** This bug has been marked as a duplicate of bug 304955 ***
Note You need to log in before you can comment on or make changes to this bug.