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

@noamr pushed 48 commits.

87ee3d464c2cc50b08c9acf6d2915406ba421f6d  Deferred fetching
02bcd3b91aeb52ffc506e8e4886892205cf29e1e  nits
558d57b04d4d44f118f2a16eff10b02c1ff3889e  Update fetch.bs
5f7ee86b7c5478b0b77793f6f99b0dc4799c1381  Move sections around
8a4d53c67e2567f61f82bb4f3ef0ea2ad9f76df2  Rename to fetchLater and backgroundTimeout
77b0325f9c08fa63221567f22fd28759a4b78f67  Fix hierarchy
9948a48f92d6e54ec0074d1ecc1d770499e9e1bd  Restructure to expose a boolean instead of a promise
d1cd39917731e8489884dfc9eee2d1f0d72cb62b  nit
d5d547aab3fe7a3cd4e22956b22cdefbcbbb9ace  or/and
ac946f3903c926ef66fe021b45a6dce82dd29e4e  Remove spurious promise
c873a3a21d11f02a86c954ac88042ea266101595  Rename backgrounded
f4a653c89c867bbd9b87e4ec5820a27418ef9fe0  Throw a few more errors
fa2404291a199514a8d7f2cfbf8060ebada4a141  Always set keepalive
de930830dca478fde97fe41b73886980c7c02b53  Nits
7a8630bc237cd07041c66c44816e5d848b710412  Remove atomics, leave thread safety to implementation
286fbf50359869a4029c6404d572474208a8514f  Throw RangeError when backgroundTimeout is negative
5e0348276158e9165d3e4e5247a229ba90153ddc  Refactor out backgroundTimeout, use activationTimeout
4971f336d1f931777ec9d0a3b088c9f4e825adea  Throw on ReadableStream
d845807918a0f6377c02b04186c708a3147f5250  Fix grammar
8a1f0d4359ea19c931b4d2760529192ed108b941  Several editorial changes, renamed to activationDeadline
1c95c9a34b5c84762a349b69239512d2d0fba43c  Handle CR nits
fdde33c6324abe8ff051228007ff74fb83fc57cb  Remove h2
85528e3560ba28345ad2cbaf477859ce27d163ef  Bring back line break
0bc5f8f79aa786599ebf426f86786881db5b7e58  nit
5be1186005c6bf4d176267fb8b86932427a538e0  nit
f5c37ff9cab2de51a3631b802725cab61036194e  nit
2d9eacfb7aba236b3804174d7563795485b1c244  - Rename activationDeadline to activateAfter
ce7818385a19b49f0e7ede944090eb36ffa2b764  Throw a NotAllowedError for 3p envs
41f4477c5363eb6fb44534e40008fe0032f09ca6  Add top-level + per-sink quota
7d14174d03ce67cd13698d2f085f267290be9ec4  Check permissions policy
141b26278d6c00b50bfdc7a2424895f1f46f3aa7  Narrow scope to Window
da0a8d3262c09dd0cd4b95bf6f6a685c7fb1d98d  Remove existing NotAllowedError
08d46adc9ce8875ace027d6480378c57e2968794  Fix null-body issues
e911490650b34e964515b61c42b94cc3b029c864  Revise based on nits
08b5d5838d9d2a01a8d2560551caad58280737f7  Use correct dfn
dee17592687c72b3735b3dd6e1a55b9e4f0263d2  Remove spurious whitespace
5e61c120681e95729bd95732bde49775812c023a  Use $
b17095558022604ca42fd9e8f104b4d489bb6962  Use new quota algorithm
3c11bc7ce8371a542b8659dc448a5a03cec5e081  nits
05c619695fa9b1ccde792859b95825f2951556e8  Include url+headers in the quota
fd83c42c08aa3a2012b910e2d1974b79bb25d11f  Allow 16kb (UA-specific) even for 3p contexts
097315f51db145d9aa6126aebdb74eb2479e6d59  Update for new quota policy
da60defce1469b35e6bcf7b20a8c40bbe7030ed8  Fix <ol>
d18ae84a4352ddcefc4a93c872abed80a34d6fe9  Only decrement for cross-origin
7d1804d471e46649fc081c66713ff4085d952c8f  Apply permission policy
871a9a869dc6508c6eecd68c9cbcf1a137f3b14f  nits
73bbcac3ab5c2d8d78898f095ee98f118ffbe6b6  refactor
66d4fc1fd3642fce31a459de05391806a77e668e  Refactor quota based on new explainer

-- 
View it on GitHub:
https://github.com/whatwg/fetch/pull/1647/files/22180d694c7c358da0fa7632dbf0c14f5267e58a..66d4fc1fd3642fce31a459de05391806a77e668e
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/pull/1647/before/22180d694c7c358da0fa7632dbf0c14f5267e58a/after/66>

Received on Monday, 28 October 2024 09:37:00 UTC