W3C home > Mailing lists > Public > www-international@w3.org > January to March 2014

[Bug 25136] You have dropped support for encoding cp862!!

From: <bugzilla@jessica.w3.org>
Date: Thu, 27 Mar 2014 15:27:18 +0000
To: www-international@w3.org
Message-ID: <bug-25136-4285-IFIbdHK7la@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25136

--- Comment #24 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> ---
(In reply to Martin Dürst from comment #23)
> (In reply to Leif Halvard Silli from comment #21)
> 
> > If you want to promote Firefox, then there it has a user style sheet
> > manager:  https://addons.mozilla.org/en-US/firefox/addon/user-style-manager/
> 
> A user stylesheet isn't needed. If you have control over your server, you
> can make it add a HTTP link header. Anne can give the details.

Cool. But my suspicion is that Queency have in mind parsing of files via the
file URL protocol.

> Also, I don't think it's necessary for the file name to end in .html as long
> as it's served as Content-Type: text/html.

There is also a "Force Content-Type" add-on for Firefox, which works fine. (Not
sure it works for file: URLs, though.)

<https://addons.mozilla.org/en-US/firefox/addon/force-content-type/>

However, as it turns out, in Firefox, CSS applies to text/plain as well. So it
might not be necessary to fiddle with the Content-Type - one can just apply the
CSS - via User-Style-Manager or via HTTP link header.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Thursday, 27 March 2014 15:27:19 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 21 September 2016 22:37:36 UTC