Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Android 2.3.4 performance #2
Flicks go in reverse on the native browser (when attempting to go back up). Overflow doesn't seem to work at all on Firefox Mobile and Opera Mobile (Opera Mobile will slide side to side). Scrolling initially works on Dolphin HD but gets stuck after first flick.
Testing on T-Mobile MyTouch
Interesting! Okay, sounds like something to test out.
On my 2.3 device, flicks work fine but the scrolling is not very smooth after release… huh.
FF Mobile should be whitelisted for native scrolling after version 3 - where it is supposed to work well… hmm. Any idea what version you've got?
Last I checked Opera Mobile, it wouldn't allow me to set height on a container, basically forcing overflow: visible at all times. Sounds like that may vary across versions?
Lastly, on the dolphin, does a slow scroll work, or nothing at all?
On Feb 22, 2012, at 10:49 PM, Jason Weaver wrote:
On native browser the flicks have to be a certain intensity (meaning not very intense) to work well and I've noticed that I get stuck sometimes or go in reverse. A user would have to stop, take his/her finger off the touch screen and then start a slow scroll.
FF Mobile version 10.0.2 doesn't move at all. Exactly the same experience when Overthrow disabled. (Using http://filamentgroup.github.com/Overthrow/examples/2-column/ to test)
On Dolphin HD version 7.3: I can confirm slow scrolling works fine but flicks make scrolling lock up.
Great info. If you could let us know how FF Mobile behaves on that device with a regular overflow: auto element (no Overthrow added), that would be great. Overthrow should be opting that browser in for native overflow support, but it sounds like there's either a hangup or it doesn't actually support it (in which case we can change the whitelist up)
Here's a page with overflow: auto to test: http://filamentgroup.com/scott-temp/overflow.html
On Feb 22, 2012, at 11:37 PM, Jason Weaver wrote:
Okay, great. Sounds like the UA check isn't catching it. I'll take a look soon. Lemme know if you get there first!
On Feb 22, 2012, at 11:57 PM, Jason Weaver wrote: