Ming-Ying Chung

Note: the spec has been moved to https://wicg.github.io/unload-beacon/

Sent out https://github.com/google/comprehensive-rust/pull/757 to rename `zh-Hant.po` to `zh-TW.po`

> If the user agent has determined that deferred fetching is not allowed in this context, then throw a [ NotAllowedError ](https://webidl.spec.whatwg.org/#notallowederror). > what is the model for this in...

> f the user agent has determined that deferred fetching is not allowed in this context, then throw a [NotAllowedError ](https://webidl.spec.whatwg.org/#notallowederror). After some offline discussions, we think it's fine to...

> in the past we talked about restricting this behind a background fetch permission, as both have similar characteristics. We use background sync permission https://github.com/WICG/pending-beacon/issues/3#issuecomment-1306174273 to decide whether a fetchLater...

cc @mingyc @fergald @yoavweiss @clelland latest API shape proposal for PendingBeacon

> Deferred fetch body sizes are limited to 64KB per origin. Exceeding this would immediately reject with a QuotaExceeded. Another note about "origin" of a beacon request: there were some...

> > > Deferred fetch body sizes are limited to 64KB per origin. Exceeding this would immediately reject with a QuotaExceeded. > > > > > > Another note about...

>> should be clear from the spec that UA can trigger fetches rather soon if it wants to > I clarified this a bit. Also renamed activationDeadline to activateAfter based...

@noamr A follow up question: should a fetchLater request's [cache mode](https://fetch.spec.whatwg.org/#concept-request-cache-mode) be enforced with `no-store`? Given the purpose of this API and the fact that it does not support response...