fix(webkit): support Cross-Origin-Opener-Policy navigation

[yury-s]

WebKit recently enabled support for Cross-Origin-Opener-Policy / Cross-Origin-Embedder-Policy and decision about whether navigation should happen in a new process now made twice:

• navigation policy decision
• response policy decision

In the latter case the requestWillBeSent and responseReceivedEvents are fired in the original process and then (if process should be swapped) fired again in the new process (with new request id but same loaderId). Moreover, after the response policy decision the old process will send Page.frameStoppedLoading and Network.loadingFailed(canceled) events. We now ignore those events if there is ongoing navigation in a provisional page.

Fixes #9065

[dgozman]

I am afraid this might not be always the case. For example, we navigate to cross-origin 204 page that creates a provisional page but never commits?

[yury-s]

Coincidentally that works because we generate loadingFinished event in WebKit ourselves when 204 response comes:

playwright/src/server/webkit/wkPage.ts

Lines 1023 to 1030 in 45b365d

	if (response.status() === 204) {
	this._onLoadingFailed({
	requestId: event.requestId,
	errorText: 'Aborted: 204 No Content',
	timestamp: event.timestamp
	});
	}
	}

With network failures we will receive Playwright.provisionalLoadFailed and that will abort the navigation, so we are good in that case too. Added a test.

[dgozman]

Can we ignore responses from the old web process only? This ensures that we get correct response from the new web process, in case WebKit fixes more security holes in the old web process and send bogus response from there (if any).

[yury-s]

At the moment response notification comes from old process we don't know if it's gonna be a cross-process or same process navigation. In case of same-process navigation we have to dispatch messages from the old process. Unless we introduce a separate notification that the navigation turned into cross-process and buffer up some messages from old web process before the notification arrives we cannot safely ignore responses from the old web process .

[mxschmitt]

Seems not needed anymore, closing.