Comments on: W3C CSS Namespaces; Now a Candidate Recommendation

By: JeromeLapointe

JeromeLapointe — Tue, 27 May 2008 17:29:30 +0000

Also I wonder how complicated it will be when you have your xml namespaces and CSS name spaces and need to target both… like xforms where you’d like to create some namespace to split sub portion of the website… like the affiliate program related pages… and therefor differentiate between your two xform signup pages… in this case the “username” …

affiliates|xf\:input#username

By: JeromeLapointe

JeromeLapointe — Mon, 26 May 2008 17:26:21 +0000

So I would go:
namespace|ul li a{}

but could I go:
ul li namespace|a{} …?

By: cromwellian

cromwellian — Mon, 26 May 2008 17:17:56 +0000

I’ve always hated the use of the pipe ‘|’ character for this back when it was first proposed. Yes, “:” is already used to separate pseudoclasses/elements, but perhaps they could have used “::” instead which is the scoping operator in “some” programming languages (e.g. C++) Or given that they are using suffix operations now, they could have just used pseudo-class syntax

Compare:

toto|A { … }

A::toto { … }

toto:ns(A)

Perhaps they considered this at the WG and rejected it for some reasons.