Andrew Sutherland

@annevk A recurring use-case in the Service Workers/Storage space is that a single origin may be divided up into sub-sites each handled by largely independent teams. If each team defines...

> This would mean that we'd run an algorithm for each impacted bottle once, in the "storage process". I'm trying to reconcile this with the algorithm being run inside the...

I've filed https://bugzilla.mozilla.org/show_bug.cgi?id=1551557 to track any Firefox specific implementation issues and our investigation of this. We'll be sure to chime back in here for any spec-related things and/or once we...

Firefox is still willing to implement this based on the original motivations. As is visible [in our implementation bug](https://bugzilla.mozilla.org/show_bug.cgi?id=1456479), our implementation stalled on some testing issues and was shelved as...

As a heads up, we're probably going to remove Firefox's (never shipped, always disabled via preference) WIP (as implemented in parts 4 and 5 of [this bug](https://bugzilla.mozilla.org/show_bug.cgi?id=1341738)) related to FetchObserver...

The advantage of specifying 2 (evict on receipt of any message) for now: - It's arguably easier to relax this constraint than to tighten them, although you could experience breakage...

It seems like the introduction of a `pagehide` event requires some explicit concept of a grace period for the worker to finish what it's doing and process an explicitly dispatched...

To be clear, I'm on board with the potential benefits of letting workers clean up. My concern is how long the window for "timely execution" has to be before we...

> So, are we fine to have dedicated events for bfcache-features rather than pagehide/pageshow, like "beingPutToBFcache" "restoredFromBfcache"? My concern isn't so much about the name, but the steps related to...

I support the refined semantics for "beingPutToBFCache". And thank you for the explicit restatement of the semantics; those make sense and I benefited from the clarity. In terms of the...