22943 2013-08-13 20:59:13 +0000 Consider using iso-8859-1 as a canonical encoding name for windows-1252 2013-12-16 17:15:56 +0000 1 1 1 Unclassified WHATWG Encoding unspecified All All RESOLVED WONTFIX P2 normal Unsorted 1 VYV03354 annevk mike sideshowbarker+encodingspec oldest_to_newest 92011 0 VYV03354 2013-08-13 20:59:13 +0000 Both IE 11 and Chrome use iso-8859-1 as a canonical. I bet IE will not change because Shawn Steele resists any changes to legacy encodings. Opera Presto was the only browser using windows-1252 until Gecko changed the canonical name. Now Presto is dead. Gecko will turn back as soon as the spec is updated. 92035 1 annevk 2013-08-14 09:49:32 +0000 How is this different from bug 15340? That instead of treating them distinct we still treat them as one but change the canonical name? I thought the issue in other browsers is that they still treat them somewhat distinctly, even though encoding/decoding is identical.