Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Learn more about Collectives

Teams

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

Learn more about Teams

Im trying to understand the difference between skipWaiting and clientsClaim . In my understanding: calling skipWaiting will cause the new service worker to skip the waiting phase, and become active right away. clientsClaim can then 'claim' any other open tabs as well.

What I gather from documentation online:

skipWaiting skips the waiting phase, and becomes active right away source

clientsClaim immediately start controlling pages source

In every post I find online, I usually always see clientsClaim and skipWaiting used together.

However, I recently found a service worker that only uses clientsClaim , and I'm having a hard time wrapping my head around what actually is the difference between clientsClaim and skipWaiting , and in what scenario do you use clientsClaim but not skipWaiting ?

My thinking on this, and this may be where I'm wrong, but this is my understanding of it: Is that calling clientsClaim , but not skipWaiting is redundant? Considering:

The new service worker will become active when all open pages are closed (because we're not using skipWaiting )

When our new service worker is activated, we call clientsClaim , even though we just closed all open pages to even activate the new service worker. There should be no other pages to control, because we just closed them.

Could someone help me understand?

Read documentation on skipWaiting

Read documentation on clientsClaim

Read about service worker lifecycle by Jake Archibald, and played around with this demo

Read a bunch of stackoverflow posts, offline cookbook, different blog posts, etc.

"Active" in this sense does not mean any currently loaded clients are now talking to that service. It instead means that service is now the service to be used whenever a new client requests it.

This is where Clients.claim() comes in:

When a service worker is initially registered, pages won't use it until they next load.

Without calling claim , any existing clients will still continue to talk to the older service worker until a full page load.

While most of the time it makes sense to use skipWaiting and Clients.claim in conjunction, that is not always the case. If there is a chance of a poor experience for the user due to a service worker not being backwards compatible, Clients.claim should not be called. Instead, the next time a client is refreshed or loaded, it would now have the new service worker without worry of the breaking change.

Thanks! That clarifies a lot already. So just making sure I understand this correctly, lets say I have my site open in a tab: tab-a . If I call skipWaiting , and refresh tab-a , the new service worker becomes active, but tab-a is actually still using the old service worker? (e.g.: in dev tools you'll see service worker #3071 as being active and running, but the previous service worker , service worker #3070 i actually still controlling the page? Additionally, what is the usecase for only using clientsClaim but not skipWaiting ? – Pazzle Sep 20, 2019 at 16:17 The case you described is correct. IIRC you'll actually see both as being active pre-refresh. In regards to the usecase of clientsClaim being used on its own, I can't think of one. – Justin Collins Sep 20, 2019 at 21:48

The difference between skipWaiting() and Clients.claim() in Service Workers

An important concept to understand is that for a service worker to become operational on a page it must be the controller of the page. (You can actually see this property in Navigator.serviceWorker.controller .) To become the controller, the service worker must first be activated, but that's not enough in itself. A page can only be controlled if it has also been requested through a service worker.

Normally, this is the case, particularly if you're just updating a service worker. If, on the other hand, you're registering a service worker for the first time on a page, then the service worker will be installed and activated but it will not become the controller of the page because the page was not requested through a service worker.

You can fix this by calling Clients.claim() somewhere in the activate handler. This simply means that you wont have to refresh the page before you see the effects of the service worker.

There's some question as to how useful this actually is. Jake Archibald, one of the authors of the spec, has this to say about it:

I see a lot of people including clients.claim() as boilerplate, but I rarely do so myself. It only really matters on the very first load, and due to progressive enhancement the page is usually working happily without service worker anyway.

As regarding its use with other tabs, it will again only have any effect if those tabs were not requested through a service worker. It's possible to have a scenario where a user has the same page open in different tabs and has these tabs open for a long period of time, during which the developer introduces a service worker. If the user refreshes one tab but not the other, one tab will have the service worker and the other will not. But this scenario seems somewhat uncommon.

skipWaiting()

A service worker is activated after it is installed, and if there is no other service worker that is currently controlling pages within the scope. In other words, if you have any number of tabs open for a page that is being controlled by the old service worker, then the new service worker will not activate. You can therefore activate the new service worker by closing all open tabs. After this, the old service worker is controlling zero pages, and so the new service worker can become active.

If you don’t want to wait for the old service worker to be killed, you can call skipWaiting() . Normally, this is done within the install event handler. Even if the old service worker is controlling pages, it is killed anyway and this allows the new service worker to be activated.

If a PWA is served by an service worker, and the PWA creates an iframe with src in the scope of the service worker, then does the service worker serve the iframe contents too? Does the iframe document have to do anything special to get served by the service worker of its parent? – Max Waterman Jan 12, 2021 at 4:27

Thanks for contributing an answer to Stack Overflow!

• Please be sure to answer the question . Provide details and share your research!

But avoid …

• Asking for help, clarification, or responding to other answers.
• Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers .