[s/b "might?".]
> In the sense of clause 5.4 of CSS2: "A type selector matches the
> name of a document language element type". The name, not the
> UniversalName.
Yeah, but when that was written, the colon wasn't a legal name
character. (Well, strictly, it was legal but reserved.) Trying to
argue that namespaces are broken, because something that doesn't know
about them doesn't work with them, is broken.
> > The behavior of CSS in the presence of namespaces is undefined.
> > But I have every reason to expect that it will follow the
> > (soon-to-be-)defined behavior of XSL, which is that the universal
> > name is compared.
>
> "Every reason" as in "reasons you can't talk about"?
No; it's just the sensical thing to do.
-Chris
-- <!NOTATION SGML.Geek PUBLIC "-//Anonymous//NOTATION SGML Geek//EN"> <!ENTITY crism PUBLIC "-//O'Reilly//NONSGML Christopher R. Maden//EN" "<URL>http://www.oreilly.com/people/staff/crism/ <TEL>+1.617.499.7487 <USMAIL>90 Sherman Street, Cambridge, MA 02140 USA" NDATA SGML.Geek>