- From: Henri Sivonen <notifications@github.com>
- Date: Thu, 30 Apr 2020 00:11:20 -0700
- To: whatwg/encoding <encoding@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/encoding/pull/209/review/403256453@github.com>
@hsivonen commented on this pull request. > @@ -612,6 +612,17 @@ prescribes, as that is necessary to be compatible with deployed content. <a>labels</a> are also available as non-normative <a href=encodings.json>encodings.json</a> resource. +<p class=note>The set of supported <a for=/>encodings</a> is primarily based on the intersection +of the sets supported by major browser engines when the development of this standard started and +removing encodings that were rarely used legitimately but that could be used in attacks. +The inclusion of some encodings is questionable in the light of anecdotal evidence of the level +of use by existing Web content. That is, while they have been broadly supported by browsers, +it is unclear if they are broadly used by Web content. However, an effort has not been made to +eagerly remove single-byte encodings that were broadly supported by browsers or are part of the +ISO 8859 series. In particular, the necessity of the inclusion of <a>IBM866</a>, <a>macintosh</a>, +<a>x-mac-cyrillic</a>, <a>ISO-8859-3</a>, <a>ISO-8859-10</a>, <a>ISO-8859-14</a>, +<a>ISO-8859-14</a>, and <a>ISO-8859-16</a> is doubtful for the purpose of supporting existing Fixed. Thanks. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/encoding/pull/209#discussion_r417800617
Received on Thursday, 30 April 2020 07:11:32 UTC