It is also controlled by ENABLE_DOUBLETAP_ZOOM flag. Currently the default
is on.
Double tap will toggle between current zoom level and all the way zoom out,
in another word, zoom overview mode.
While in zoom overview mode, don't display zoom control while panning. You
can click to follow the link. If clicking on a text input box, it should
bring it back to the normal mode so that it will be easy to edit text.
While in zoom overview mode, the page is zoomed to fit the width in the
view. While the text paragraph are wrapped to the matching normal mode scale.
So there is no reflow when we switching between two modes.
Merge commit '3b99e64e5899030b5d6f8201cb56cd149c80b24d'
* commit '3b99e64e5899030b5d6f8201cb56cd149c80b24d':
Per conversation, remove the toast while saving the Certificates to CertTools.
When TextView handles a mouse move as a scroll, scroll the
underlying textfield/textarea. Also do not hide the cursor
while scrolling within a text input. Requires a change to
external/webkit.
Fix for http://b/issue?id=1703971. Because the browser overlays
the WebTextView over textfields, it intercepts all the touch
events, which was preventing the page from scrolling. This
change passes the move events back to the WebView to make
the page scroll.
The Browser used to have a concern around mapping text extensions to various
text/* mime types. If a text extension mapped to an unknown text/* mime type,
the Browser would attempt to download a url instead of just displaying the
content.
There is another change in external/webkit that uses 2 static functions in
DOMImplementation that determine if a mime type is text or xml. The text
function in particular checks for a leading "text/" string in the mime type.
With that change, pruning text mime types is no longer needed.
Bug: 1988375
205 is interpreted by Safari to be like 200 and show the given content. Change
canHaveResponseBody to allow 205 to have a body.
305 is a very rare server response indicating to the client to use the given
Location header as a proxy and reissue the original request. Curl doesn't do
anything with this header and neither does internal networking code. For now,
we will just allow the response body to propagate to webcore.
Instead of calling remove(), which would hide the soft
keyboard, remove the WebTextView manually, so the soft
keyboard remains up (if it was up to begin with). WebView
will properly handle the keys now that the focus has
changed.
* changes:
Fix 1986313. WebKit assumes things happened in a certain order. In this case, we can't call LoadListener's nativeError until BrowserFrame's startLoadingResource returns. Otherwise, the failed request will not be removed from the DocLoader's request list. So the page will never finish loading.
A subclass of SurfaceView is created in order to appear like a normal
SurfaceView to jni but can be managed in Java easily. This class implements the
SurfaceHolder.Callback interface in order to notify the native PluginSurface
when the surface changes.
Fix for http://b/issue?id=1979719 : cannot see password in browser
textfield. Show the system's password transformation in a password
field, which can be set to show the text partially or completely,
rather than webkit's version, which never shows the text.
Install an observer for the Location system setting and
move the Gears permission check to a slightly earlier time.
Move the logic into a separate manager class.
Also delete some whitespace and fix some style issues.
Merge commit '3bb692338fed7f34f010398fe8b831d0de22c6e8'
* commit '3bb692338fed7f34f010398fe8b831d0de22c6e8':
Keep Gears permissions in sync with system location settings.
When the user edits text in a textfield, we increase a generation
number so we can mark changes from webkit to be out of date. With
this change, update webcore's notion of the text generation number
in deleteSelection and replaceTextfieldText, in addition to
passToJs. Requires a change in external/webkit.
Merge commit '79ec07b333f8982ee83de8eeb0b1927a6cb112ed'
* commit '79ec07b333f8982ee83de8eeb0b1927a6cb112ed':
Fixes#1444844. Set a maximum fling velocity in scrollable views.
Add the ViewManager class to handle child views within a WebView. This class
attaches and removes the views in the UI thread. It also scales the layout
params based on the scale of the WebView.
