"Serialize the user prompt handler" algorithm should probably have a special case for WebDriverBiDi-only session #1834
Labels
Content-Length: 196165 | pFad | http://github.com/w3c/webdriver/issues/1834
6CFetched URL: http://github.com/w3c/webdriver/issues/1834
Alternative Proxies:
At the moment, running "serialize the user prompt handler" algorithm in case of BiDi when a client didn't specify
unhandledPromptBehavior
capability will resolve todismiss 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.The text was updated successfully, but these errors were encountered: