W3C home > Mailing lists > Public > www-style@w3.org > March 2013

Re: [css3-regions] offsetParent for element collected inside a named flow

From: Garrett Smith <dhtmlkitchen@gmail.com>
Date: Mon, 25 Mar 2013 14:58:49 -0700
Message-ID: <CABZUbM3AMK=quMsjFaknnA38dYhj+1a1d_WyBED5Tcwdp6PvMw@mail.gmail.com>
To: Alan Stearns <stearns@adobe.com>
Cc: Andrei Bucur <abucur@adobe.com>, Mihnea-Vlad Ovidenie <mihnea@adobe.com>, "www-style@w3.org" <www-style@w3.org>
On 3/25/13, Alan Stearns <stearns@adobe.com> wrote:
> On 3/25/13 9:42 AM, "Garrett Smith" <dhtmlkitchen@gmail.com> wrote:
>>On 3/25/13, Andrei Bucur <abucur@adobe.com> wrote:
>>> With regions, this is more complicated because an element gets to
>>>occupy a
>>> certain space inside the viewport because of both the flow layout and
>>> layout. I can imagine there are situations when developers want to
>>> the offsetParent relative to the flow in some contexts and the visual
>>> offsetParent relative to the regions in other contexts.
>>Nobody who knows what they are doing would want to use offsetParent.
>>The problems with this festering property have continued because it
>>was specified normatively.
> So your recommendation would be not to make any changes to these
> attributes, because they aren't reliable anyway?
Yeah, leaving it alone might be a good call at this point. THough I
haven't retested all the latest implementations so I'm not sure what
they're doing now.

I think the spec should mention that offsetParent, offsetLeft, and
offsetTop have been implemented inconsistently; developers should
instead use getBoundingClientRect.

> Thanks,

Thanks for asking.
Twitter: @xkit
Received on Monday, 25 March 2013 21:59:18 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:27 UTC