[TIMOB-2678] Android: 2.3, new UI feedback - New yellow flash to denote scroll end ( was - when scrolling tabs to end - scrollable tab + many on a screen

So what we're seeing is the effect mentioned in the first bullet to this blog post:

http://googleblog.blogspot.com/2010/12/some-cool-android-tips-and-tricks.html"> http://googleblog.blogspot.com/2010/12/some-cool-android-tips-and-t...

To verify that it's nothing weird in our code that makes the outside border of this overscroll region not match any border radius (rounded corners) that are being used, I created a native Android app with a ListView and it's background set to...

   <?xml version="1.0" encoding="utf-8"?>
   <shape xmlns:android="http://schemas.android.com/apk/res/android"> 
       <corners android:radius="20dp"/>
       <solid android:color="#3a3a3a"/>
   </shape>
   

which I believe is the standard way to get a rounded look on a view. With the new 2.3 overscroll stuff, the effect was the same: the border of the overscroll is straight, whereas the border of the view is curved. Video of this native test app:

http://screencast.com/t/m8OoQXFJ">http://screencast.com/t/m8OoQXFJ

It appears that the only way to get around that would be to explicitly set http://developer.android.com/reference/android/widget/ListView.html#setOverscrollHeader%28android.graphics.drawable.Drawable"> custom overscroll header and footer), like this guy/gal had fun with http://www.youtube.com/watch?v=Ih8X6HnOp1c">here in this video. This would mean compiling against api level 9, however, which we can't do. (Or use reflection.)

My vote would be to ignore it because it's not so bad. Someday when we can compile against 9, or if we elect to use reflection, we can give users the opportunity (via new api props/methods) to set their own overscroll header/footer drawables.

What does Don think?

I agree that we should "ignore it" for now. I'm going to move it to TBS. Set it back to new.