History log of /cts/tests/src/android/view/cts/FocusFinderStubActivity.java
Revision Date Author Comments
d4d396426119cbd55ce560f544ee7356a23c9d89 09-Sep-2010 Brian Muramatsu <btmura@android.com> FocusFinderTest Workarounds...

Bug 2437360

The FocusFinder tests were failing on large width screens, because
the focus model takes into account the width of the widgets. The
prior layout had buttons that spanned the entire screen, and this
caused the focus behavior to change across different screen sizes.
This does not seem correct, but it is how the framework is coded.
Create a new layout that has four equally-sized center buttons to
avoid this problem.

Finally, the FocusFinder#findNearestTouchables seems to not take
into account the touch coordinates when calculating the delta
offset for the down and right focus directions which thus makes
the distance greater than the "edge slop" causing it to fail.
This also does not seem correct but probably due to a lack of
my understanding (Bug 2986136). Work around the problems using
more simple cases that touch on the outer edges of the widgets
that do not trigger that problem.

(Backport from Froyo. match_parent attributes changed to fill_parent
and strings added to strings.xml to get around translation errors)

Change-Id: I1b33e254c4d15c29f85713758ccf61366b6071da
4adc2b8dd15323659f6051136b5c0aab83ed7b09 09-Sep-2010 Brian Muramatsu <btmura@android.com> FocusFinderTest Workarounds...

Bug 2437360

The FocusFinder tests were failing on large width screens, because
the focus model takes into account the width of the widgets. The
prior layout had buttons that spanned the entire screen, and this
caused the focus behavior to change across different screen sizes.
This does not seem correct, but it is how the framework is coded.
Create a new layout that has four equally-sized center buttons to
avoid this problem.

Finally, the FocusFinder#findNearestTouchables seems to not take
into account the touch coordinates when calculating the delta
offset for the down and right focus directions which thus makes
the distance greater than the "edge slop" causing it to fail.
This also does not seem correct but probably due to a lack of
my understanding (Bug 2986136). Work around the problems using
more simple cases that touch on the outer edges of the widgets
that do not trigger that problem.

Change-Id: I1b080b13c8e2973808ca6e4eceea2b6e599d9749
3da7534f2880068b90b88585c45be62751dbfd6b 13-Jan-2010 The Android Open Source Project <initial-contribution@android.com> android-2.1_r1 snapshot
0cbe49a83ac10de466b8efa8d8775d8686353186 09-Jan-2010 Romain Guy <romainguy@android.com> Deprecate fill_parent and introduce match_parent.
Bug: #2361749.
597759f5189ecbed3803046dee4a86c575a57b0c 19-May-2009 Phil Dubach <phillipd@google.com> Integrate unsubmitted cupcake change 122803:
CTS: add test cases for FocusFinder and GestureDetector