- From: Robin Berjon <robin@berjon.com>
- Date: Tue, 9 Dec 2008 09:57:01 +0100
- To: Lachlan Hunt <lachlan.hunt@lachy.id.au>
- Cc: "public-webapps@w3.org" <public-webapps@w3.org>, www-svg <www-svg@w3.org>
On Dec 9, 2008, at 01:06 , Lachlan Hunt wrote:
> Robin Berjon wrote:
>> On Dec 8, 2008, at 17:26 , Lachlan Hunt wrote:
>>> Similar functionality was previously requested and rejected for
>>> the xml and xmlns prefixes, and I see no reason to treat the xhtml
>>> and svg prefixes any differently.
>>>
>>> http://lists.w3.org/Archives/Public/public-webapi/2008Feb/0062.html
>> That's a shame, they should be defined for a DOM that supports XML
>> features, especially the xml namespace.
>
> Although the xml and xmlns prefixes are predefined for use in XML,
> neither the Selectors spec, nor the CSS Namespace Module predefine
> them for use with Selectors in CSS. There is no reason why this
> should be any different for Selectors used in this API. If you
> still disagree, then I suggest you take up the issue with the CSS
> WG, as it would be more appropriate to address the issue in either
> Selectors or the CSS Namespace Module, if at all.
Yes, it would be right to fix that there too, but I've long ago lost
any hope of doing anything about the CSS WG's irrational-bordering-on-
frothing hatred for all things even vaguely related to XML. I'd rather
that the WebApps WG made up its own mind on these issues rather than
hide behind someone else's bigotry.
--
Robin Berjon - http://berjon.com/
Feel like hiring me? Go to http://robineko.com/
Received on Tuesday, 9 December 2008 08:57:38 UTC