- From: Sam Ruby <rubys@us.ibm.com>
- Date: Thu, 06 Dec 2007 01:58:02 -0500
- To: Ian Hickson <ian@hixie.ch>
- CC: Henri Sivonen <hsivonen@iki.fi>, public-html <public-html@w3.org>
Ian Hickson wrote: > On Wed, 5 Dec 2007, Sam Ruby wrote: >> Henri Sivonen wrote: >>> I identified four classes of errors: >>> 1) meta charset in XHTML >> Why specifying a charset that matches the encoding is flagged as an >> error is probably something that should be discussed another day. I >> happen to believe that people will author content intended to be used by >> multiple user agents which are at various levels of spec conformance. > > That's actually an XML issue -- XML says the encoding should be in the XML > declaration, so HTML tries to not step on its toes and says that the > charset declaration shouldn't be included in the markup. (The spec has to > say that the UA must ignore that line anyway, so it's not clear that > there's any benefit to including it.) If the declaration clashed, I could see the value in an error message, but as I said, this can be discussed another day. >>> 2) wbr >> I don't understand the error message that is produced, nor can I figure >> out what the problem is. Can you elaborate? > > <wbr> isn't valid HTML (and never has been). Should it be? :-) i.e., does it serve a useful purpose? Does it cause any backwards compatibility problems? - Sam Ruby
Received on Thursday, 6 December 2007 06:58:29 UTC