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.
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.
Fix for http://b/issue?id=2063143 . Use TypedValue's
types to set the text size properly for the screen's
density.
Change-Id: I3772035157e2a9a8a2dba00ebddbf967c42bfa99
mRequestHandle is only set from Network. So we can skip checking whether url is Network url if mRequestHandle is not null.
Fix http://b/issue?id=1980031
Add a test to doFling() to return quickly if the fling has
no effect. For simplicity, only test for horizontal or vertical
flings.
The man purpose is to avoid suspending webkit until the fling
animation is complete when the purpose of the touch drag is
to activate a touch event, like a swipe in superpudu.
fixes http://b/issue?id=2052852
Browser defaults overview mode to true in BrowserSettings.java,
but a WebView should default overview mode to false. This permits
applications without zoom interfaces, such as HTMLViewer, to
have the same interface as before.
Rename addTitleBar to setEmbeddedTitleBar. This requires a change
to packages/apps/Browser. Also remove mTitleBar if there already
was one.
In ViewManager, call contentToViewDimension where appropriate.
Change-Id: If4d378fad192990253411924a9a80bee96e63ff2
have a bigger minPrefWidth than the screen width. So we don't want to force
the minZoomScale to be same as defaultScale. Otherwise we won't be able to
zoom out in these sites.
Fix http://b/issue?id=2090718
Remove the old notions of changing the viewing mode
resulting in changing the visibility of the title bar.
Instead, attach the title bar to the top of the page.
Change contentToView() to contentToViewY() (and an X
version; same change for viewToContent), to account
for the title bar's height. Adjust the parameters
for drawing the scroll bar to account for the title bar.
Requires a change to packages/apps/Browser.
Change-Id: Ic0f7d6e0a1cce58ba2bca87337cf72a8194e9aa4
Partial fix for http://b/issue?id=2081673
This prevents a crash. However, if the user continues typing
into the textfield, the selection is incorrect. The real solution
(forthcoming), will make sure that the WebTextView's text gets
updated when webkit updates.
Change-Id: Ic832ec48fd4236c8116c5cbda1467677ad731feb
We need to pass them to WebViewCore as they are per process base. If we drop
them, the counter in the JWebCoreJavaBridge can be out of order.
Part 2 of fixing http://b/issue?id=2087410
* changes:
When we get 304 and switch to cacheLoader, need to set mFromCache to be true. So that the cache loading will not create a new mCacheResult which overwrites the old cache data.
Use the fact that the scroller keeps track of the current velocity
to accelerate subsequent flings. The current velocity is added to
the new velocity if the flings are in the same general direction
and if the fling animation hasn't been aborted.
This makes it easier to move to the top or bottom of very large
pages (either in overview mode or reading mode) by taking
consecutive flings as a cue from the user that they want to
page faster. The user can stop the fling with any action as
before.
fixes http://b/issue?id=2066090
This change adds the EventHandler error codes to WebViewClient for the public
api. Previously, the api was ambiguous about the value of the errorCode
parameter and falsely documented that the values are HTTP status codes.
