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 22819 - The pre-pass algorithm for extracting an encoding from meta should also be used for parsing charset attribute.
Summary: The pre-pass algorithm for extracting an encoding from meta should also be us...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-27 22:50 UTC by Alistair Potts
Modified: 2013-07-27 22:58 UTC (History)
3 users (show)

See Also:

Attachments

Description Alistair Potts 2013-07-27 22:50:36 UTC 
8.2.5.4.4 The "in head" insertion mode -

When the parser comes across a charset declaration, it makes sense for it to use the same algorithm for extracting the charset as defined in the "algorithm for extracting a character encoding from a meta element".

It does this for the http-equiv style charset declaration, but currently for 'charset=foo' style declaration it just says:

"If the element has a charset attribute, and getting an encoding from its value results in a supported ASCII-compatible character encoding or a UTF-16 encoding..."

Specifically 'getting an encoding from its value' should be be unambiguous, as with the http-equiv wording, because the algorithm is more robust. If it's not used, and just the literal value of the attribute extracted, then there's the possibility of a needless reparse and an incorrect inference from the charset value.

Thanks.
Comment 1 Alistair Potts 2013-07-27 22:58:36 UTC 
Actually, having re-read it I withdraw this bug.