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 7135 - fix HTML5 facet so that it doesn't incorrectly warn "No Character Encoding Found"
Summary: fix HTML5 facet so that it doesn't incorrectly warn "No Character Encoding Fo...
Status: RESOLVED DUPLICATE of bug 5992
Alias: None
Product: HTML Checker
Classification: Unclassified
Component: General (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: qa-dev tracking
URL: http://validator.w3.org/check?uri=htt...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-24 00:39 UTC by Michael[tm] Smith
Modified: 2015-08-23 07:07 UTC (History)
0 users

See Also:

Attachments
patch with proposed changes (1.26 KB, patch)
2009-07-24 00:39 UTC, Michael[tm] Smith 		Details

Description Michael[tm] Smith 2009-07-24 00:39:46 UTC 
Created attachment 732 [details]
patch with proposed changes

see http://lists.w3.org/Archives/Public/www-validator/2009Jul/0034.html
and http://www.annmanor.ca/news.shtml

that page contains the element <meta charset="utf-8" /> , which is a conformant character-encoding declaration in HTML5. So the HTML5 facet should not emit a  "No Character Encoding Found" warning.

for a proposed fix, see the attached patch
Comment 1 Ville Skyttä 2009-09-21 18:56:01 UTC 
Unfortunately the patch is not correct for two reasons:

1) It would only affect scenarios where a charset override ("hard" or "fallback") is present, and

2) $File->{DOCTYPE} will always be undefined at that point because no attempt to parse the doctype has been made yet.

We already have bug 5992 tracking this issue, so I'm marking this one as its duplicate.

*** This bug has been marked as a duplicate of bug 5992 ***