- From: Robert O'Callahan <robert@ocallahan.org>
- Date: Wed, 2 Sep 2015 14:55:06 +1200
- To: www-style <www-style@w3.org>
- Message-ID: <CAOp6jLbRj+JkV7sVkFgQ_4Jd858xPdBvk7CbY2bf2X4n2uDEQg@mail.gmail.com>
https://drafts.csswg.org/css-scroll-snap/ Basically it seems good. Obviously I prefer the box-oriented model. This draft lacks a processing model and that leaves many ambiguities about which snappoints are actually relevant to each snapping container, and how those snappoints are actually used to affect scrolling. This draft is silent on the issue of what happens with dynamic changes to the layout. The use-cases for "group-based snapping" aren't very clear. Nor is the behavior of the group snapping properties. I basically have no idea what group snapping is for. It seems to me that for the use-cases cited, proximity scrolling of individual items would work just as well. One way to resolve this would to just drop group snapping from level 1. Rob -- lbir ye,ea yer.tnietoehr rdn rdsme,anea lurpr edna e hnysnenh hhe uresyf toD selthor stor edna siewaoeodm or v sstvr esBa kbvted,t rdsme,aoreseoouoto o l euetiuruewFa kbn e hnystoivateweh uresyf tulsa rehr rdm or rnea lurpr .a war hsrer holsa rodvted,t nenh hneireseoouot.tniesiewaoeivatewt sstvr esn
Received on Wednesday, 2 September 2015 02:55:35 UTC