Bug 32536 – Some Browser-hosted SunSpider files are not valid HTML5

• Status: RESOLVED
• Resolution: FIXED
• Component: Tools / Tests

[Maciej Stachowiak]

Some Browser-hosted SunSpider files are not valid HTML5.

[Maciej Stachowiak]

Created attachment 44835 [details]
Patch

[WebKit Review Bot]

style-queue ran check-webkit-style on attachment 44835 [details] without any errors.

[Darin Adler]

Comment on attachment 44835 [details]
Patch

> +<meta charset=utf8>

Wow, I have never seen that syntax before. I always did it like this:

    <meta http-equiv="content-type" content="text/html; charset=utf-8">

I guess a new HTML5 thing. Does WebKit respect that syntax?

rs=me

[Maciej Stachowiak]

(In reply to comment #3)
> (From update of attachment 44835 [details])
> > +<meta charset=utf8>
> 
> Wow, I have never seen that syntax before. I always did it like this:
> 
>     <meta http-equiv="content-type" content="text/html; charset=utf-8">
> 
> I guess a new HTML5 thing.

Yep, it's new in HTML5.

> Does WebKit respect that syntax?

Yes. All browsers support it accidentally, because sniffing for a declared charset needs to be extremely lax. In particular sometimes people drop the quotes and write this:

<meta http-equiv=content-type content=text/html; charset=utf-8>

Thus you have to support charset=utf-8 by itself, and since browsers support it already, HTML5 wisely decided to make the shorter version conforming.

[Maciej Stachowiak]

http://trac.webkit.org/changeset/52139