Do we know why this is happening? Are we not receiving touch down / touch up events if the upper android layer detects a click?

Do we know why this is happening? Are we not receiving touch down / touch up events if the upper android layer detects a click?

At least in the emulator this is expressed as a "click" method call on the view, I think.

Ah, sorry. The ServoView which extends SurfaceView exposes a click method in the API as well using it to handle onSingleTapUp. Probably these tap events should be interpreted properly, but that seems like a larger change.

Seems fine to me to fix the regression, although I do wonder if this should make us re-evaluate the decision to completely remove the click event.

"click" is an internal DOM concept that should probably not be exposed to the API probably. They are produced by platform APIs so every embedder had to implement them, which could well mean that simple mistakes in the embedder could lead to non-conformant behavior according to the specification.

I think probably what we want to do is to remove the "click" event from the ServoView API entirely.

Ah, so the click() method in SevoView is an implementation detail, and not something we need to implement on Android? Then, yeah - we should probably remove it and wire up the up / down events to touch up / touch down.