- From: fantasai <fantasai.lists@inkedblade.net>
- Date: Tue, 06 Mar 2012 14:23:24 -0800
- To: "www-style@w3.org" <www-style@w3.org>
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() I also got the following suggestions from mpt: Matthew Paul Thomas wrote: > > mirror > clone > liveclone > portal > reflect > transmit > counterpart > facsimile > replica > mimic > portray > manifold > puppet > > Of these, the one I like best is "mimic". > - It conveys that the image is just a bitmap imitation, not a real HTML object. > - Unlike "clone", "facsimile", etc, it suggests that the imitation is responsive -- it changes whenever the original does. > - It's hard for developers to misspell. ~fantasai
Received on Tuesday, 6 March 2012 22:23:56 UTC