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 9127 - As others have pointed out: why have so many willfull violations to support legacy content if there is *no legacy HTML5 content to support?*
Summary: As others have pointed out: why have so many willfull violations to support l...
Status: RESOLVED WORKSFORME
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
: 9134 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-02-23 13:43 UTC by contributor
Modified: 2010-10-04 14:47 UTC (History)
6 users (show)

See Also:

Attachments

Description contributor 2010-02-23 13:43:25 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#parsing

Comment:
As others have pointed out: why have so many willfull violations to support
legacy content if there is *no legacy HTML5 content to support?*

Posted from: 71.224.28.44
Comment 1 Teraunce 2010-02-23 17:49:22 UTC 
That spec just seems shameful. if it really wants to support legacy encodings, let it, but don't mandate changing the encoding of the message.
Comment 2 Edward O'Connor 2010-02-23 17:54:37 UTC 
Effectively the entire Web is made of legacy *HTML* content, which HTML5 defines processing for. Those willful violations are necessary for this legacy content.
Comment 3 Edward O'Connor 2010-02-24 02:43:59 UTC 
*** Bug 9134 has been marked as a duplicate of this bug. ***