New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: close WebDriver BiDi session on disconnect #11470
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have not you said it's a non-breaking change?
Technically it is not breaking, as behavior has not changed and it should not change any existing workflows, but the API has changed. |
I can switch description to non-breaking, WDYT? |
b54333f
to
78db994
Compare
Converting to draft, as some tests are failing |
There are two concerns: 1) every breaking change results in a major puppeteer version which we don't want to bump so often 2) at the same time it does not look like it deserves a major version since there is no breaking behavior. |
Let's go with |
`browser.disconnect` returns `Promise<void>` instead of `void`. This is required ti be able to properly close BiDi session before disconnecting.
This reverts commit b54333f.
This reverts commit a7b3995db4c3f7d973be024eb6799d276944008f.
c356d29
to
abd7b87
Compare
browser.disconnect
returnsPromise<void>
instead ofvoid
. This is required to be able to properly close BiDi session before disconnecting.browser.disconnect
sendssession.end
before disconnecting.Preparation for supporting
puppeteer.connect
by Firefox.