Remove trailer support #979
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
As noted in #772 (comment) the current way it is exposed subsets what HTTP supports and therefore does not feel like a good starting point. Both for the internal and public API. Additionally, the public-facing API has not seen interest from implementers, at least for the past year and a half.
annevk
added a commit
to web-platform-tests/wpt
that referenced
this pull request
Dec 11, 2019
This was referenced Dec 11, 2019
|
lgtm |
|
Thanks @ricea, appreciate it! |
moz-v2v-gh
pushed a commit
to mozilla/gecko-dev
that referenced
this pull request
Dec 19, 2019
…iler, a=testonly Automatic update from web-platform-tests Fetch: remove support for Response's trailer See whatwg/fetch#979. -- wpt-commits: 1db21a0158e71f849e151c4111a804ed15df855e wpt-pr: 20720
gecko-dev-updater
pushed a commit
to marco-c/gecko-dev-wordified
that referenced
this pull request
Dec 20, 2019
…iler, a=testonly Automatic update from web-platform-tests Fetch: remove support for Response's trailer See whatwg/fetch#979. -- wpt-commits: 1db21a0158e71f849e151c4111a804ed15df855e wpt-pr: 20720 UltraBlame original commit: e48da00946f8f65a57afe14904884a094ff86d60
gecko-dev-updater
pushed a commit
to marco-c/gecko-dev-comments-removed
that referenced
this pull request
Dec 20, 2019
…iler, a=testonly Automatic update from web-platform-tests Fetch: remove support for Response's trailer See whatwg/fetch#979. -- wpt-commits: 1db21a0158e71f849e151c4111a804ed15df855e wpt-pr: 20720 UltraBlame original commit: e48da00946f8f65a57afe14904884a094ff86d60
gecko-dev-updater
pushed a commit
to marco-c/gecko-dev-wordified-and-comments-removed
that referenced
this pull request
Dec 20, 2019
…iler, a=testonly Automatic update from web-platform-tests Fetch: remove support for Response's trailer See whatwg/fetch#979. -- wpt-commits: 1db21a0158e71f849e151c4111a804ed15df855e wpt-pr: 20720 UltraBlame original commit: e48da00946f8f65a57afe14904884a094ff86d60
lissyx
pushed a commit
to lissyx/mozilla-central
that referenced
this pull request
Dec 20, 2019
…iler, a=testonly Automatic update from web-platform-tests Fetch: remove support for Response's trailer See whatwg/fetch#979. -- wpt-commits: 1db21a0158e71f849e151c4111a804ed15df855e wpt-pr: 20720
foolip
added a commit
to foolip/browser-compat-data
that referenced
this pull request
Aug 20, 2020
It was added in mdn#1400 because it was then in https://fetch.spec.whatwg.org/. It was removed from the spec in whatwg/fetch#979 and apparently never implemented. There's no MDN page for this so nothing more to clean up.
Elchi3
pushed a commit
to mdn/browser-compat-data
that referenced
this pull request
Aug 20, 2020
It was added in #1400 because it was then in https://fetch.spec.whatwg.org/. It was removed from the spec in whatwg/fetch#979 and apparently never implemented. There's no MDN page for this so nothing more to clean up.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As noted in #772 (comment) the current way it is exposed subsets what HTTP supports and therefore does not feel like a good starting point. Both for the internal and public API.
Additionally, the public-facing API has not seen interest from implementers, at least for the past year and a half.
Preview | Diff