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

Re: [CSSOM] Interaction of getBoundingClientRect/getClientRects with transforms

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Tue, 31 Aug 2010 07:34:18 -0700
Message-ID: <AANLkTin12-WcGhaFSvepxHm33vrmH91rM+oCpO7O0-gz@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: www-style list <www-style@w3.org>
On Tue, Aug 31, 2010 at 7:30 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> On 8/31/10 10:13 AM, Tab Atkins Jr. wrote:
>>> Bounding box is what we do for SVG so we should do that here too. Ideally
>>> the definition of "border box" in CSS reflects this behavior or CSS gets
>>> a
>>> different kind of "border box" that reflects this behavior and CSSOM View
>>> is
>>> updated to use that.
>> Given that transforms don't affect the geometry
> Well...  do they not?  If not, why should they affect getClientRects?

No, they don't.  And so, they shouldn't.  That was my point.

>> (I'm curious about how a transformed element works when used in a
>> background with the -moz-element() function or the -webkit-canvas()
>> function, particularly with background-repeat:repeat.)
> -moz-element currently uses the untransformed size as the size of the
> background image for -moz-element, and draws the transformed element into
> that box, clipping at the edges.  Screenshot of a 500px by 500px div using
> the 45-degree-rotated div from my other example as a repeating -moz-element
> background.

Cool.  That confirms to me that CSS's current conception of "border
box" as being something with page-geometry is just fine to use for

> Why would there be an issue with -webkit-canvas?  -webkit-canvas presumably
> just uses the canvas backing store as the background image; since the canvas
> it uses isn't even shown on the page there are no transforms involved.

You're probably right about us just using the backing store directly.
The canvas being used *can* be shown on the page, though it doesn't
*need* to be.

Received on Tuesday, 31 August 2010 14:35:08 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:07:49 UTC