The touch slop seems to be too large for scrolling
a small textfield, so use a smaller number. Also,
in WebView, create viewToContentDimension, and use
it for determining the scroll position of the text
field.
Partial fix for http://b/issue?id=2133049
Change-Id: I0ded3be264b179bad39301e6adce86851b649a42
Move the specialized code in NEW_PICTURE_MSG_ID to
setContentScrollTo so that a scroll to (0,0), whether
a result of a NEW_PICTURE_MSG_ID or from an initial
layout (or otherwise) is treated as scrolling to the
top of the content, including showing the title bar.
Scrolls to (0,1) will trigger code that animates the
title bar off screen.
Change-Id: Ia6db6d4620dea2bfe62407c4394a8ead38501b2f
Use the set dialog height when the find dialog is up so that
found items at the bottom of the screen are scrolled into view.
This requires a companion change to set the dialog height in
the browser app.
Fixes http://b/issue?id=2122916
Slows down the animation so the user can see it slide away. Also
move the animation to before we change to view coordinates so it
will not be dependent on the zoom level/screen resolution.
Change-Id: Icc54b2b26c08cd54d84b4e9892a316a5712534e4
Though the user can still manually scroll the title bar
off screen, we do not want it to happen automatically.
When we load a new page, its scroll position can be
set to (0,0). Make sure that we simply set it to the
top without adding in the title bar's height. Also,
prevent javascript which attempts to scroll the page
to (0,0) or (0,1) from removing the title bar.
Fixes http://b/issue?id=2113398 and http://b/issue?id=2123079
Change-Id: Ida64d8c94be6744c7b0b4d60af1c229b2cc83673
Call another invalidate() to draw with the final filters.
This fixed the problem where the end of the zoom animation
is slow and jagged.
Fix http://b/issue?id=2126523
Fix http://b/issue?id=2074446
Add in code that is normally called by TextView.onDraw(). Since
drawing does not happen for WebTextView, we need to call it
ourselves.
Change-Id: Icb47f6a58fba6f8b11e2924befc704f26af68d43
Slide the title away if the scroll is to zero or one, and the
title is partially or fully visible. Set the animation time
to at least SLIDE_TITLE_DURATION, currently set to 300 ms.
Fix http://b/issue?id=2019857
If the user has not moved beyond the scaled touch slop, do not
turn it into a scroll, so the user can change the selection.
Change-Id: I1d88691a35ea2da4b03ad713b56331b5c268b757
If the restore requests a scroll to zero and the titlebar is
partially or fully visible, skip the scroll altogether.
This fixes http://b/issue?id=2123079
Two methods in WebViewCore are called from WebView. The C
underpinnings were synchronized with a mutex, but the Java
shell was not, so under rare cirumstances, the Java side might
delete the native class. Add Java synchronization to
protect against this.
Fixes http://b/issue?id=2121684
Call nativeMotionUp from touchUpOnTextField to move the
mouse cursor to the text field if necessary before moving
the text caret to the desired position.
Fixes http://b/issue?id=2075647
Dragging and flinging have different minimums for the max Y
value. Allow the fling to have the title height instead of zero
for the minimum max Y so the title can always be removed via
fling.
This fixes http://b/issue?id=2109006
scrollbar. The worst case is that you can never scroll down to the last
pixel. The old special case can cause problem when getViewWidth/Height
have changed which do not match mLastXXSent any more.
Remove FIND_HEIGHT from computeVerticalScrollRange per conversation with Leon.
Change computeMaxScrollY to use computeVerticalScrollRange which matches
how it computes X.
Change onMeasure to use contentToViewDimension() as it has the same logic.
