Sync vendored puppeteer to v17.1.2
Categories
(Remote Protocol :: CDP, task, P1)
Tracking
(firefox108 fixed)
| Tracking | Status | |
|---|---|---|
| firefox108 | --- | fixed |
People
(Reporter: whimboo, Assigned: Sasha)
References
Details
(Whiteboard: [webdriver:m5])
Attachments
(2 files)
Version 18.0.3 is the most recent release:
https://github.com/puppeteer/puppeteer/releases/tag/v18.0.3
Very important are the testrunner changes which now include a custom expectation file to more easily set test expectations. This already landed for the 17.1.3 release.
https://github.com/puppeteer/puppeteer/commit/d8830cbc55a07fb0cd7d3ac98d9af4e6d95b179b
That means for us that we probably do no longer have to maintain our own expectation file but could hopefully re-use what's coming from Puppeteer directly.
If that's the case we should also update https://puppeteer.github.io/ispuppeteerfirefoxready/ to use the Puppeteer's own expectation file. I filed the following issue for such a change already:
https://github.com/puppeteer/ispuppeteerfirefoxready/issues/13
Updated•3 years ago
|
Updated•3 years ago
|
| Reporter | ||
Updated•3 years ago
|
| Assignee | ||
Updated•3 years ago
|
| Assignee | ||
Comment 1•3 years ago
|
||
Right now, expectation file from Puppeteer repo doesn't fulfill our requirements since it skips most of the tests which don't pass in Firefox, and we would like to have "fail", "timeout" or "fail, pass" expectations where it's possible. I've opened an issue in Puppeteer repo to see if it's possible to address it in puppeteer repo: https://github.com/puppeteer/puppeteer/issues/9118.
| Assignee | ||
Comment 2•3 years ago
|
||
| Assignee | ||
Comment 3•3 years ago
|
||
Updated•3 years ago
|
| Assignee | ||
Updated•3 years ago
|
| Assignee | ||
Updated•3 years ago
|
| Assignee | ||
Updated•3 years ago
|
Comment 5•3 years ago
|
||
| bugherder | ||
Description
•