This patch provides all of the plumbing but only provides the error event,
used when we fail to connect to the device's sensors. Connection to the
sensors is coming in a later patch.
Change-Id: I322297d70570425b19917712e63e815651ceacc2
This makes the zoom animation much more smooth. With previous dynamic
viewport, the animation jumps because of viewport adjustment and big
screen.
Also the viewport width is changed from 800 to 1040 to better suit
the tablet device. It's the middle point of 1280 and 800.
The text reflow re-alignment for non-double-tap zoom is disabled for
tablet, since most of the time the reflow has no effect.
issue: 2919307
Change-Id: I74493df6408291c24ef8511512d7ed0b81bf507a
Bug: 2582455
A corresponding webkit change eliminates the rest of the calls
to change the active and focused state of the focus controller.
Change-Id: I18868b7480ba5daae71375d109d5a721ecf22b4d
sJavaBridge may not exist by the time onWindowFocusChanged is called.
To avoid an NPE, just static methods that modify a global field.
JWebCoreJavaBridge is a global object anyway so using a static field
will be fine. To avoid any garbage collection issues, store the
WebView in a WeakReference.
Bug: 2894682
Change-Id: I73de9237ddbbdc55841a9b2639437e26856439c8
The stale value will happen when rotating the large screen and make
double tapping not behave well.
Alternatively, shall we get rid of this variable?
issue: 2919307
Change-Id: I2d71e547db42adeb5674accbf79fb0e7fc587fcd
This happens when default and overview scales have not much difference.
This solves the double tap issue for large screen devices,
where overview and default scale are the same. The code works well
with phone device as well.
Change-Id: Iac7f66369d58a152de8de7025b326d1672da30d4
Sometimes clearTextEntry is called when mWebTextView is not
being used. In those cases, we still want to hide the soft
keyboard, since the user is no longer attempting to type.
Bug: 2835685
Change-Id: I4e8d4bc60b23028e2840d6205caf13699bce6031
Complex characters like chinese are sent via the onKeyMultiple()
callback. The WebView passes these characters to Webkit so that
non-text inputs (e.g. plugins) can process them.
Change-Id: I159c4a404c195b60cc7f63ef4bff0aa80db96c3f
http://b/2900114
(Said table is the very same data that used to be, but pushed further down
the dependencies so that it can be shared with java.net.URLConnection, so
the two classes' equivalent methods return the same results.)
Bug: 2422917
Bug: http://code.google.com/p/android/issues/detail?id=10100
Change-Id: Ic4e80c2fede22671e825d569f349e4329dcf01ea
Detect two fingers close together and enter drag layer mode. Add a
few checks for this mode (mostly to not change the WebView's scroll
position).
Bug: 1566791
Change-Id: I019bb36479884a51c7ca046ca40c05f7c5706b22
one SkLayer tree to get ready for GL rendering.
Now UI holds its copy of SkLayer tree. The top node
is BaseLayerAndroid which has the PictureSet as its
content.
There is a matching change in external/webkit.
the touch incon url instead. The DownloadTouchIcon class will handle the case that
this file does not exist on the server.
Change-Id: I8ab8fd65b571584d7b648af72c568f0b01c2dcaf
has marked itself as being an installable web app. Default implementation
in the WebChromeClient does nothing.
Requires an external/webkit change.
b/2766917
Change-Id: I7aae1b097f866e3d1c6c6a7a31a55bb12ff6a441
Our use of web settings does not specify the maximum image size,
although we have some hard-coded values used when decoding the
image. For defective images, the hard-coded values are not enough,
since we may exceed memory in the decoder before the limit is
reached.
Pass along our limits to the decoder, and respect any limits
set by the caller.
companion change in external/webkit
Change-Id: Iabd78165390dddce917f637bd3263b83f9b4aa56
http://b/2689053
This CL also includes some minor changes to the ZoomManager that
make the manager easier to test as well as fix some uncovered issues.
Change-Id: I66a84d70ee75e765ccf9cccb2d123757a9470f93
In WebView:
- Remove the select mode, so that while text is selected,
the view may respond to scroll or zoom gestures.
- Remove the getFindIsUp() method -- let the host application
track if the dialog is visible.
- Map long press to select text if the host application does
not already intercept it.
- Draw find 'extras' during zoom animation.
- Draw select 'extras' during animation and scrolling as well.
- Distinguish between selecting text and pressing a shift key
(the shift key is still a possible select text shortcut)
- Add more public (but hidden) interfaces: setUpSelect, selectAll, etc.
In WebChromeClient, add interfaces to allow WebView to tell the host
application that selection has started or finished. A long press on
a part of the view that does not trigger a host context menu may
start the selection (if text is underneath the press), and clicking
the trackball or tapping away from the current selection may
end the selection.
Companion changes in external/webkit and packages/apps/Browser
Change-Id: I81f549181249c38d8d4c10fd7064f513d11318fa
http://b/262451
This isn't the perfect solution as any calls into WebViewDatabase will block
until initialization completes. It is better than the current model which
blocks when creating the WebViewDatabase.
In order to get a perfect solution, we would need to do initialization in the
background and have a way to interact with the database during initialization
that would not block.
Bug: 2721802
Change-Id: Ibbaf7f97926128de6534fbf2148452099766c6b7
Grab the WebViewCore immediately so that if the Tab is destroyed, we have the
old WebViewCore object and can return the BrowserFrame.
Bug: 2733004
Change-Id: Ic3e4c5417f2165f412f60f05aea3ed403d8cecfd
