Re: [cssom-view] Moving forward on subpixel positioning for offset*/client*/scroll* properties

On Fri, Jun 13, 2014 at 8:56 AM, Tab Atkins Jr. <jackalmage@gmail.com>
wrote:

> On Wed, Jun 11, 2014 at 2:24 PM, Robert O'Callahan <robert@ocallahan.org>
> wrote:
> > Following up on the F2F notes...
> >
> > For offset*: getBoxQuads totally subsumes these properties and avoids the
> > craziness of offsetParent at the same time. I don't think we need to add
> > anything more here.
>
> So you mean we could just ignore those entirely and declare them
> legacy, trusting gBQ to address the problem with subpixel precision?
>

Yes. To be clear: I think there are two reasonable options for offset*:
1) Just go ahead and let them return subpixel values.
2) Do nothing and advocate getBoxQuads as the preferred alternative API.
If compatibility precludes #1, then #2.

> For client*: I think the simplest way forward for these properties (and
> for
> > scroll*, if we need to) is to add new box types to BoxType that expose an
> > element's scrollport rect and "scrolled content" rects.
>
> Yes please!  I still have no idea what scroll/client/offset actually
> mean until I look up a tutorial, every time.
>

Simon should probably just do that then :-). We can do that independently
of what we do with scroll*/client*, and extending BoxType makes all the
GeometryUtils APIs more powerful, including coordinate conversion.

Rob
-- 
Jtehsauts  tshaei dS,o n" Wohfy  Mdaon  yhoaus  eanuttehrotraiitny  eovni
le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o  Whhei csha iids  teoa
stiheer :p atroa lsyazye,d  'mYaonu,r  "sGients  uapr,e  tfaokreg iyvoeunr,
'm aotr  atnod  sgaoy ,h o'mGee.t"  uTph eann dt hwea lmka'n?  gBoutt  uIp
waanndt  wyeonut  thoo mken.o w