| Summary: | Some Browser-hosted SunSpider files are not valid HTML5 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Maciej Stachowiak <mjs> | ||||
| Component: | Tools / Tests | Assignee: | Maciej Stachowiak <mjs> | ||||
| Status: | RESOLVED FIXED | ||||||
| Severity: | Normal | CC: | webkit.review.bot | ||||
| Priority: | P2 | ||||||
| Version: | 528+ (Nightly build) | ||||||
| Hardware: | PC | ||||||
| OS: | OS X 10.5 | ||||||
| Attachments: |
|
||||||
|
Description
Maciej Stachowiak
2009-12-14 19:36:41 PST
Created attachment 44835 [details]
Patch
style-queue ran check-webkit-style on attachment 44835 [details] without any errors.
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 (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. |