[Webkit-unassigned] [Bug 184626] New: [css-scroll-snap] Sometimes freezes between snap positions when nested scrolling element receives a scroll in alternate axis against nested scroll containers edge?

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=184626

            Bug ID: 184626
           Summary: [css-scroll-snap] Sometimes freezes between snap
                    positions when nested scrolling element receives a
                    scroll in alternate axis against nested scroll
                    containers edge?
           Product: WebKit
           Version: Safari Technology Preview
          Hardware: Macintosh
                OS: macOS 10.12
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: CSS
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: hi at jonjohnjohnson.com

I made the title of this bug as specific as I was able to deduce. :/

Observed:
Scroll-snap freezing between scroll-snap positions.

Expected:
Scroll-snap should always snap to a position if type if set to `mandatory`.

Steps to reproduce:

1. Visit this test case -> http://output.jsbin.com/lefekiv/5
2. Scroll horizontally and notice scroll-snapping between full window sized "pages".
3. Scroll vertically within each "page".
4. Sometimes when horizontal snapping hasn't finished, nested vertical scrollers receive a vertical scroll event and freezes horizontal snapping.

I am *pretty sure that it only freezes when the vertical scroll event is happening against an already fully scrolled edge, top or bottom.

Note, this sounds similar to another bug (https://bugs.webkit.org/show_bug.cgi?id=183239), but when I test the bug inducing behaviors for each, what causes failures in one doesn't in the other.

Here is a quick video showcasing the freezing, though not easy to tell when my trackpad commences vertical scrolling:
http://cl.ly/qtlD

As an aside, from what I've seen in the iOS versions of safari, scrolling axises that aren't on the same element, can NEVER happen at the same time, which is nice, and might be a preferred ux paradigm for desktop safari as well? If you offer feedback being in favor of this note, maybe I'll bring up the topic to the csswg about making it a specified behavior for consistencies sake?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20180414/dfe3a4cf/attachment.html>