Author r.david.murray
Recipients Hunanyan, Matt.Basta, cpalmer, eric.araujo, ezio.melotti, fantoozler, fdrake, friday, georg.brandl, gsf, momat, orsenthil, r.david.murray, yotam
Date 2011-07-27.19:13:08
SpamBayes Score 0.000550358
Marked as misclassified No
Message-id <1311793989.53.0.421914604186.issue670664@psf.upfronthosting.co.za>
In-reply-to
Content
I thought HTLM4 conformance was documented somewhere, but I could be wrong.

HTML5, from what I understand (I haven't read the spec), is explicitly or implicitly following "what browsers really do" exactly because nobody conformed to HTML4, so arguing that "a later spec changed the rules" isn't really relevant in this case :)

We made the change the way we did (strict option) out of backward compatibility concerns, so I still think this topic needs to be discussed on python-dev.  I think the argument that python should handle what most browsers handle is a strong one (I myself would have been in favor of just making this stuff work, absent backward compatibility concerns).  The question in my mind is what's the best way to get there from here?
History
Date User Action Args
2011-07-27 19:13:09r.david.murraysetrecipients: + r.david.murray, fdrake, georg.brandl, yotam, orsenthil, fantoozler, gsf, cpalmer, ezio.melotti, eric.araujo, momat, Hunanyan, friday, Matt.Basta
2011-07-27 19:13:09r.david.murraysetmessageid: <1311793989.53.0.421914604186.issue670664@psf.upfronthosting.co.za>
2011-07-27 19:13:08r.david.murraylinkissue670664 messages
2011-07-27 19:13:08r.david.murraycreate