UX / UI issue/suggestion

[hessius]

Having the content as slide-selector and not setting containerSlideDelay causes some usability issues on pages that need scrolling (e.g. lists)

Setting a slideDelay remedies those issues. From feedback I've come to understand that this slideDelay is perceived by (some) end users as lag. I think that it is not really the SlideDelay itself that users perceive as lag but rather that the container snaps out to the selected delay-position instead of sliding from the edge.

If the containerSlideDelay could be tweaked so that it instead is the distance which the user has to slide before the container starts sliding from the edge the perceived lag would be gone.

[wnielson]

Thanks for the input. I see what you mean and I like the idea, but my initial reaction is that this might be rather difficult. "slideDelay" is also a horrible name (my fault) because it isn't a delay, but rather a distance (in px) that must be dragged before the component is allowed to slide. The problem, off the top of my head, is that once the user starts dragging, the amount of drag (offset) for the remainder of the drag event is from that initial starting point, but what we really want is essentially "[current offset of event] - slideDelay".