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

Re: [css-snappoints] Always snapping to a mandatory point

From: Robert O'Callahan <robert@ocallahan.org>
Date: Sat, 1 Aug 2015 13:00:54 +1200
Message-ID: <CAOp6jLY4Wd_hd-6hcsGQ=gCZ2Jm9YnOwC=idvu--VxNJ6dVWMw@mail.gmail.com>
To: Matt Rakow <marakow@microsoft.com>
Cc: "www-style@w3.org" <www-style@w3.org>, Majid Valipour <majidvp@chromium.org>
On Sat, Aug 1, 2015 at 7:52 AM, Matt Rakow <marakow@microsoft.com> wrote:

> > What happens if that snap point ceases to exist?
>
> In the case of mandatory snap points it will need to be resnapped to a
> valid location.  I'm inclined to leave it to the UA for exact selection
> mechanism (in the same way that a snap point selection is not specified for
> scrolling), but "snap to closest" or "snap to next" is probably a
> recommendable approach.  Likely scenarios might include deleting a
> center-snapped photo from a filmstrip view.
>
> For proximity the requirement is lightened from "must" to "may".  I expect
> UAs may want to consider other factors (e.g. distance) when deciding
> whether resnapping is appropriate.
>
> > When does this auto-snapping occur? On every layout? Including layouts
> that occur during script execution?
>
> No need to resnap synchronously during script execution; this requirement
> is intended to ensure the user isn't left long-term with an invalid view,
> not to eliminate transient states.  Resnapping should be done after
> OM/layout/display completes, as long as there's also not a scroll currently
> underway for that scroller or any descendent scroller.
>

That sounds reasonable, but it also sounds like a potential interop
minefield.

> What happens if layout changes to that the current snap point can't be
> snapped to anymore because the container can't be scrolled far enough?
>
> Same as for deleting the point.  If the snap type is mandatory then the
> scroller must be snapped to some point to ensure a valid view, so if its
> currently snapped point becomes invalid for any reason then resnapping must
> occur.
>

Is this what IE actually does? It sounds like it could lead to very bad
user experiences, where an element that the user was looking at suddenly
disappears because the browser had to scroll to snap to another element.

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 Saturday, 1 August 2015 01:01:23 UTC

This archive was generated by hypermail 2.3.1 : Saturday, 1 August 2015 01:01:24 UTC