W3C home > Mailing lists > Public > www-style@w3.org > March 2012

Re: [css3-images] [css3-gcpm] element() and element()

From: L. David Baron <dbaron@dbaron.org>
Date: Wed, 7 Mar 2012 16:24:40 -0800
To: www-style@w3.org
Message-ID: <20120308002440.GA7486@pickering.dbaron.org>
On Wednesday 2012-03-07 14:53 -0800, fantasai wrote:
> On 02/29/2012 03:57 PM, Simon Fraser wrote:
> >On Feb 29, 2012, at 3:45 PM, fantasai wrote:
> >
> >>[Once more, with correct tags...]
> >>
> >>GCPM defines an element() function, which returns an element
> >>  http://dev.w3.org/csswg/css3-gcpm/#running-elements
> >>
> >>and Images defines an element() function, which returns an image
> >>  http://dev.w3.org/csswg/css3-gcpm/#running-elements
> >>
> >>They are not the same, and they are both acceptable as input to 'content'.
> >>
> >>I don't have a solution, but there is a conflict here.
> >
> >element() in the CSS Image case doesn't immediately strike me
> >as meaning a snapshot of the targeted element. Maybe we should
> >use something more descriptive, like:
> >
> >snapshot() (even though it updates)
> >replica()
> >element-image()
> >imageof()
> 
> Another option is just paint(), since we are expecting it to be
> used with paint servers etc.

I think all of these are inferior to element() considering the
context, which is something like:

  background: element(#tab);

In the context of the background property, we know we're talking
about something to draw.  What's interesting is that the thing being
drawn is an element from the document.

-David

-- 
𝄞   L. David Baron                         http://dbaron.org/   𝄂
𝄢   Mozilla                           http://www.mozilla.org/   𝄂
Received on Thursday, 8 March 2012 00:25:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 22 May 2012 03:48:51 GMT