Currently Chrome rejects the FetchEvent.preloadResponse promise with an error when redirected.
https://chromium.googlesource.com/chromium/src/+/2fd0fdd/content/renderer/service_worker/service_worker_context_client.cc#295
But according to the spec, the promise should be resolved with the redirect response.
https://w3c.github.io/ServiceWorker/#handle-fetch
> 1. Fetch preloadRequest.
> To process response for navigationPreloadResponse, run these substeps:
> 1. If navigationPreloadResponse’s type is "error", reject preloadResponse with a TypeError and terminate these substeps.
> 2. Associate preloadResponseObject with navigationPreloadResponse.
> 3. Resolve preloadResponse with navigationPreloadResponse.
horo@, Thanks for taking a stab at this. Since this is a fix to an Original Trial, do you think it will be possible to get this cherrypicked in M57? Barring that, what's the soonest we would be able to get this to prod?
The internal bug for Docs is b/36734243 in which we lay out how this bug makes many things problematic, and will probably block our participation in the Original Trial on this bug.
Thanks!
This patch for the fix is not a trivial one. I think it is imposiible to merge to M57.
The branch cut day of M59 is Apr 13.
If I can land the patch before the day, it will be available in Stable from Jun 6th.
https://www.chromium.org/developers/calendar
Your change meets the bar and is auto-approved for M58. Please go ahead and merge the CL to branch 3029 manually. Please contact milestone owner if you have questions.
Owners: amineer@(Android), cmasso@(iOS), bhthompson@(ChromeOS), govind@(Desktop)
For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Comment 1 by ralp...@google.com
, Mar 27 2017