On Feb 12, 2007, at 14:09, Benjamin Hawkes-Lewis wrote:
The practical alternative is to refuse to implement specs that
require legacy-incompatible changes to processing models.
For browsers which have already implemented XHTML1, that seems to
require implementing neither XHTML2-in-the-XHTML1-namespace nor XHTML5
(cf. Anne's reply).
What's there in XHTML5 that would require breaking XHTML1 support (in
practice, predefined class names don't break practice)?
--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/
