[Bug]: Synthesizing double or triple click events via "input.performActions" doesn't work with WebDriver BiDi
Maintainers usually reply within 1 day
Nobody has claimed this yet.
- #42058 by @krishpranav — closed without merging
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 57/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- testing-qa
Research direction
Start by running the should dblclick the div test in tests/page/page-mouse.spec.ts at the referenced location. Trace how input.performActions builds the separate mouse action chains under WebDriver BiDi, using the linked WebDriver discussion for context. Done means the test passes and produces a double-click event rather than two independent click events.
Written by the indexing model from the issue text.
Description
Version
latest
Steps to reproduce
Run the should dblclick the div test in page-mouse.spec.ts:
Expected behavior
The test should pass with a double click event generated.
Actual behavior
The test fails because two independent click events are emitted by the browser only.
This happens because the multiple mouse down and up actions are part of different action chains. But with WebDriver BiDi to get double clicks those actions need to be part of the same action chain. See the discussion at:
https://github.com/w3c/webdriver/issues/1772#issuecomment-2801439996
Additional context
No response
Environment
As used in GitHub actions.
CC @hbenl
- Dominant language
- TypeScript
- Stars
- 100k
- Forks
- 6.9k
- Avg merge
- 16h 8m
- Merged PRs (30d)
- 281
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/playwright
-
[MCP]: page snapshots in .playwright-mcp/ are not git-ignored (.playwright-cli/ is, since #42318)Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
microsoft/playwright#44289 ·
Maintainers usually reply within 1 day
-
agent-triage-done
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
microsoft/playwright#44264 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 12/100
microsoft/playwright#44290 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 22/100
microsoft/playwright#44288 ·
Maintainers usually reply within 1 day
-
[Bug]: page.goto never returns for a load started as a newer service worker takes over (Chromium)Open
Difficulty 5/5 Over a week Newbie friendliness 12/100
microsoft/playwright#44287 ·
Maintainers usually reply within 1 day
All issues in microsoft/playwright
Similar issues
-
clawsweeper:needs-maintainer-review clawsweeper:needs-product-decision clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster P3
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
openclaw/openclaw#203385 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nwverse/persona#12800 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 Half a day Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
WISE-Community/WISE-Client#2404 ·
Maintainers usually reply within 1 day