canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,747
edits
WebDriver/RemoteProtocol/Meetings/2020/02/26: Difference between revisions
WebDriver/RemoteProtocol/Meetings/2020/02/26 (view source)
Revision as of 20:09, 26 February 2021
, 26 February 2021Whimboo moved page Remote/Meetings/2020/02/26 to WebDriver/RemoteProtocol/Meetings/2020/02/26: Reorganization for WebDriver BiDi project documenation
m (→Agenda: -) |
m (Whimboo moved page Remote/Meetings/2020/02/26 to WebDriver/RemoteProtocol/Meetings/2020/02/26: Reorganization for WebDriver BiDi project documenation) |
||
| (3 intermediate revisions by one other user not shown) | |||
| Line 7: | Line 7: | ||
; Present | ; Present | ||
:dreams, Joel Einbinder (Microsoft), :maja_zf, :mmucci, :whimboo | |||
== Minutes == | |||
[whimboo] Will work on describeNode next which is one of the main blockers for Puppeteer and a lot of Puppeteer unit tests | |||
[maja_zf] Finishing off the patch for downloading Firefox when puppeteer is installed. Lots of Puppeteer code around this is tightly coupled with other areas, so unravelling that and removing Chrome-only assumption in lots of places. | |||
* Next will return focus on protocol implementation. Maybe investigate setContent (which would use up a contingency bug in our planning) | |||
Puppeteer's page.setContent (https://bugzilla.mozilla.org/show_bug.cgi?id=1612174) | |||
* [joel] lots of people are using it judging by Playwright issues | |||
** in Playwright it sends a console.debug() call: https://github.com/microsoft/playwright/blob/master/src/frames.ts#L622 | |||
* [joel] init event is used to indicate the next load is for setContent | |||
[maja] foolip raised an issue for running puppeteer with firefox (https://github.com/puppeteer/puppeteer/issues/5437) | |||
* The problem is that one needs to provide an executable path for Firefox, which isn't clearly explained in the docs | |||
* This is be irrelevent after automatic browser fetching works for Firefox, so Maja will reply by pointing to that PR | |||
[mmucci] Project status: | |||
* We are 74% complete, 8 bugs remaining and 2 contingency bugs | |||
* 5th Milestone from 26th Feb March 10th | |||
* We may be able to finish on May 19th | |||
[joel] Playwright update: | |||
* Playwright team is landing lots of patches in upstream WebKit, especially their web inspector | |||
* Playwright webkit browser diff includes lots of browser fixes in addition to protocol | |||
* Aiming for 1.0 in March | |||
* Webkit crashing a lot on windows | |||
* The Playwright Firefox diff is just the custom protocol, no browser fixes. | |||
* Only Firefox issue is slow start-up, 2000 ms in headless mode versus 15 ms for Chrome. Joel will file a bug. | |||
** [joel] Could it be because Firefox headless mode is fundamentally different and this startup time is expected? | |||
** [maja] We welcome everyone to file bugs, it's a very good way to collaborate even if you're not submitting patches | |||
** [whimboo] You can attached info from Firefox Profiler https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Profiling_with_the_Built-in_Profiler#Profiling_Firefox_Startup | |||
== Progress == | == Progress == | ||
| Line 58: | Line 82: | ||
== PTO == | == PTO == | ||
* maja_zf: some days in first week of March, TBC | |||