Re: [css-snappoints] Definition of "nearest ancestor" for scroll-snap-coordinate

+Matt and Jacob (the snap points spec editors).  Are you guys still
actively editing the snap points spec, at least to track these open issues?

On Mon, Jun 22, 2015 at 2:43 PM, Majid Valipour <majidvp@chromium.org>
wrote:

> On Mon, Jun 22, 2015 at 1:59 PM Simon Fraser <simon.fraser@apple.com>
> wrote:
>
>> On Jun 22, 2015, at 5:10 AM, Majid Valipour <majidvp@chromium.org> wrote:
>>
>> I think redefining in terms of containing blocks should address the
>> issues with the absolute positioned elements.
>>
>>
>> Sounds good. Do you (or Matt) plan to do any draft spec updates soon with
>> the recent changes?
>>
>
> Not me but I suppose Matt, being the editor, will be the person to update
> the spec. I am happy to share our thoughts as one of the implementers.
>
> On that note, the last f2f meeting notes mention potentially reworking the
> spec to define snapping behaviour based on box alignments instead of the
> current coordinate alignment in order to handle responsive environments. I
> feel that is a larger change compared to recent changes discussed in the
> mailing list. I am wondering if that is going to be added to spec any time
> soon as well? We should stay away from shipping two slightly different ways
> of doing scroll snaps.
>
> Majid
>

Received on Wednesday, 24 June 2015 14:18:30 UTC