Closed Bug 618763 Opened 14 years ago Closed 14 years ago

HTML5 Charset Tag not Followed

Categories

(Core :: DOM: HTML Parser, defect)

Product:
Core
Component:
DOM: HTML Parser
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 584285

People

(Reporter: trappmanrhett, Unassigned)

References

(
URL
)

Details

(Keywords: html5) 

User-Agent:       Mozilla/5.0 (Windows NT 6.0; rv:2.0b8pre) Gecko/20101119 Firefox/4.0b8pre
Build Identifier: 

The new Character set tag, does not modify the way Firefox renders a webpage, nor does it show up as a meta tag on "Page Info".

HTML5 DTD:
<!DOCTYPE HTML>

HTML5 Charset Tag:
<meta charset="UTF-8">

Reproducible: Always
Keywords: html5
My blog site is an example (see above link)
(In reply to comment #0)
> The new Character set tag, does not modify the way Firefox renders a webpage,

Do you have a test case that shows this clearly?

> nor does it show up as a meta tag on "Page Info".

That's bug 584285.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
(In reply to comment #2)

Just for example...

I put <meta charset="UTF-32"> on my blog at: 
http://chaparralweb.com/rhett/project/news.php

Refreshed the page and, the page info shows:
Encoding: ISO-8859-1, Should Be: "UTF-32" or whatever the meta tag specifies.

> (In reply to comment #0)
> > The new Character set tag, does not modify the way Firefox renders a webpage,
> 
> Do you have a test case that shows this clearly?
> 
> > nor does it show up as a meta tag on "Page Info".
> 
> That's bug 584285.
> 
> *** This bug has been marked as a duplicate of bug 584285 ***
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
UTF-32 is not a supported encoding name. The HTML5 parser deliberately blacklists UTF-32 so that UTF-32 is treated as unsupported. See http://www.whatwg.org/specs/web-apps/current-work/#character-encodings-0

Furthermore, it's invalid to use <meta charset> to declare an encoding that's not a rough ASCII superset. For example, <meta charset="UTF-16"> is invalid.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.