2 ms·
This feature should be replicable in a plugin: it just needs to inject an appropriate Content-Type header into a response (similarly to how user-agent extension
by nneonneo 5y ago
This feature should be replicable in a plugin: it just needs to inject an appropriate Content-Type header into a response (similarly to how user-agent extensions override the User-Agent headers in requests). A fancier plugin could even remember overrides per domain/path/site, making it even more useful than the original menu.
To be clear, no such extension appears to exist yet, but it should be a matter of time before one is created.
- nneonneo 5y ago...and because it sounded easy, I went ahead and just did it: https://addons.mozilla.org/en-US/firefox/addon/override-text-encoding/ https://addons.mozilla.org/en-US/firefox/addon/override-text... The hardest part was doing all the UI bits, because I had to learn how to make a UI that would look halfway decent in the popup menu. But hey, it works!
- hsivonen 5y agoThe reason why this seems easy while the built-in feature got in the way of other changes is that the built-in feature dealt with more issues. For example: https://hsivonen.com/test/moz/never-show-user-supplied-content-as-utf-16.htm16le https://hsivonen.com/test/moz/never-show-user-supplied-conte...