Skip to content

Make the tap() method issue the full event sequence for a physical tap - #51

Merged
hovinen merged 2 commits into
sync-with-blitzfrom
fix-tap-event
Nov 14, 2026
Merged

hovinen merged 2 commits into
sync-with-blitzfrom
fix-tap-event

Conversation

@hovinen

@hovinen hovinen commented Nov 14, 2026

Copy link
Copy Markdown
Collaborator

Previously, tap() was just a synonym for click(), which would only dispatch the literal click event. There was no way to cause the dispatch of pointerdown and pointerup, much less the full sequence of events associated with a physical click or tap.

This changes tap() to cause the full sequence of events to be dispatched. It is no longer a synonym of click(). The documentation now reflects that, and new doctests are included.

@hovinen
hovinen added this pull request to stack #50 November 14, 2026 14:49
Previously, `tap()` was just a synonym for `click()`, which would only
dispatch the literal `click` event. There was no way to cause the
dispatch of `pointerdown` and `pointerup`, much less the full sequence
of events associated with a physical click or tap.

This changes `tap()` to cause the full sequence of events to be
dispatched. It is no longer a synonym of `click()`. The documentation now
reflects that, and new doctests are included.
@hovinen
hovinen merged commit 32f848e into main Nov 14, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant