Puppeteer E2E test: Use new headless mode

[LeviPesin]

Related issue: #25979
(I cannot access my computer currently to do a force push so I just created a new branch from an older commit and made new PR)

[mrdoob]

Reposting my comment from #25979

The issue is the difference of text rendering between all three OSes.

Then... How about we just test in one OS as we used to?

I have yet to see any benefit in testing on all OSes...

[LeviPesin]

Wouldn't that confuse people if they try to (re)generate screenshot on their machine and then after commiting it see that it doesn't work because it renders differently on Linux? Currently we can see which screenshots render differently on which OSes.

[mrdoob]

I guess we have to pick one...

1. Making contributors generate screenshots using MacOS (and we maintainers can help)
2. Continue battling with Puppeteer timeouts, text rendering issues, and waiting for CI tests that take 3x longer 😅

[LeviPesin]

The MacOS is the worst OS for running CI tests -- currently Mac tests sometimes don't complete even in 20 minutes. If we are going to select one it's better to return to the Ubuntu.

[mrdoob]

Does any of them support WebGPU yet? 🤔

[linbingquan]

Chrome 113 supported WebGPU by default, I tested it can generated screenshot with WebGPU examples in my computer (windows 11) with puppeteer 20.1.0.

I tried commit this code in my repo to test, but it has some fail... TBH, I have no idea how to fix it.

P.S. puppeteer-core 20.1.0 use Chrome 113, but it does not have BrowserFetcher API...

[LeviPesin]

I think the problem is not that Chrome doesn't support WebGPU (it does behind a flag) but that Chrome headless mode doesn't. Maybe in this new mode which should be more similar to headful it would...

[Mugen87]

(it does behind a flag)

To clarify: Since 113 enabling a flag isn't necessary anymore. WebGPU works right out of the box.

[LeviPesin]

Can we merge this PR? I plan again to work on E2E (replacing BrowserFetcher with @browsers, retesting exceptions, tweaking timeouts, adding support for setInterval/setTimeout, maybe removing text completely for fixing few exceptions, trying to add support for WebGPU again) soon (maybe next week).
We can discuss whether we should keep three OSes or return to one (Ubuntu) in another issue.

[mrdoob]

Okay!