- From: Ennals, Robert <robert.ennals@intel.com>
- Date: Mon, 22 Mar 2010 19:25:07 +0000
- To: Philip Taylor <pjt47@cam.ac.uk>
- CC: "public-html@w3.org WG" <public-html@w3.org>, "Carr, Wayne" <wayne.carr@intel.com>
Do you know how common that is on the web? If it is a problem then we could easily work round it by requiring that the root element have an @extension attribute set to true in order for the xmlns to be interpreted, or something similar. -Rob > -----Original Message----- > From: Philip Taylor [mailto:pjt47@cam.ac.uk] > Sent: Monday, March 22, 2010 11:59 AM > To: Ennals, Robert > Cc: public-html@w3.org WG; Carr, Wayne > Subject: Re: Possible Conservative Proposal : no prefixes, but allow > xmlns on a root element > > Ennals, Robert wrote: > > [...] > > * If the browser encounters an unknown element with a default > > namespace declaration, then it should apply that namespace to all > > descendent nodes. > > This looks like it will break content. E.g.: > > http://www.zapster.it/biografia/Suzy-Kendall/filmografia > > <div id="myGallery"> > > <playlist version="1" xmlns="http://xspf.org/ns/0/"> > <trackList> > > <div class="imageElement"> > <p>clicca per vedere tutti i poster</p> > <a href="..." title="Ingrandisci" class="open"></a> > <img src="..." class="full" alt="Suzy Kendall"/> > <img src="..." class="thumbnail" alt="Suzy Kendall"/> > </div> > ... > > If the <playlist xmlns> causes the descendants to have the > http://xspf.org/ns/0/ namespace instead of the HTML namespace, then > they > will no longer be rendered correctly as HTML links and images. > > -- > Philip Taylor > pjt47@cam.ac.uk
Received on Monday, 22 March 2010 19:25:51 UTC