Bug 237950 – [Model] A long press on a <model> infinitely corrupts the touch events sent to its WKModelView

• Status: NEW
• Component: WebXR

[Thomas Kumlehn]

After a first long tap/press on a <model> any future single finger drag is interpreted as a two finger event.
So a simple rotate gesture becomes a zoom/dolly.
The next long press totally halts interactions with the modelElement, probably because it's interpreted as a 3-finger gesture.

[Thomas Kumlehn]

The first long tap selected the word preceding the model tag.

[Radar WebKit Bug Importer]

<rdar://problem/90364936>

[Antoine Quint]

Thanks for filing this Thomas. Which iOS version is that?

[Thomas Kumlehn]

iPadOS 15.4

[Thomas Kumlehn]

but it happened before and was reported in Feedback.app as part of other <model> related problems for iOS15.3

[Antoine Quint]

Would you have the id for the issue as reported through the Feedback app?

[Thomas Kumlehn]

It was mixed in with a macOS related bug reported as FB9822366, that was already fixed.
I should have investigated further and should have reported those separately.

[Thomas Kumlehn]

Someone did a really bad job in following the steps that cause the problem, I also reported specifically for iPadOS as FB9951062, so I made a screen recording showing the problem.

The newly attached screen recording shows how I use two fingers to dolly close to the asset, then do a single finger long press. All following interactions are single touch only, but behave unexpected and totally different to a similar session without long press.

I very much hope <model> can be introduced this year, so please let more qualified/motivated developers work on the fixes. Would be very embarrassing otherwise if this (IMHO) blocking bug stays.

[Thomas Kumlehn]

I updated to iPadOS 15.5 public beta 2 and now the same problem occurs when opening the USDZ as a stand alone model document.
The long press shows a kind of capsule shaped loop instead of selecting nearby text, but it also jeopardises the touch events the same way.
A single touch event is interpreted as a multi touch.
Every long press adds another finger not being lifted.

[Antoine Quint]

That behavior is consistent since loading the USDZ file as a standalone document yields a <model> element.

[Thomas Kumlehn]

Problem persists with iPadOS 15.5 RC

[Thomas Kumlehn]

Bug persists in iPadOS 15.6 (19G5027e)

[Thomas Kumlehn]

persists in iPadOS16beta

[Thomas Kumlehn]

Besides of a long press, also one of more other events seem to bring the tap events out of synch. I tested avoiding a long press and it still happened - don't know what kind of finger event it was.

[Thomas Kumlehn]

Problem not solved with iPadOS 16.0 beta2 (20A5303i)

[Thomas Kumlehn]

Same problem on iPadOS 16 beta 3 (20A5312g)

[Thomas Kumlehn]

Bug still not fixed in iPadOS 16 beta (20A5312j)

[Thomas Kumlehn]

bug persists on iPadOS16 (20A5328h)

[Thomas Kumlehn]

bug persists on iPadOS16 (20A5339d)

[Thomas Kumlehn]

Not fixed in iPadOS 16.0 (20A5349b)

[Dean Jackson]

You'll see here when it is fixed :)

[Thomas Kumlehn]

iPadOS 16.2 (20C65) brought the following tiny change:
A long tap does NOT select a word in a neighbour <span> any longer, but it still permanently disrupts the communication of touch events to the ARQL / USD process.

[Thomas Kumlehn]

With iPadOS 16.4 dev beta (20E5212f) the long press again selects a preceding text span, but now the whole communication seem to crash the connection to the native process.

The WKModelView stays frozen.

[Thomas Kumlehn]

Looks like the bug has not been fixed and will cause embarrassment when <model> comes out of experimental on iOS and iPadOS