Fix buffer range estimation for large files.

There is a potential overflow in TimeForByteOffset_Locked
when estimating the time offset for a given byte offset.

BUG=326201

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@239113 0039d316-1c4b-4281-b951-d872f2087c98
Support KitKat accessibility APIs.

The KitKat API adds a lot more accessibility data that can
be exposed from Android applications. This implements
all of them and updates test expectations.

In addition, it exposes the same properties on JellyBean
via a Bundle, allowing accessibility services a way to access
this information even without KitKat, just without the clean
API.

BUG=none

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@239114 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 239113
input: Add some touch-event related browser-tests.

The tests added verify that the touch-events are acked correctly, for
both single and multi-touch points. The tests run both with and without
the compositor thread event-handler, to ensure that the event acks are
the same in both cases.

BUG=321457
R=jdduke@chromium.org
TBR=jochen@chromium.org for content_tests.gypi

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@239115 0039d316-1c4b-4281-b951-d872f2087c98
Cleanup: rename tracked_by_workspace to is_dragged
 This flag was used for workspace, but now only used to indicate that a window is dragged.

* Removed two tests in WorkspaceControllerTest that are no longer useful (no real usage scenario associated with them)
* Set is_dragged flag at the begining and end of drag. This is consistent with what tab_drag_controller does.
* Removed MaybeSnapToEdge as this is no longer necessary (as discussed offline)

BUG=none

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@239116 0039d316-1c4b-4281-b951-d872f2087c98
IndexedDB: Forced close should cancel pending timers

Missing case in the "lazy close backing store" logic. If all connections
were closed normally, followed by a force-close, the force-close never
made it to the factory since there were no connections, so the backing
store would still close lazily. This would prevent deletion of browsing
data.

BUG=309015
R=dgrogan@chromium.org,alecflett@chromium.org

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@239117 0039d316-1c4b-4281-b951-d872f2087c98
MostVisitedSites listens for updates to most visited sites.

This adds a C++ counterpart to the MostVisitedSites Java class. The C++
class listens for updates to the most visited sites and calls a Java
callback when the list changes.

BUG=318092
NOTRY=true
R=tedchoc@chromium.org

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

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