[Webkit-unassigned] [Bug 210716] pointermove event sometimes has incorrect pointerType of 'mouse' on touch interactions

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Apr 21 04:21:31 PDT 2020


https://bugs.webkit.org/show_bug.cgi?id=210716

--- Comment #4 from ae at seven.systems ---
(In reply to Tim Horton from comment #2)
> Is this a change from a prior version of iOS? What version are you seeing
> this on?
> 
> We are tracking one regression in this area (rdar://problem/60422815) caused
> by r251320, but that would be a behavior change in iOS 13.4

Sorry, I can't tell if it's a change -- the version I'm testing it on is 13.4.

Maybe a little background: We've developed a large WKWebView-based hybrid app that is a few years old and still based exclusively on touch events (touchstart, touchmove etc.).

When iOS 13.4 was introduced with "proper" mouse support, users started complaining about the mouse not doing anything, so we added a "mouse emulation layer" that generates synthetic touch events for received mouse events.

However, we want to avoid launching that layer unless the user actually uses a mouse, because it obviously is a huge hack and introduces overhead.

It seems to be very hard to properly detect if there is an actual mouse connected. We've tried various means, but the "PointerEvent.pointerType" route seemed the best and most logical, until we discovered that it is not reliable.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20200421/51d89534/attachment.htm>


More information about the webkit-unassigned mailing list