-
Notifications
You must be signed in to change notification settings - Fork 44
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
Remove unknown/unknown and application/unknown #91
base: main
Are you sure you want to change the base?
Conversation
Firefox has had no need for these. It seems less weird behavior is better. See #30 for context.
(Note that there is much more cleanup possible here now that "extract a MIME type" is almost a thing, but it seems worthwhile doing that separately from this decision.) cc @MattMenke2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Editorially LGTM. It would be good to check with other implementers, maybe the CORB folks?
While I own the MIME sniffer, what the renderer actually does with the information is largely a black box to me. So I'm fine with removing them, but have no clue about the potential fallout. |
(No separate issue, so commenting here.) Chromium treats Firefox defines But also treats |
With a payload of
|
Support for |
Firefox has had no need for these. It seems less weird behavior is better.
See #30 for context.
Preview | Diff