service-worker

I'm testing under Chrome Version 42.0.2311.152m and I want to implement to open a window on a notificationclick like in this example: (source: https://developer.mozilla.org/en-US/docs/Web/API/WindowClient ) self.addEventListener('notificationclick', function(event) { console.log('On notification click: ', event.notification.tag); event.notification.close(); // This looks to see if the current is already open and // focuses if it is event.waitUntil(clients.matchAll({ type: "window" }).then(function(clientList) { for (var i = 0; i < clientList.length; i++) { var client = clientList[i]; if

I wish to make a fetch call after the push event for fetching the notif data through an internal api with user specific params which are stored in the localstorage or cookie such as usertype or country id .. how do i do this ? You cannot use Local Storage in service workers. It was decided that service workers should not have access to any synchronous APIs. You can use IndexedDB instead, or communicate with the controlled page using postMessage() . By default, cookies are not included with fetch requests, but you can include them as follows: fetch(url, {credentials: 'include'}) . 来源： https:/

I have a Polymer app with service workers hosted with Firebase. The app works fine on every browser except Firefox. When you try to refresh the browser in Firefox after initial load (which works), it throws the following error: A ServiceWorker passed a redirected Response to FetchEvent.respondWith() while RedirectMode is not ‘follow’ The service-worker.js is auto-generated by the polymer-cli (v0.16.0). To address this known issue , set the redirect option to follow in your service worker's fetch() requests: fetch(..., { redirect: 'follow' }) 来源： https://stackoverflow.com/questions/40274429

I have a web app that is working and relying on service workers to keep all the cached files in check and to make sure users are on the correct version of the app. Our client is currently wanting the device to check for an update at specific points (When reopening the app) etc, as currently when you open the app it can take up to 5minutes before the device realises its on an outdated version. Am I able to force the device to check the service worker for any new changes instead of waiting for the app to check for me? Thanks! There are two main points you should refine for instant update of your

I have updated my angular app into PWA, since I need to preload all of the assets on the first launch (application have a lots of images, which are used for UI). That's why I would like to show some kind of spinner/loading bar during service worker install event and hide it when it's done. So first question - is it possible to handle this event from the component? I have found this example and tried to add it inside first component, that loads on app launch, but didn't get any logs. So probably it doesn't work that way. ngOnInit() { self.addEventListener('install', event => { this.log(

How do I get page URL with parameters from a service worker? I have tried self.registration.scope but that doesn't include the parameters. I'm not clear as to whether you're asking about getting the service worker script's URL, or the URLs of all of the client pages that are open under the service worker's scope. So... here's how to do both: // Get a URL object for the service worker script's location. const swScriptUrl = new URL(self.location); // Get URL objects for each client's location. self.clients.matchAll({includeUncontrolled: true}).then(clients => { for (const client of clients) {

I've deployed a new version of my site (It was on Polymer, now on Vue.js) to Firebase over an existing project. I'm using default Vue.js template with Webpack ( vue init webpack my-project ) in the new project Now that I've deployed the new version, when I open the site I see just a cached shell, I assume that's the service worker's fault In order to get actual current files from Firebase I (and all the previous visitors) have to now hard refresh the site every time ( Ctrl+F5 in firefox) Console Now, in browser console (network tab) I see: The service worker in red, it says: (failed) net::ERR