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

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

From: Ojan Vafai <ojan@chromium.org>
Date: Wed, 22 Sep 2010 08:34:15 +1000
Message-ID: <AANLkTinGo2D=EXXphDLwmmX+WkNgJ3D7CJrbqdJOW3d0@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: Simon Fraser <smfr@me.com>, www-style list <www-style@w3.org>
On Wed, Sep 22, 2010 at 4:21 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote:

> On 9/21/10 2:17 PM, Simon Fraser wrote:
>
>> I agree. I'd expect one of two behaviors for rotated inline elements. The
>> first would be "slab" rotation, where all parts of the element are rotated
>> on a plane (with some center point that we'd specify, probably the center of
>> the bounding box of the parts of the span). The second would be that the
>> rotation is applied per line, somehow.
>>
>
> Both of these really do look pretty weird with bidi text (for example, it's
> pretty easy to end up with a situation where the boxes on a line are:
>
>  XXXX YYYYYYYYYYYYYYYYYYY XXXX
>
> where the Xs belong to one span and the Ys to another.  When applying a
> transform to the X span, things would look pretty odd.
>
> Maybe that's just a cost of supporting both bidi reordering across inline
> element boundaries and sufficiently rich styling of inline elements.  I
> guess borders look pretty weird too, in that situation.


That certainly would look weird, but I don't think it's any weirder than the
current Gecko behavior. More importantly, I think web developers would
understand what was going on here (to the extent that anyone understands
bidi!) and not have difficulty coming up with a workaround.

Ojan
Received on Tuesday, 21 September 2010 22:35:06 GMT

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