Ben Kelly

FYI, I am in the process of moving our limit on "internal" redirects to be separate from the "real" redirect count. This would make it easier to align our redirect...

Yeah, I think we removed it from MDN when it became apparent the spec was not immediately moving forward.

FWIW, one reason I have seen to implement FetchObserver is that using streams to observe progress of wasm bundle downloads ends up breaking bytecode caching optimizations.

So it appears that I was confused about site-for-cookies for navigations. @sbingler has explained that this section: https://tools.ietf.org/id/draft-ietf-httpbis-rfc6265bis-03.html#rfc.section.5.2.1 Says the site-for-cookies for a navigation is determined by the frame being...

That is solved by partitioning with the "ancestor chain bit". We can set site-for-cookies properly for the service worker context based on the information in the StorageKey. That is better...

> Per https://github.com/wanderview/quota-storage-partitioning/blob/main/explainer.md it seems that @wanderview et al plan to use > > `` I don't think that is accurate. The SW partitioning proposal would effectively key on ``...

Service workers could carry the "iframe-navigation bit" forward through a pass-through fetch if we wanted to. Ideally this would be tied to the destination, but it could also be a...

> slightlyoff/ServiceWorker#584 tracks FetchEvent.waitUntil(), which looks like will make it to browsers at some point. FWIW, FetchEvent.waitUntil() is in Chrome and will be in the first version of SW's shipped...

@blakeembrey PTAL. This is the first in a series of pull requests to add changes/features necessary for urlpattern. This first PR adds `*` wildcard support. Note, I was going to...

I would expect the service worker to be killed after 5 minutes of being held open by respondWith() processing an SSE response. (Unless another FetchEvent or something occurred since then...