This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 22943 - Consider using iso-8859-1 as a canonical encoding name for windows-1252
Summary: Consider using iso-8859-1 as a canonical encoding name for windows-1252
Status: RESOLVED WONTFIX
Alias: None
Product: WHATWG
Classification: Unclassified
Component: Encoding (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: Unsorted
Assignee: Anne
QA Contact: sideshowbarker+encodingspec
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-13 20:59 UTC by Masatoshi Kimura
Modified: 2013-12-16 17:15 UTC (History)
1 user (show)

See Also:

Attachments

Description Masatoshi Kimura 2013-08-13 20:59:13 UTC 
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.
Comment 1 Anne 2013-08-14 09:49:32 UTC 
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.