"Serialize the user prompt handler" algorithm should probably have a special case for WebDriverBiDi-only session
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 718
- Forks
- 228
- PR merge metrics
- No merged PRs in 30d
Description
At the moment, running "serialize the user prompt handler" algorithm in case of BiDi when a client didn't specify unhandledPromptBehavior capability will resolve to dismiss and notify value which is not compatible with BiDi response for "session.new" command. So we probably should have a special case here if BiDi-only session was started.
Contributor 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.
Research direction
Start with the WebDriver specification's "serialize the user prompt handler" algorithm and compare its default with the WebDriver BiDi "session.new" command requirements. Determine how a BiDi-only session is identified and what compatible result the special case must define. Done means the specification resolves this scenario consistently and includes coverage or an example for the default capability case.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100