- From: Nick <halbtaxabo-temp4@yahoo.com>
- Date: Fri, 10 Mar 2017 08:20:03 +0000 (UTC)
- To: "Michael[tm] Smith" <mike@w3.org>, Nick <halbtaxabo-temp4@yahoo.com>
- Cc: "www-validator@w3.org" <www-validator@w3.org>
From: Michael[tm] Smith <mike@w3.org>To: Nick <halbtaxabo-temp4@yahoo.com> >Nick <halbtaxabo-temp4@yahoo.com>, 2017-03-09 22:31 +0000: >> Archived-At: <http://www.w3.org/mid/204362919.2534675.1489098696666@mail..yahoo.com> >The HTML checker uses the same HTML parser that Firefox uses. So I’d expect >that if you take whatever document is causing you to see that “Proceeding >using windows-1252” message, you might find you get the same behavior in >Firefox as you’re seeing from the checker. And in other browsers as well. Google Chrome (56.0) treats it correctly, i.e. as UTF-8. That's the most important case because Google Chrome has about three times as many users as the next-most-popular browser according to netmarketshare.com Firefox renders it wrongly (using windows-1252) which is to be expected if it uses the same HTML parser as the checker. Nick
Received on Friday, 10 March 2017 10:15:19 UTC