Comment 11 for bug 39136

(In reply to comment #1)
> It would make more sense, imo, to implement "view in browser as text" as a way
> to handle an arbitrary MIME type and then let users set it as needed.

I'd certainly like to see that option. I had assumed such a thing would already
exist, and spent quite a while looking for it.

An alternative approach would be "treat this MIME type exactly as you would this
other type", which would be (marginally) more generally useful.

It would probably be unreasonable to attempt to refine it further, to restrict
such mappings to particular domains to cope with (say) a particular JPEG being
presented as an application/octet-stream.

Hugo