- From: <bugzilla@jessica.w3.org>
- Date: Sun, 24 Jul 2011 20:41:03 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12561 --- Comment #26 from Aryeh Gregor <Simetrical+w3cbug@gmail.com> 2011-07-24 20:41:03 UTC --- (In reply to comment #25) > Sorry for the noise, but I also meant to say that the problem with > compatibility applies to HTML4/HTML5 as well as XHTML/HTML5 (as already > mentioned above). The current spec makes it impossible to generate a form that > targets the same URL, and have that form be both valid HTML4 and valid HTML5. Again, allowing the same markup to be both valid HTML5 and valid something-else is not a design goal here. > Section 2.5 of the HTML design goals - > http://dev.w3.org/html5/html-design-principles/#compatibility - says this: > > "implementations should be able to add new features to existing code, rather > than having to develop whole separate modes." > > It seems to violate the design goal of 'evolution not revolution' to add > something to the spec that requires a doctype switch to specify between HTML4 > and HTML5, when all I want to do is use a subset of the capabilities provided > by both HTML4 and HTML5. That design goal says that browsers have to be able to process all pages the same. They do: they process all pages as HTML5, without regard for other standards. The question at hand is whether authors can write pages that are both valid HTML5 and valid something-else. That's not a design goal. If you only want to use a subset of features, just pick one or the other. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Sunday, 24 July 2011 20:41:04 UTC