Re: [css-layout-api] Updates before F2F

>
> I also believe the code forgot a bunch of “this.” for instance when
> calling resolve*() methods, or are those methods defined in the global
> scope?
>

I stumbled over the same thing. According to the spec they are defined on
the global scope, so the example code is correct. I am wondering if
defining them on the base class would be more intuitive / idiomatic /
portable.


>
>
>
>
>
>
> *From:* Ian Kilpatrick [mailto:ikilpatrick@chromium.org]
> *Sent:* Tuesday, January 3, 2017 2:33 AM
> *To:* public-houdini@w3.org
> *Subject:* [css-layout-api] Updates before F2F
>
>
>
> Hi all,
>
>
>
> I've created an explainer
> <https://github.com/w3c/css-houdini-drafts/blob/master/css-layout-api/EXPLAINER.md>
> on github which contains an overview of the API proposal so far. The spec
> <https://drafts.css-houdini.org/css-layout-api/> has also updated which
> is much more complete than last time.
>
>
>
> Explicit things I'd like feedback on are:
>
>  - How to handle min/max content contributions. I think this is the last
> major thing to nail down. We've talked about this previously about how we
> can do this either with an additional author defined method, or via the
> existing layout method; but I'd like to gain consensus here.
>
>  - Any nits on naming and structure of the API in general. E.g. how this
> API handles scrolling, the utility functions, etc.
>
>
>
> Thanks,
> Ian
>