Android: Provide a smaller list  of files to be pushed for content_browsertests.

BUG=138275

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192656 0039d316-1c4b-4281-b951-d872f2087c98
Fix large mis-paint when resizing windows aura chrome

See bug attached for screenshots

The CL does two things:
- Disables the resizer lock, so that UI bits can go ahead of content bits
- Janks (blocks) the UI thread until the compositor has flushed / finished
the pending commands.

This makes the mis-draw way less, up to one frame behind, which at my regular
mouse speed of 1.2 pixels / ms comes out to 20 pixels of whiteout.


BUG=177115
TEST=none
Review URL: https://codereview.chromium.org/13604007

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192657 0039d316-1c4b-4281-b951-d872f2087c98
Add more URL to the whitelist in source_index.py

Context: https://groups.google.com/a/chromium.org/forum/?fromgroups=#!topic/chromium-dev/1aTQc4fd-rk

BUG=

Review URL: https://chromiumcodereview.appspot.com/13529016

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192658 0039d316-1c4b-4281-b951-d872f2087c98
Merge ui::Layer's concept of position with cc::Layer's

This makes ui::Layer use cc::Layer::SetPosition for setting
its position, instead of baking its position into the
transform that's set on the cc::Layer. This means that a
change to a ui::Layer's bounds no longer affects the
transform set on the cc::Layer, and hence bounds animations
no longer conflict with threaded transform animations.

BUG=170219,226326


Review URL: https://chromiumcodereview.appspot.com/13725015

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192659 0039d316-1c4b-4281-b951-d872f2087c98
MacTerminateOnHeapCorruption shouldn't leak the OOM killer into the shared test context.

BUG=196349
TEST=SecurityTest.NewOverflow and CallocOverflow should not fail as part of a long test run


Review URL: https://chromiumcodereview.appspot.com/13529020

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192660 0039d316-1c4b-4281-b951-d872f2087c98
Aura: Make compositor_unittests work with --ui-enable-threaded-compositing

Check that a draw occured, rather than just that it was scheduled. Verify that CompositorDelegate is not called if compositing is threaded.

BUG=173417
TEST=compositor_unittests --ui-enable-threaded-compositing


Review URL: https://chromiumcodereview.appspot.com/13555004

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192661 0039d316-1c4b-4281-b951-d872f2087c98
Use java_apk.gypi for gtest apks

Currently, normal APKs and instrumentation APKs are both built using
java_apk.gypi (which includes all kinds of new hotness). Native
unittest APKs, though use apk_test.gypi and thus the complicated
native_test_apk.xml and Android's Ant build.xml. That is bad.

This change updates apk_test.gypi to include java_apk.gypi and so
brings these two ways of building APKs into alignment. It also very
slightly updates the configurability of java_apk.gypi and
apk-package.xml.

There are still a couple of targets in WebKit that use
generate_native_test.py and native_test_apk.xml directly that need to
be updated to use apk_test.gypi before those two scripts can be
simplified/removed.

BUG=158821


Review URL: https://chromiumcodereview.appspot.com/13564003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192662 0039d316-1c4b-4281-b951-d872f2087c98
cros: Disallow opening new tab/popup in app mode.

BUG=178469


Review URL: https://chromiumcodereview.appspot.com/13638012

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192663 0039d316-1c4b-4281-b951-d872f2087c98
Search & replace of -webkit-box-shadow -> box-shadow

Webkit has supported unprefixed box-shadow since December 2010:
http://peter.sh/2010/12/no-more-delete-unprefixed-box-shadows-and-a-have-happy-new-year/

BUG=


Review URL: https://chromiumcodereview.appspot.com/12842013

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192665 0039d316-1c4b-4281-b951-d872f2087c98
sync: Refactor job ownership in SyncScheduler

This change separates the tracking of what work needs to be done from
the decision of when to do it.  Prior to this change, SyncSessionJobs
were owned either by Closures posted to the sync thread's message loop,
or held temporarily in unscheduled_nudge_storage_, a member of the
SyncScheduler.  Following this change, there can be only two jobs in
existence, and they will be referenced only by the scoped_ptr members of
SyncScheduler named pending_nudge_job_ and pending_configure_job_.

This change, along with some previous changes to the way we schedule
tasks, makes it possible to simplify the job "saving" logic.  Jobs with
purpose == NUDGE are saved by assigning them to pending_nudge_job_ or
coalescing them with the existing pending_nudge_job_.  Jobs with purpose
== CONFIGURE are never coalesced, and can be saved in the
pending_configure_job_ member.  These changes allow us to make
SyncSessionJob::Clone() obsolete.

The logic in ScheduleNudgeImpl() has been updated to take advantage of
the fact that the pending job is much easier to find now.  It should now
be much better at coalescing its sources.  In other words, there will be
less scenarios where it can drop notification hints.  However, there are
still some cases in DecideOnJob() that may induce it to drop hints
unnecessarily.

The scheduling logic has been modified, too.  We've removed support for
the nudge while in an exponential backoff interval.  This makes it
possible to track the next wakeup time using a single timer, since the
wakeup event will be one of:
- The end of a throttled interval
- An end-of-backoff-interval retry
- A scheduled nudge
and these scenarios are now mutually exclusive.

