Fix for scrolling when the user has already scrolled.

[remy]

fix for scrolling the window when the user has already started scrolling - apparent when slow download and user is ahead of content or when jQM is being used on desktop platform - ref http://remysharp.com/doing-it-right-skipping-the-iphone-url-bar/

[remy]

I should have added this, but you can see it on @aral's site - just scroll down whilst it's loading and it'll jump.

[scottjehl]

Woops. Yeah, spot-on. Cool, care to update the pull then?

[remy]

No time - literally running out the door to leave for day long training - can do next week when got a few mins!

[gseguin]

That request has gone stale. @remy could you update it with what you agreed on with @scottjehl?

[scottjehl]

I think this generally covers what we want to do:
https://gist.github.com/1183357

We'll need to adapt it to jQM, but same principle.

On Sep 1, 2011, at 5:23 PM, gseguin wrote:

That request has gone stale. @remy could you update it with what you agreed on with @scottjehl?

Reply to this email directly or view it on GitHub:
#2095 (comment)

[eddiemonge]

@remy @scottjehl Following up on is this is still valid or needs to be updated.

[johnbender]

This appears to be a problem of determining the performance tradeoffs of scrollTop and a scrollstart when deciding whether to scroll to the default home scroll value

$window.load( function() {
    if( $window.scrollTop() <= 1 ) {
        $.mobile.silentScroll();
    }
});

I'm also confused by @scottjehl's snippet that suggests we should only be scrolling to 1 or 0 when the scrollTop value is greater than 1 given that we're trying to avoid scrolling when the user has altered the value by scrolling.

[johnbender]

@scottjehl

Wanted to pop this back on your radar. Two questions:

1. My previous question still requires clarification, we really don't want to scroll if the scrollTop value is greater than 1 right?
2. I'd like to avoid firing up the scrollstart machinery if we can (first time sets up the watch and then triggers the event). Does anyone have sense for which is worse reflow or scrolling machinery (@jblas?)

[johnbender]

@remy @scottjehl

I'm going to close this one in my next pass if there isn't movement. Seems like it isn't hyper critical right now.

[scottjehl]

Well, I still think we should make the change if we haven't already. It should probably be added as an issue though - this pull didn't contain the proper fix quite yet if I remember right?

On Apr 3, 2012, at 2:34 AM, John Bender wrote:

@remy @scottjehl

I'm going to close this one in my next pass if there isn't movement. Seems like it isn't hyper critical right now.

---

Reply to this email directly or view it on GitHub:
#2095 (comment)

[johnbender]

@scottjehl

Right you are. Closing in favor of the #3958.