715
edits
(→Roster: fill in) |
(→Minutes: from gdocs) |
||
Line 15: | Line 15: | ||
== Minutes == | == Minutes == | ||
* ochameau has been ensuring we can connect to Puppeteer | |||
* Last week ochameau also looked at the WordPress test suite | |||
** Succinct user stories lends themselves well for ramping up work on the most important features | |||
** They are using an older target selection technique from an earlier Puppeteer version | |||
** Supporting earlier Puppeteer versions? | |||
*** Not a big effort, but sort of unfortunate that WordPress is not using upstream Puppeteer | |||
*** Supporting the few additional target location methods is probably useful also for other CDP consumers | |||
*** Interesting data point that significant test suites in the wild are not necessarily using the latest Puppeteer, and that this has consequences for which Chrome versions they test against | |||
*** No indication ''why'' they are stuck on an old version | |||
* Running tests on try currently blocked by not building the remote agent as part of Firefox | |||
** ato will be working on that this week, then possibly on running the Puppeteer test suite on try afterwards | |||
** Should we run the WordPress test suite on try? | |||
*** It has lots of difficult dependencies, so likely hard | |||
*** But we are landing fixes with tests attached, so it’s not really a necessity | |||
** Chrome has lower-level CDP tests we should probably investigate running | |||
*** https://chromium.googlesource.com/chromium/src/+/master/third_party/blink/web_tests/inspector-protocol | |||
* What is remote agent announcement blocked on? | |||
** '''ACTION:''' sole will check | |||
== Changelog == | == Changelog == |
edits