BUG=175024

Review URL: https://chromiumcodereview.appspot.com/13422003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192666 0039d316-1c4b-4281-b951-d872f2087c98
Fix uninitialized POD member |use_custom_insets_| to fix regression and coverity
issue somewhere (I'm sure).

R=sky@chromium.org
BUG=224259


Review URL: https://chromiumcodereview.appspot.com/13533021

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192667 0039d316-1c4b-4281-b951-d872f2087c98
Add provision_devices step to all Android testers.

This CL adds --auto-reconnect as an option to the
provisioning script. This option is not being used.

BUG=164180


Review URL: https://chromiumcodereview.appspot.com/13649010

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192668 0039d316-1c4b-4281-b951-d872f2087c98
Implement the host side of the PPB_PDF proxy.

TBR=brettw@chromium.org


Review URL: https://chromiumcodereview.appspot.com/13004012

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192669 0039d316-1c4b-4281-b951-d872f2087c98
Use NTP time for video frame timestamp.
Add tracing for capture timestamps.

BUG=225209


Review URL: https://chromiumcodereview.appspot.com/13554003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192670 0039d316-1c4b-4281-b951-d872f2087c98
cc: Make animations tick regardless of drawing.

The compositor should tick and finish animations even if it is not
drawing anything. It can not draw for various reasons:
1) The tab is backgrounded.
2) CanDraw() is false for any of its reasons.
3) PrepareToDraw() fails due to checkerboarding.
4) There is no damage on the screen to draw.

Currently the problems are:
- When backgrounded, the animations are ticked but their states are not updated.
- When CanDraw() is false, we don't draw, and animations just stop ticking.
- If we stop drawing when we damage the screen, we tick animations, but don't
  update animation state since this happens in DrawLayers().

To solve these problems, I've moved the animation control more explicitly out
of LayerTreeHostImpl. The proxy already calls Animate(). Now it will also call
UpdateAnimationState(). It always does this after calling Animate() regardless
if drawing or not.

Secondly, the missing UpdateAnimationState() call is added to the OnTimerTick
for background animation ticking.

We enable background ticking only when we change visibility, currently. But
when CanDraw() is false, we don't draw and thus don't tick animations. So
instead we add to LayerTreeHostImpl a UpdateBackgroundAnimateTicking() method.
We call this always after calling Animate() since that can remove animations -
it's something Animate() used to do. And we also call this:
a) After a commit - this could add new animations, or change visibility.
b) After changing CanDraw()'s state.

However, when PrepareToDraw() is false, we do not want to start new animations
so we let animations finish without starting new ones. This is verified by 
the LayerTreeHostAnimationTestCheckerboardDoesntStartAnimations test.

This is covered by adding single-thread mode to all the animation unit tests
(except those that call SetNeedsAnimate() which is not legal in single thread
mode). Also by new tests:
LayerTreeHostAnimationTestRunAnimationWhenNotCanDraw.RunSingleThread
LayerTreeHostAnimationTestRunAnimationWhenNotCanDraw.RunMultiThread
LayerTreeHostAnimationTestRunAnimationWhenNotVisible.RunSingleThread
LayerTreeHostAnimationTestRunAnimationWhenNotVisible.RunMultiThread
LayerTreeHostAnimationTestCheckerboardDoesntStartAnimations.RunMultiThread

Added scheduler tests:
SchedulerStateMachineTest.ReportIfNotDrawing
SchedulerStateMachineTest.ReportIfNotDrawingFromAcquiredTextures

R=ajuma@chromium.org
BUG=222915

Review URL: https://chromiumcodereview.appspot.com/13613003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192671 0039d316-1c4b-4281-b951-d872f2087c98
media: Support VP9 in media source.


Review URL: https://chromiumcodereview.appspot.com/13652011

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192672 0039d316-1c4b-4281-b951-d872f2087c98
Refactor ChunkDemuxer code so all source state is in a SourceState class.


BUG=172688

Review URL: https://chromiumcodereview.appspot.com/13652012

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192673 0039d316-1c4b-4281-b951-d872f2087c98
Add comment explianing memory policy on Mac.

TBR=nduca@chromium.org
BUG=

Review URL: https://chromiumcodereview.appspot.com/13655002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192674 0039d316-1c4b-4281-b951-d872f2087c98
cc: Moved contents_swizzled out of TileManager

Drawing info now has everything it needs to calculate
the contents_swizzled instead of it being set in
TileManager in two spots.

BUG=225804


Review URL: https://chromiumcodereview.appspot.com/13665003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192675 0039d316-1c4b-4281-b951-d872f2087c98
cc: Use refresh_rate from LayerTreeSettings

We use it in compositor_unittests to have a faster refresh rate during test
(when WGC3D is mocked out --- no hardware vsync).

TEST=cc_unittests pass, compositor_unittests --ui-enable-threaded-compositing are faster

Review URL: https://chromiumcodereview.appspot.com/13674006

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192676 0039d316-1c4b-4281-b951-d872f2087c98