[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: CSS Scoping in XML Namespaces

• To: "Bullard, Claude L (Len)" <clbullar@i...>
• Subject: Re: CSS Scoping in XML Namespaces
• From: Robin Berjon <robin.berjon@e...>
• Date: Thu, 04 Mar 2004 13:40:18 +0100
• Cc: xml-dev@l...
• In-reply-to: <15725CF6AFE2F34DB8A5B4770B7334EE03F9F41F@h...>
• References: <15725CF6AFE2F34DB8A5B4770B7334EE03F9F41F@h...>
• User-agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4

Bullard, Claude L (Len) wrote:
> Thanks Robert.  Fortunately, I only have to 
> contend with IE for this project.  Closed worlds 
> are scoped worlds by definition. ;-)

Unfortunately, IE is such a poor excuse for a browser that you won't be 
able to do much with CSS. IE only does tagsoup rendering, you're feeding 
caviar to the pigs.

> On the other hand, if the namespace prefixes 
> are different, why the backslash?

Because ':' is a special character in CSS, and has to be escaped if you 
want it to be part of a name selector.

> Considering that CSS is in it's own syntax, 
> and inside a comment, there is a distinctly 
> weird feel to the concept of it having ANY 
> impact on the XML namespaces.  Obviously it 
> does.  Is that informally specified, formally 
> specified, or just another "gotta do it 
> somehow because of legacies" solution?

CSS is *not* in a comment, that's just a broken hack. CSS has the 
ability to match on element names, and naturally this includes the 
ability to match namespaces.

-- 
Robin Berjon

• Follow-Ups:
  • Re: CSS Scoping in XML Namespaces
    • From: Robert Koberg <rob@k...>

• References:
  • RE: CSS Scoping in XML Namespaces
    • From: "Bullard, Claude L (Len)" <clbullar@i...>

• Prev by Date: Re: CSS Scoping in XML Namespaces
• Next by Date: Re: CSS Scoping in XML Namespaces
• Previous by thread: Re: CSS Scoping in XML Namespaces
• Next by thread: Re: CSS Scoping in XML Namespaces
• Index(es):
  • Date
  • Thread