Sync vendored puppeteer to v8.0.0
Categories
(Remote Protocol :: Agent, task, P2)
Tracking
(firefox88 fixed)
Tracking | Status | |
---|---|---|
firefox88 | --- | fixed |
People
(Reporter: whimboo, Assigned: jdescottes)
Details
(Whiteboard: [bidi-m1-mvp])
Attachments
(3 files)
Version 7.1.0 is the most recent release:
https://github.com/puppeteer/puppeteer/releases/tag/v7.1.0
Even Puppeteer doesn't contain BiDi code yet, we should keep up-to-date. As longer as we are waiting with a sync, as more complex it will be.
Reporter | ||
Comment 1•3 years ago
|
||
A new major release of Puppeteer just appeared:
https://github.com/puppeteer/puppeteer/releases/tag/v8.0.0
Reporter | ||
Updated•3 years ago
|
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 2•3 years ago
|
||
Slightly blocked on try job outage right now, but a quick summary:
- there is no upstream sync needed, all the changes from
hg diff remote/test/puppeteer -r c97179fc8830
were already synced back to the puppeteer repository (https://github.com/puppeteer/puppeteer/pull/6690 & https://github.com/puppeteer/puppeteer/pull/6868) - there are new failures for existing cookies tests, because puppeteer starts testing non standard properties, not supported in Firefox (https://github.com/puppeteer/puppeteer/commit/0c688bd75ef1d1fc3afd14cbe8966757ecda68fb)
- a few new tests to add to the puppeteer-expected.json
Reporter | ||
Comment 3•3 years ago
|
||
(In reply to Julian Descottes [:jdescottes] from comment #2)
- there are new failures for existing cookies tests, because puppeteer starts testing non standard properties, not supported in Firefox (https://github.com/puppeteer/puppeteer/commit/0c688bd75ef1d1fc3afd14cbe8966757ecda68fb)
Would you mind filing an upstream issue? I would like to know what can be done here to keep the cross-browser compatibility for cookie tests. It would be bad if we have to mark them as disabled.
- a few new tests to add to the puppeteer-expected.json
Would be interested in the numbers of how many pass/fail now. So lets hope try will be back soon.
Thanks Julian!
Assignee | ||
Comment 4•3 years ago
|
||
Would you mind filing an upstream issue?
Filed https://github.com/puppeteer/puppeteer/issues/6976
I assume it should be doable to only check the non-standard properties when running in Chrome?
Would be interested in the numbers of how many pass/fail now
Here's a quick breakdown:
New tests:
- PASS: Page Page.waitForRequest should work with async predicate (page.spec.ts)
- PASS: JSHandle JSHandle.jsonValue works with jsonValues that are not objects (jshandle.spec.ts)
- PASS: JSHandle JSHandle.jsonValue works with jsonValues that are primitives (jshandle.spec.ts)
- FAIL: Page Page.emulateNetworkConditions should change navigator.connection.effectiveType (page.spec.ts)
- FAIL: Launcher specs Puppeteer Puppeteer.connect should be able to reconnect (launcher.spec.ts)
The existing TIMEOUT test Page Page.Events.Popup should work with clicking target=_blank (page.spec.ts) was split in 2:
- TIMEOUT: Page Page.Events.Popup should work with clicking target=_blank and without rel=opener (page.spec.ts)
- TIMEOUT: Page Page.Events.Popup should work with clicking target=_blank and with rel=opener (page.spec.ts)
The existing FAIL test Screenshots Page.screenshot should clip elements to the viewport (screenshot.spec.ts) was changed and is now passing (we didn't clip to the viewport, and puppeteer doesn't expect that anymore):
- PASS: Screenshots Page.screenshot should get screenshot bigger than the viewport (screenshot.spec.ts)
So overall, just 2 new FAIL so far. One for emulateNetworkConditions, which is expected. The second one is more interesting Puppeteer.connect should be able to reconnect
, not sure yet why this fails for Firefox.
You can check the current sync diff at https://hg.mozilla.org/try/rev/5d03c9221e0998f1cbbd1e5be7b927fc35d0313d
Reporter | ||
Comment 5•3 years ago
|
||
(In reply to Julian Descottes [:jdescottes] from comment #4)
So overall, just 2 new FAIL so far. One for emulateNetworkConditions, which is expected. The second one is more interesting
Puppeteer.connect should be able to reconnect
, not sure yet why this fails for Firefox.
Sounds ok. The reconnect test is new? I can remember that I have also seen problems when running the chrome-remote-interface unit tests. But no idea why it's failing.
Assignee | ||
Comment 6•3 years ago
|
||
Generated by running ./mach remote vendor-puppeteer and replacing itFailsFirefox to it etc...
Assignee | ||
Comment 7•3 years ago
|
||
Depends on D108099
Summary of changes.
New tests:
- PASS: Page Page.waitForRequest should work with async predicate (page.spec.ts)
- PASS: JSHandle JSHandle.jsonValue works with jsonValues that are not objects (jshandle.spec.ts)
- PASS: JSHandle JSHandle.jsonValue works with jsonValues that are primitives (jshandle.spec.ts)
- FAIL: Page Page.emulateNetworkConditions should change navigator.connection.effectiveType (page.spec.ts)
- FAIL: Launcher specs Puppeteer Puppeteer.connect should be able to reconnect (launcher.spec.ts)
The existing TIMEOUT test "Page Page.Events.Popup should work with clicking target=_blank (page.spec.ts)" was split in 2:
- TIMEOUT: Page Page.Events.Popup should work with clicking target=_blank and without rel=opener (page.spec.ts)
- TIMEOUT: Page Page.Events.Popup should work with clicking target=_blank and with rel=opener (page.spec.ts)
The existing FAIL test "Screenshots Page.screenshot should clip elements to the viewport (screenshot.spec.ts)" was changed and is now passing (we didn't clip to the viewport, and puppeteer doesn't expect that anymore):
- PASS: Screenshots Page.screenshot should get screenshot bigger than the viewport (screenshot.spec.ts)
The existing SKIP test "Launcher specs Puppeteer Puppeteer.launch should be able to launch Firefox (launcher.spec.ts)" is now running with itFailsWindows instead of itOnlyRegularInstall. It used to be flagged as SKIP, but it is now failing because we attempt to run it.
- FAIL: Launcher specs Puppeteer Puppeteer.launch should be able to launch Firefox (launcher.spec.ts)
Assignee | ||
Comment 8•3 years ago
|
||
Depends on D108099
Synchronize the upstream change merged at https://github.com/puppeteer/puppeteer/pull/6994
Pushed by jdescottes@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/c91e827cf38a [puppeteer] Sync vendored puppeteer to v8.0.0 r=remote-protocol-reviewers,whimboo https://hg.mozilla.org/integration/autoland/rev/6a73f4984952 [puppeteer] chore: skip non-standard cookie asserts on Firefox (sync #6994) r=remote-protocol-reviewers,whimboo https://hg.mozilla.org/integration/autoland/rev/d3089529400c [puppeteer] Update puppeteer-expected.json for v8.0.0 r=remote-protocol-reviewers,whimboo
Comment 10•3 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/c91e827cf38a
https://hg.mozilla.org/mozilla-central/rev/6a73f4984952
https://hg.mozilla.org/mozilla-central/rev/d3089529400c
Updated•3 years ago
|
Description
•