- From: Laurens Holst <lholst@students.cs.uu.nl>
- Date: Mon, 19 Mar 2007 05:07:03 +0900
- To: Robert Brodrecht <w3c@robertdot.org>
- CC: dboudreau@webconforme.com, public-html@w3.org
Received on Sunday, 18 March 2007 20:07:45 UTC
Robert Brodrecht schreef: > So, yes, XHTML 2 threw out backward compatibility. I think this is a common mistake, and given the charter of XHTML2 maybe not a strange one. However, this does not reflect the reality where XHTML2 contained elements like <h1>...<h6>, <a>, <img>, and also re-uses the XHTML1 namespace. The existence of these elements and this namespace can only be explained as being for backwards compatibility reasons, so that XHTML2 documents can be written that will work in an XHTML1 environment (like Mozilla, Opera, Safari). I think the main thing you can fault the XHTML2 working group here is that they never formalised this in their charter, causing a lot of confusion over the existence of the aforementioned elements, etc. ~Grauw -- Ushiko-san! Kimi wa doushite, Ushiko-san nan da!! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Laurens Holst, student, university of Utrecht, the Netherlands. Website: www.grauw.nl. Backbase employee; www.backbase.com.
Received on Sunday, 18 March 2007 20:07:45 UTC