Enable Support for WebDriver-Bidi in Firefox

[pyoor]

Summary

Closes #609.

Support for CDP was removed in Firefox v141, leaving WebDriver BiDi as the only supported automation protocol. However, Firefox currently does not support multiple concurrent WebDriver BiDi sessions.

To work around this limitation, the setup has been modified to:

• Launch the browser once
• Record the wsEndpoint
• Immediately disconnect

Subsequent access to the browser is handled via puppeteer.connect() using the saved wsEndpoint, ensuring only a single active connection at any time.

Note: I made the minimal changes necessary in order to re-enable support for Firefox. This PR could likely be cleaned up further.

Test Plan

Firefox-specific tests were added and can be run via the test:firefox npm script.

Note: These tests only pass when using jest-environment-puppeteer.
expect-puppeteer is currently incompatible with WebDriver BiDi and supports only CDP, as noted in issue #614.

[gregberge]

I don't understand the concept of this PR sorry. We are now disconnecting all browsers instantely and we connect / disconnect into the close browsers function. Something is not clear to me.

[gregberge]

Why disconnecting directly?

[gregberge]

Can you just do a map instead of doing a loop like that?

[gregberge]

Why do we have a hack here?

[gregberge]

Why are we connecting into the closeBrowsers

[pyoor]

@gregberge I decided to reply here rather than in-line as you may prefer an alternative approach.

Firefox 141+ no longer works because it dropped supported for CDP (puppeteer also remove CDP support for Firefox) and it does not support multiple connections over WebDriver BiDi (CDP did). The easiest way to re-enable support for Firefox is to first launch the browser and record the wsEndpoint. We have to disconnect after the initial setup as other connections are made during connectBrowserFromWorker.

jest-puppeteer/packages/jest-environment-puppeteer/src/browsers.ts

Lines 125 to 136 in ddb3fb9

	export const connectBrowserFromWorker = async (
	config: JestPuppeteerConfig,
	): Promise<Browser> => {
	const wsEndpoint = getWorkerWsEndpoint();
	const puppeteer = getPuppeteer();
	return puppeteer.connect({
	...config.connect,
	...config.launch,
	browserURL: undefined,
	browserWSEndpoint: wsEndpoint,
	});
	};

This will throw in firefox. See #609.

I suppose an alternative (and cleaner) fix here would be to return the existing browser instance from globalThis.__jestPptr.browsers in connectBrowserFromWorker? I don't see why it wouldn't work but I also don't know the reasoning for the original multiple connections.

[pyoor]

@gregberge Just following up on this. Is there one approach you'd prefer over the other?