Summary: | WebSWServerConnection::startFetch() should never fail synchronously | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Chris Dumez <cdumez> | ||||
Component: | Service Workers | Assignee: | Chris Dumez <cdumez> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | beidson, commit-queue, ggaren, webkit-bug-importer, youennf | ||||
Priority: | P2 | Keywords: | InRadar | ||||
Version: | WebKit Nightly Build | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
See Also: | https://bugs.webkit.org/show_bug.cgi?id=205261 | ||||||
Attachments: |
|
Description
Chris Dumez
2019-12-13 16:10:34 PST
Created attachment 385654 [details]
Patch
r=me Comment on attachment 385654 [details] Patch Clearing flags on attachment: 385654 Committed r253528: <https://trac.webkit.org/changeset/253528> All reviewed patches have been landed. Closing bug. http/wpt/service-workers/postMessage-fetch-order.https.html fails consistently. The spec does not mandate the order between fetch and postMessage since these are different sources so we could update the test accordingly. An alternative would be to only delay the didNotHandle case, which would remove an unnecessary dispatch in the usual case. |