From 142e7ae3cb323560b9d7818d0b409f082167d8e8 Mon Sep 17 00:00:00 2001 From: Piotr Delawski Date: Mon, 17 Aug 2020 14:01:51 +0200 Subject: [PATCH] Update the way a navigation route is registered The way a navigation route is registered changed in Workbox 5 (GoogleChrome/workbox#2095). --- .../js/service-worker-navigation-routing.js | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/wp-includes/js/service-worker-navigation-routing.js b/wp-includes/js/service-worker-navigation-routing.js index 122178365..f6a6e1df1 100644 --- a/wp-includes/js/service-worker-navigation-routing.js +++ b/wp-includes/js/service-worker-navigation-routing.js @@ -158,11 +158,15 @@ ERROR_OFFLINE_URL, ERROR_500_URL, NAVIGATION_DENYLIST_PATTERNS, ERROR_MESSAGES * (pattern) => new RegExp(pattern) ); if (navigationRouteEntry && navigationRouteEntry.url) { - wp.serviceWorker.routing.registerNavigationRoute( - navigationRouteEntry.url, - { - denylist, - } + wp.serviceWorker.routing.registerRoute( + new wp.serviceWorker.routing.NavigationRoute( + wp.serviceWorker.precaching.createHandlerBoundToURL( + navigationRouteEntry.url + ), + { + denylist, + } + ) ); class FetchNavigationRoute extends wp.serviceWorker.routing.Route {