Closed pmeenan closed 1 year ago
sweet! So much better with fewer non-actionables. Not sure why the build job failed, attempting again...
Looks like there is a "scheduled brownout" for ubuntu 18.04 CI tests to get people's attention that it will be going away on April 1st when 18.04 reaches EOL.
Once the prod WPT servers are moved to 22.04 the CI tests can be updated (should probably make sure the prod teams are on it to update the images).
Note that the official launch for the new Headless mode (albeit still behind the --headless=new
flag) is M112, which is currently the Canary channel. (We’ve been landing some fixes up until recently.)
Chrome 112 is scheduled for Beta between March 9–16, and Stable on March 29th.
Not sure why the rebase isn't showing up cleanly over here but it is trying to pick up way more changes than the latest branch. Going to close this and open a new PR now that Chrome 112 has rolled to stable.
Chrome has a "new" headless mode in 109+ (technically added in 96 but it's the official way now) that makes headless Chrome behave much more like the real Chrome with UI and uses all of the same code. Of particular note for WebPageTest is that this makes the lighthouse audits (where headless is used) more accurate and fixes issues with the BF cache audit.
Before (for WebPageTest):![Screenshot 2023-02-21 at 10 49 24 AM](https://user-images.githubusercontent.com/444165/220393443-a2091f91-e114-426b-b171-63fd9bcd11d2.png)
After (for WebPageTest):![Screenshot 2023-02-21 at 10 39 08 AM](https://user-images.githubusercontent.com/444165/220393539-3048fc3d-6fb6-430e-894f-43ec8ca2fbca.png)
Before (for Google Search):![Screenshot 2023-02-21 at 10 49 50 AM](https://user-images.githubusercontent.com/444165/220393595-e9e9c76b-6623-44a6-94fd-104f4d0bee10.png)
After (for Google Search):![Screenshot 2023-02-21 at 10 38 36 AM](https://user-images.githubusercontent.com/444165/220393664-2b27fea4-2e37-44c5-9272-acd4a3a884dd.png)
This also removes the hack of using the lighthouse legacy navigation flow (the issue in 10.0 that required it was fixed right before 10.0 was released).