Re: [whatwg/fetch] CORB++: CSS (#964)

In Gecko, the behavior is "Blocked if there is a content-type header result of parsing the content-type header produces a nonempty string".

I suspect based on code inspection, but have not tested, that something like:
```
Content-Type: ; charset="utf-8"
```
would get treated as "empty string" in Gecko, for example.  And not sure about this one:
```
Content-Type: text/css, ; charset="utf-8"
```

If we want to know the actual behavior across browsers, we'll need to write some testcases and maybe do some code-sleuthing.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/964#issuecomment-595248149