W3C home > Mailing lists > Public > whatwg@whatwg.org > January 2018

Re: [whatwg] [CSSWG][css-scroll-snap] Updated CR of CSS Scroll Snapping Level 1

From: Anne van Kesteren <annevk@annevk.nl>
Date: Thu, 4 Jan 2018 13:44:06 +0100
Message-ID: <CADnb78j0NDPOAqATrTi+NeJ4VqCsK47ETHFs7N=2X9xf-WLfZQ@mail.gmail.com>
To: fantasai <fantasai.lists@inkedblade.net>
Cc: WHAT Working Group <whatwg@whatwg.org>, public-review-announce@w3.org, "www-style@w3.org" <www-style@w3.org>
On Mon, Dec 25, 2017 at 11:54 AM, fantasai
<fantasai.lists@inkedblade.net> wrote:
> A related concern was brought up that some DOM APIs define scrolling to
> an element in a way that conflicts with scroll-snapping; such APIs should
> allow for an element's snap position, if defined, to dictate the position
> of an element to the viewport if no explicit argument is given to the
> contrary.

The way I would expect this to work is that if CSS "owns" scrolling
(which I think it ought to), it defines an operation that performs
scrolling taking into account various parameters. Those DOM APIs then
call into that operation. Then if you define new properties that
affect scrolling, you only need to adjust the scrolling algorithm and
the various APIs will not require any changes as they all share the
same underlying primitive. I'd recommend figuring out that primitive
and clearly documenting it (parts of it are already in CSSOM View if I
remember correctly).


-- 
https://annevankesteren.nl/
Received on Thursday, 4 January 2018 12:44:38 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:45 UTC