canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,714
edits
WebDriver/RemoteProtocol/Meetings/2020/03/04: Difference between revisions
WebDriver/RemoteProtocol/Meetings/2020/03/04 (view source)
Revision as of 20:09, 26 February 2021
, 26 February 2021Whimboo moved page Remote/Meetings/2020/03/04 to WebDriver/RemoteProtocol/Meetings/2020/03/04: Reorganization for WebDriver BiDi project documenation
(Milestone status update) |
m (Whimboo moved page Remote/Meetings/2020/03/04 to WebDriver/RemoteProtocol/Meetings/2020/03/04: Reorganization for WebDriver BiDi project documenation) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 3: | Line 3: | ||
* Project Status Update [mmucci] | * Project Status Update [mmucci] | ||
* Communicating project status [maja_zf] | * Communicating project status [maja_zf] | ||
* For cookies sameSite=Lax is default now in Firefox Nightly [henrik] | |||
* Inspector protocol tests [henrik] | * Inspector protocol tests [henrik] | ||
== Roster == | == Roster == | ||
| Line 14: | Line 10: | ||
; Present | ; Present | ||
dreams, marco, maja_zf, whimboo | |||
== Minutes == | == Minutes == | ||
=== Status update === | |||
* On track, 2 bugs per milestone | |||
* 0 contigency bugs left | |||
Q: Should we move bug out of mvp if something comes up? | |||
: Yes, must do a swap. | |||
=== Communicating project status === | |||
* No user-friendly status page | |||
** Reporting Puppeteer API support (which we impact indirectly) versus CDP support (what we're actually working on)? | |||
** Old CDP status dashboard depends on Bugzilla structure we don't use since October, so it reports inaccurate data https://andreastt.github.io/remotedash/ | |||
* What should Puppeteer users look at? | |||
** Puppeteer team could publish summary of unit test results ("Is Puppeteer + Firefox ready") similar to what they did for Juggler | |||
* Best source of info for internal/external collaborators is [[Remote/Milestones]] | |||
** Marco will update the queries to match his spreadsheet for the beta milestone | |||
* [devin] what does the beta milestone actually mean? | |||
** [maja] We looked at different sources for how often CDP methods and events are in use by various frameworks and testsuites and prioritized accordingly. Can think of it as what would get the tools working for Firefox for 90% of use-cases? To measure completeness: might not be high percentage of Gutenberg, maybe 70% puppeteer unit tests | |||
** [henrik] Could Devin can have a look at [[Remote/Milestones]] and tell us his ideas what could / needs to be on this page | |||
*** Based on that feedback we can add more information for overall target and for each of the milestones | |||
* After beta we should target a Hacks blog post to get further feedback from end-users of puppeteer for next goals | |||
=== Cookies === | |||
* Upstream Puppeteer tests started to fail for Firefox but not Chrome, which should have it since the 80 release | |||
* Does Puppeteer disable it? No feedback from Mathias yet. | |||
* Disable the pref in Firefox for now. | |||
=== CDP Tests === | |||
* Got links from Joel when asking about basic tests | |||
** https://cs.chromium.org/chromium/src/third_party/blink/web_tests/inspector-protocol/dom/resources/?g=0 | |||
** https://cs.chromium.org/chromium/src/third_party/blink/web_tests/http/tests/inspector-protocol/ | |||
** https://cs.chromium.org/chromium/src/v8/test/inspector/runtime/ | |||
* Also listed in [[Remote/Developer Resources]] | |||
* We may not want to import and run those tests in our CI, but might be a good resource for our browser chrome tests | |||