- From: Matt Falkenhagen <notifications@github.com>
- Date: Mon, 29 Oct 2018 18:58:53 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 30 October 2018 01:59:16 UTC
https://github.com/whatwg/fetch/issues/679#issuecomment-433827856 makes sense to me to implement. Like Youenn, I'm not quite convinced the specification needs this level of detail, but I'll leave it for you. The updated proposal doesn't seem to include the 30 second timeout. Is it being removed? By the way, don't these restrictions conflict with the current Beacon spec? Beacon is specified using keepalive and [says](https://w3c.github.io/beacon/#privacy-and-security): > [Other than payload size], the sendBeacon() API is not subject to any additional restrictions. The user agent ought not skip or throttle processing of sendBeacon() calls, as they can contain critical application state, events, and analytics data. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/679#issuecomment-434144125
Received on Tuesday, 30 October 2018 01:59:16 UTC