W3C home > Mailing lists > Public > www-style@w3.org > June 2015

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

From: Majid Valipour <majidvp@chromium.org>
Date: Mon, 22 Jun 2015 18:43:23 +0000
Message-ID: <CAB8RdXtwwGqZ0aAjJv5c=Y0b6yojZ18pkF4S4m5AC4DPmsCVeg@mail.gmail.com>
To: Simon Fraser <simon.fraser@apple.com>, Majid Valipour <majidvp@chromium.org>
Cc: "www-style@w3.org list" <www-style@w3.org>
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 Monday, 22 June 2015 18:44:12 UTC

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