- From: Lukasz Anforowicz <notifications@github.com>
- Date: Mon, 16 May 2022 09:45:27 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 16 May 2022 16:45:39 UTC
I support removing CORB from the spec and WPT. I hope that existing CORB WPT coverage can be refactored to support/cover ORB instead: 1. Expecting blocked responses to hit a network error (instead of just having an empty response body). FWIW I've pinged https://crbug.com/827633 - one action item for Chrome might be to quantify the perceived risk of blocking-by-network-error VS blocking-by-injecting-empty-response-body (and if that risk is small, then Chrome should just switch to blocking-by-network-error). 2. Covering additional scenarios where CORB and ORB differ in their allow-vs-block decision. (It seems that most of the CORB-specific WPT testcases cover scenarios where ORB would behave in a similar way wrt allow-vs-block decision.) -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/pull/1441#issuecomment-1127899462 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/pull/1441/c1127899462@github.com>
Received on Monday, 16 May 2022 16:45:39 UTC