-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
deps(puppeteer): upgrade to 16.1.0 #14244
Conversation
Bumping to 16: https://github.com/puppeteer/puppeteer/releases/tag/v16.0.0 This is the release with changes to how puppeteer handles iframes, so I am going to run our DT / FR tests a few times to see if any flakiness reeappers. |
@@ -216,7 +216,7 @@ describe('Lighthouse Viewer', () => { | |||
document.querySelector('.lh-tools__dropdown')).visibility === 'visible'; | |||
}); | |||
|
|||
// For some reason, clicking this button doesn't always initiate the download after upgrading to Puppeteer 15.2.0. | |||
// For some reason, clicking this button doesn't always initiate the download after upgrading to Puppeteer 16. |
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.
why update this line? presumably the version it broke in is useful information.
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.
I didn't do a bisect to find the revision that broke it, this is just calling out the version upgrade that introduced the problem for us.
Split of from #13901
At some point along the way, pptr added a
package.json
for the esm modules. This would be nice to have if we want to use the esm versions of the modules.This also fixes some outdated chrome issues with #14146