Enable is not the exact opposite of disable

[tkahn]

Enable is not the exact opposite of disable

[tkahn]

This is strange since I don't really disable mousewheel scrolling in the disable function - I just set the "enabled" variable to false. Then I check if the "enabled" variable is true or false in the event handlers. So when you scroll using the mousewheel an event is triggered and if the variable "enabled" is true the scroller should scroll. If it's false the event handler will still execute but nothing will happen since "enabled" is false.

So I'm thinking there might be something else going on here?

Regarding the resetting of the scroller position to the starting point, is most likely a legacy thing. It's been that way since the first version and I'm not really sure why I implemented it that way in the first place, but I think it was because I wanted to reset the position if you replaced the content in the scroller. Or there could have been some browser bug that prevented the scroller from working in a specific browser.

I will do some testing and remove it if I find it's not needed. You can comment out rows 1026-1027 in the source code and make a new minified version here: http://marijnhaverbeke.nl/uglifyjs

[css117]

Indeed, I allready commented those lines, wihtout any side effects :)
And I abandonned the disabling / enabling actions because I'm triggering loading stuffs before the end is reached, so I don't need any disabling anymore.
Thanks !

[tkahn]

Okay! I will close this issue now!
The result is that the resetting of the scroller position will be removed in the next update since I don't think it fills any purpose anymore.