When reading the famo.us docs in desktop Chrome, I see an overshoot effect when scrolling past the top or bottom of the center container (i.e. below the header). It seems famo.us emulates the overshoot to resemble the native overshoot of iOS apps.
Is there an option (declaratively or programmatically) to disable the overshoot?
Assuming your talking about a Scrollview, you can define pretty much all of the aspects that effect how it handles input. In the options object when creating the ScrollView you can set edgePeriod = 0. In physics, the period is the time taken for one cycle of vibration. So this should make sense. More options are documented in the docs.
P.S There seem to be a few typos and glitches with the docs generated, I'll file a an issue and see about normalizing it. (egePeriod??)
