9127 2010-02-23 13:43:25 +0000 As others have pointed out: why have so many willfull violations to support legacy content if there is *no legacy HTML5 content to support?* 2010-10-04 14:47:24 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED WORKSFORME http://www.whatwg.org/specs/web-apps/current-work/#parsing P3 normal LC 1 contributor ian gexicus321 hober0 ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 32583 0 contributor 2010-02-23 13:43:25 +0000 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 32589 1 gexicus321 2010-02-23 17:49:22 +0000 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. 32590 2 hober0 2010-02-23 17:54:37 +0000 Effectively the entire Web is made of legacy *HTML* content, which HTML5 defines processing for. Those willful violations are necessary for this legacy content. 32606 3 hober0 2010-02-24 02:43:59 +0000 *** Bug 9134 has been marked as a duplicate of this bug. ***