-
Notifications
You must be signed in to change notification settings - Fork 343
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Response.prototype.type property #3590
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
cebf528
to
ac4b5d8
Compare
ac4b5d8
to
307d264
Compare
This comment was marked as outdated.
This comment was marked as outdated.
307d264
to
ca052c4
Compare
This comment was marked as outdated.
This comment was marked as outdated.
The generated output of |
WinterTC recently agreed that conformant implementations should, at the very least, support the `'default'` value for `Response.prototype.type` property and, if the runtime implements `Response.error()`, the `'error'` value -- even if the implementation otherwise does not implement CORS.
75653f2
to
672a70c
Compare
@irvinebroque ... for the changelog entry once this and #3592 are merged and are released: We are adding the |
WinterTC recently agreed that conformant implementations should, at the very least, support the
'default'
value forResponse.prototype.type
property and, if the runtime implementsResponse.error()
, the'error'
value -- even if the implementation otherwise does not implement CORS.