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

RE: CSS Scoping in XML Namespaces

• To: 'Robert Koberg' <rob@k...>
• Subject: RE: CSS Scoping in XML Namespaces
• From: "Bullard, Claude L (Len)" <clbullar@i...>
• Date: Wed, 3 Mar 2004 16:44:47 -0600
• Cc: xml-dev@l...

Thanks Robert.  Fortunately, I only have to 
contend with IE for this project.  Closed worlds 
are scoped worlds by definition. ;-)

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

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?

len

From: Robert Koberg [mailto:rob@k...]

Hi,

just escape the backslash. I have only used this in IE, so test in other 
browsers...

<style>

myns1\:myelement {
color:purple;
}

myns2\:myelement {
color:#fff;
}

</style>


Bullard, Claude L (Len) wrote:

> The subject says it.   What are the rules (if any) 
> for the scoping of CSS declarations with regards 
> to XML documents with multiple namespaces?  For 
> example, SVG/VML etc., within X(HTML)?

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

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