W3C home > Mailing lists > Public > www-style@w3.org > July 2003

Re: attr() construct in generated content and namespaces

From: L. David Baron <dbaron@dbaron.org>
Date: Sat, 26 Jul 2003 21:27:57 -0700
To: Boris Zbarsky <bzbarsky@MIT.EDU>
Cc: www-style@w3.org
Message-ID: <20030727042757.GA5887@pool-141-158-54-70.phil.east.verizon.net>

On Saturday 2003-07-26 22:57 -0500, Boris Zbarsky wrote:
> How exactly does the attr() construct work in the presence of namespaced 
> attributes?  For example, what is the expected rendering of:
> 
> <div xmlns:xlink="whatever"
>      xmlns:myNS="somethingElse"
>      xlink:type="convoluted"
>      myNS:type="confusing"
>      type="confounding" />
> 
> styled with:
> 
> div::before { content: attr(type) }
> 
> ?

The combination of [1] (which is a bit vague) and [2] (which is a bit
off-topic) suggests that you should end up with "confounding".  I think
the general principle there is that you should need to use namespaces in
order to end up with any of the others (either through the namespace
awareness described in css3-namespace or through attr(xlink\:type) in
non-namespace-aware CSS).

-David

[1] http://www.w3.org/1999/06/25/WD-css3-namespace-19990625/#q4
[2] http://www.w3.org/1999/06/25/WD-css3-namespace-19990625/#attr-selector

-- 
L. David Baron                                <URL: http://dbaron.org/ >
Received on Sunday, 27 July 2003 00:28:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:22 GMT