W3C home > Mailing lists > Public > www-style@w3.org > August 2011

Re: [css3-images] Element() corner-cases

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Mon, 8 Aug 2011 15:40:37 -0700
Message-ID: <CAAWBYDC-VNf2D8eG7D1YLCT1bKVFNJOWbRS51seDp5jjxRThHQ@mail.gmail.com>
To: fantasai <fantasai.lists@inkedblade.net>
Cc: www-style@w3.org
On Mon, Aug 8, 2011 at 3:14 PM, fantasai <fantasai.lists@inkedblade.net> wrote:
> On 08/08/2011 12:36 PM, Tab Atkins Jr. wrote:
>>
>> All right, I've rewritten the element() section:
>> <http://dev.w3.org/csswg/css3-images/#element-reference>.  Please let
>> me know if I've made any mistakes.
>>
>> * Transforms on the element are now ignored
>> * The size of the image is now the "bounding box" of the element (do I
>> need to be more specific?  If so, how?)
>> * Pages are adjoined when calculating the size/appearance of elements
>> broken across pages.
>
> Use the term "page content area" when specifying what to concatenate,
> since that excludes the page borders/padding/margins.

Thanks, changed.


>> * defined a general notion of "paint source" which SVG and HTML can
>> use for elements that don't need to be rendered to be used as an image
>> (<linearGradient>,<img>, etc.)
>
> I'm not sure that <img> etc. from HTML should be considered "paint sources"
> rather than just handled as regular elements... why do you want to do this?

-moz-element() allows some elements (limited, I believe, to
<img>/<video>/<canvas>) to be used in the function without being
inserted into the document (you create them in script, then associate
them with a virtual id).  By default, if they're not in the document,
they're not rendered, and so wouldn't be usable.  SVG's paint servers
suffer from the same problem (they're not rendered directly, but they
have an intrinsic notion of size and appearance), so it seemed elegant
to just unify the concepts.

~TJ
Received on Monday, 8 August 2011 22:41:51 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:43 GMT