W3C home > Mailing lists > Public > www-svg@w3.org > January 2014

Re: [svg][filter-effects][css-masking] objectBoundingBox/userSpaceOnUse in HTML

From: Dirk Schulze <dschulze@adobe.com>
Date: Fri, 3 Jan 2014 22:34:01 +0000
To: Tab Atkins Jr. <jackalmage@gmail.com>
CC: www-style list <www-style@w3.org>, public-fx <public-fx@w3.org>, www-svg <www-svg@w3.org>
Message-ID: <D9A245B0-5CE3-4A20-8641-D23334195304@adobe.com>

On Jan 3, 2014, at 10:40 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:

> Note the closely-related question of what to do for paint servers in a
> CSS context, which Images defines in line with Firefox implementation,
> based on an old blog post of roc's:
> <http://dev.w3.org/csswg/css-images/#paint-sources>
> 
> There, the space you're drawing into is identical for both cases; the
> only difference is the size of a coordinate unit.
> 
> I think the same really makes sense here, for things like clip-path -
> use the bounding rect.  If we have a way to manipulate the box used,
> it should also affect stuff using objectBoundingBox, in the same way
> as images.
> 

It makes very much sense to use the same definition. While I describe the size as the bounding client rect (based on the result of getBoundingClientRect()), CSS Image is using the term “concrete object size”. The definition of this term spreads across three other definitions and is a bit confusing to me. Could you provide examples how this looks like for overflowing content?

I assume that the definition of "concrete object size" is not necessarily compatible with the observed behavior in Firefox, WebKit and Blink where it is the mentioned bounding client rect for objectBoundingBox for example.

Greetings,
Dirk

> ~TJ
Received on Friday, 3 January 2014 22:34:50 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:47:35 UTC