summaryrefslogtreecommitdiff
path: root/core/java/android/inputmethodservice/IInputMethodWrapper.java
diff options
context:
space:
mode:
authorGrace Kloba <klobag@google.com>2010-03-28 15:49:23 -0700
committerGrace Kloba <klobag@google.com>2010-03-29 09:32:36 -0700
commit51b97011b73c10b832ea4ad10637f761802e125d (patch)
tree1ecf91ca67e33334a80216ef93f39b022021496f /core/java/android/inputmethodservice/IInputMethodWrapper.java
parent7c3006f53ac02adeac7396726cdc0bf5d6d01926 (diff)
cherry-pick 4a4f9886a789ece80f127397c1c7ad7f543b78fa into froyo
Use the content width to calculate the zoom overview width. We used to use the minimum preferred width to calculate the overview width as it is what we use to define the viewport width. But some sites, like cbsnews, engadget, the content width will be slightly wider than the viewport width decided by the min preferred width. The result is we can still scroll a little bit in the overview mode. This issue is magnified when we introduce the overscroll feature. By using content width as zoom overview width, we will have content fit in the overview mode. But some sites, like "http://www.sfjazz.org/concerts/2010/spring/artists/towner.php" will be layout wider in the overview mode than it is in the zoom in state. This is a tradeoff. Fix http://b/issue?id=2551119
Diffstat (limited to 'core/java/android/inputmethodservice/IInputMethodWrapper.java')
0 files changed, 0 insertions, 0 deletions