Alex Rudenko
Alex Rudenko
@gsnedders I intended to add userAgent as an output capability only as described [by this definition](https://w3c.github.io/webdriver/#dfn-matched-capability-serialization-algorithm)("provide any computed value to return to the user") so it should not be interpreted...
So I believe the following in the request ``` { "capabilities": { "alwaysMatch": { "userAgent": "This/1.0 Is/2.0 Not/3.0 (A User-Agent String" } } } ``` would result in a failure...
Updated the PR to handle userAgent when matching capabilities.
@Lightning00Blade can this be landed?
ah waiting for m125
@sadym-chromium looks like chromium-bidi needs to be updated to ignore the certificate errors on the browser target similar to how Puppeteer and Firefox does so that service workers are also...
Blocked by https://github.com/GoogleChromeLabs/chromium-bidi/issues/2357
Will be fixed via https://github.com/puppeteer/puppeteer/pull/12500 the example actually runs for me as is (without enter as there are inline search results showing I believe)
M126 is available with Puppeteer 22.11.0 and this feature is now supported (I will update the docs in another PR).