Trim more dead code from webkit/support/

Review URL: https://codereview.chromium.org/23264025

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@230794 0039d316-1c4b-4281-b951-d872f2087c98
Build mojo_shell on Android

This CL contains a basic skeleton for building mojo_shell on Android. I've
introduced a mojo_shell_apk target that builds an APK that prints a simple
message and loads libmojo_shell.so. Currently libmojo_shell doesn't do
anything. A future CL will do write up something interested on the C++ side.

R=bulach@chromium.org, darin@chromium.org, joth@chromium.org

Review URL: https://codereview.chromium.org/38993002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@230795 0039d316-1c4b-4281-b951-d872f2087c98
Collect metrics data from service process.

MetricsService in browser process sends request for histograms to service process if service is running. Request is called in parallel with requests to other browser child processes.

Service process still loses all data collected after browser process is gone.

BUG=305019

Review URL: https://codereview.chromium.org/26779002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@230796 0039d316-1c4b-4281-b951-d872f2087c98
IndexedDB: Ensure backing store is released on forced-close

r222626 made Chromium hold backing stores open for a short grace
period after closing so that the common open/close/open pattern would
be fast. That patch was buggy - the database would still have a 
reference to the backing store, short-circuiting the accounting.
The backing store files would still be deleted, though. However...

r228768 http://crrev.com/27048003 made Chromium use LevelDB's
DestroyDB function, which tries to grab a lock. In the above case it
would fail.

This change correct the order in which the database releases its
backing store reference, and handles the case where the timer is
interrupted by context destruction (e.g. shutdown).

BUG=308739

Review URL: https://codereview.chromium.org/27536013

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@230797 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 230797
Avoid creating two resizers for two-finger drag. This CL is trying to avoid creating two separate WindowResizer instances that are now created in both ToplevelWindowEventHandler and TwoFingerDragHandler in the following scenario:
 . Start dragging a window with a touch.
 . Drag a bit, then add a second finger (touching the caption).
 . Continue dragging.
 . Release both fingers.
In this scenario a WindowResizer is first created by ToplevelWindowEventHandler::OnGestureEvent(ET_GESTURE_SCROLL_BEGIN) and then a second instance gets created by TwoFingerDragHandler::ProcessGestureEvent(ET_GESTURE_BEGIN) when a second finger touches down. This scenario is probably an oversight but was not causing too many problems other than occasional window moving jitter. However with the docked windows introduction the DockedWindowLayoutManager currently assumes a single window resizing operation and breaks when FinishDragging is called for the second time.

Additional complication is when this one-two-finger gesture is used to drag a tab out of a browser. In this case The first resizer is created when ToplevelWindowEventHandler::RunMoveLoop is invoked and not as a result of a gesture (not in ToplevelWindowEventHandler::OnGestureEvent). I have added an accessor to the current window resizer to wm::WindowState and use it to determine if a new resizer needs to be created.

I have corrected the state model in TwoFingerDragHandler to always Complete or Revert a drag once it started. This takes care of scenarios when drags start with one or two fingers and get stopped when more fingers are added.

BUG=305730
TEST=interactive_ui_tests --gtest_filter=*TabDragControllerTest*DetachToOwnWindowTwo*/1
TEST=ash_unittests --gtest_filter=*SystemGestureEventFilterTest.TwoFingerDragDelayed*
TEST=ash_unittests --gtest_filter=*SystemGestureEventFilterTest.ThreeFingerGestureStopsDrag*

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=230671

Review URL: https://codereview.chromium.org/28043002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@230798 0039d316-1c4b-4281-b951-d872f2087c98
replace setIsOpaque (deprecated) with explicit SkAlphaType

BUG=
R=enne@chromium.org, jam@chromium.org, jamesr@chromium.org, thakis@chromium.org

Review URL: https://codereview.chromium.org/37233002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@230799 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 230799