Re: [whatwg/fetch] Deferred fetching (PR #1647)

@noamr pushed 41 commits.

b8699dc87fb52c802bf88943860d33186d882c5c  Deferred fetching
6f8788db158aeae5da4124a905791473e64f6014  nits
2c5a378d5ae4c8b88871e404922d48409094cddd  Update fetch.bs
fad605876295eca70aaf78025a92ca90b9769127  Move sections around
6ba4a6cab8e55d98dcb72a47347f27818078de38  Rename to fetchLater and backgroundTimeout
e0e3edb952073581e9ed64ed8ab1090982791dd6  Fix hierarchy
b81c12618aa920c25d2bdfc691c52bdb5c540100  Restructure to expose a boolean instead of a promise
19cef3957c56a403f7f01bd22100e7d591ca5239  nit
d7c9ba2148b9e8351133f720f1ab9a7254bf6cc5  or/and
3f3fe9b9d68f864ffeb3a7854fd491a1d12b535d  Remove spurious promise
ade759d3a22a004d2b3639643d2c5aab6edd2cf5  Rename backgrounded
a25b200e13593f4022af96fa968749cd3268f060  Throw a few more errors
f2e965cbff1e00fef7c36e20fbcac24e281aee92  Always set keepalive
a4dcd5e505af7a54b49a51f21d9d2839c011973c  Nits
dca8fb401b05de594a6e1a94eb0b8f3b6e1637de  Remove atomics, leave thread safety to implementation
119091ebd849b1a900be0a5fbb83212cf9b25163  Throw RangeError when backgroundTimeout is negative
cecdcc2ce60a881f3c36a88033fc7cfc5b655799  Refactor out backgroundTimeout, use activationTimeout
614427b415495eba9a4b9bf7ed16681b86b08b9a  Throw on ReadableStream
e859f1044ff52a8dc2b180fb6559756ef7a32caf  Fix grammar
47c68c59f514f60f761c9f9efabdb60cff82f1ff  Several editorial changes, renamed to activationDeadline
c281ebd989f85ece1d09ef0352b294424dd77cac  Handle CR nits
a29d2a8b64f3172352035151eed2d3a9f37a6c59  Remove h2
8450509a0357cdcba4c9ee3dbfef394ee7f9ba43  Bring back line break
984b40d0c9cd02cecd8e3280ed507c4d95a2755c  nit
372a04b47173258da98f33c57b3d5dfd0a47eb9f  nit
5bbae3d2e7325d17f84f2b01802b851250a0ae12  nit
ddb109e2ae4af22cd88d762162af8950edbe4bbf  - Rename activationDeadline to activateAfter
86d89545ee49a6843f90069df79c19e54743b3ea  Throw a NotAllowedError for 3p envs
d608571737c170e18afa26af38c192e37cdc3f06  Add top-level + per-sink quota
871044f47c40459699fed0e28de95145afc32e42  Check permissions policy
859ac792821967b6fd4c568121500af0ad7ee37f  Narrow scope to Window
f99d1dd7a4100439ce68ede86d33766ed1c7ca76  Remove existing NotAllowedError
9761a60b488f401507524795d1c5a52fc1472a1a  Fix null-body issues
123ac9f84389bf9634392f98a0eaacfde86a8ddd  Revise based on nits
f67f4dbaab77d9a148a3e19039f49de207a57af5  Use correct dfn
22aac8bfe6a23162f1f7ec0eb4774e4d0b9fea6f  Remove spurious whitespace
a4f971a05fc468f03f533d8393bf8bc5b7f9cd66  Use $
5ddc3c3b49c018e8b49c2a5ef4c8b9a8304a5190  Use new quota algorithm
4879ba18e61090cb0556eefdba8a7f2f3a6b6fc0  nits
6e429cea98aa63656c5767ec50689d9cc4eac2a8  Include url+headers in the quota
19d3bd23526a49739f6d2388d9bf043140fd9ff9  Allow 16kb (UA-specific) even for 3p contexts

-- 
View it on GitHub:
https://github.com/whatwg/fetch/pull/1647/files/de4d48aabc3239cdb352d21f94e4a1227aced17e..19d3bd23526a49739f6d2388d9bf043140fd9ff9
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/pull/1647/before/de4d48aabc3239cdb352d21f94e4a1227aced17e/after/19>

Received on Thursday, 5 September 2024 09:35:41 UTC