[Webkit-unassigned] [Bug 279458] WindowClient.matchAll resolves promise too early

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=279458

--- Comment #3 from youenn fablet <youennf at gmail.com> ---
I uploaded the patch above.
Looking at the results though, it is not compatible with the WPT tests.

This exhibits 
Some service workers expect get/matchAll to resolve before actually answering the fetch event.
Some tests that fail:
- https://wpt.fyi/results/service-workers/service-worker/controlled-iframe-postMessage.https.html. It expects get to resolve. Chrome is timing out like Safari would with this patch. Firefox and stock Safari are passing the test.
- https://wpt.fyi/results/service-workers/service-worker/navigation-preload/redirect.https.html. It expects matchAll() to resolve. All browsers are passing but it is unclear whether the same set of clients are matching in all browsers.

I did some tests to check what matchAll and get give in the case of a being fetched new iframe:

1. matchAll
- Chrome does not list the iframe client
- Firefox lists the iframe client as 'about:blank'
- Safari lists the iframe client with its request URL

2. get
- Chrome does not list the iframe client
- Firefox lists the iframe client as 'about:blank'
- Safari lists the iframe client with its request URL

I'll update the patch to align with Chrome for matchAll.
This will reduce the possibility of web pages trying to focus/openWindow/postMessage clients that are not yet ready.
This is aligned with the spec ignoring clients whose execution ready flag (https://html.spec.whatwg.org/multipage/webappapis.html#concept-environment-execution-ready-flag) is not set.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20241029/52b00b40/attachment.htm>