- From: Anne van Kesteren <notifications@github.com>
- Date: Fri, 29 Sep 2023 08:12:48 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 29 September 2023 15:12:53 UTC
### What is the issue with the Fetch Standard? 1. These are not should requirements. They are musts. 2. They return non-Infra values. 3. The usage of headings and questions marks seems to lead to some bugs, such as not being able to navigate to the caller of [https://fetch.spec.whatwg.org/#should-response-to-request-be-blocked-due-to-mime-type?](https://fetch.spec.whatwg.org/#should-response-to-request-be-blocked-due-to-mime-type?) Ideally we'd change Fetch, CSP, and Mixed Content around the same time so we can have this continue to be somewhat consistent. Maybe something like: > To determine if a response _response_ to a request _request_ **is blocked due to its MIME type**: > 1. ... > 2. Return true. @antosart @carlosjoan91 thoughts? -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/1714 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/issues/1714@github.com>
Received on Friday, 29 September 2023 15:12:53 UTC