GitLab

We had incorrectly obmitted an update to the opacity when we first start
sending frames. This CL adds that necessary call, and also neatens up
the logic to update opacity and rotation, making the effect of these
calls clearer.

Bug: 893056
Change-Id: I1b6edb4292f1a3a25aa22b61e82c20381d395eb7
Reviewed-on: https://chromium-review.googlesource.com/c/1275525
Commit-Queue: CJ DiMeglio <lethalantidote@chromium.org>
Reviewed-by: Emircan Uysaler <emircan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602112}

Note that this refactoring is not entirely without side effects.
In some cases we will do a better job of reading the color space from the container.
For VP9, we will no longer be using the resolution to guess color spaces.

media: :ColorSpace is deprecated.
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Change-Id: I6ebd5b6f9a5fc579274032e17f84c53f1c63f6ad
Reviewed-on: https://chromium-review.googlesource.com/c/1277838
Commit-Queue: Fredrik Hubinette <hubbe@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Reviewed-by: Jesse Doherty <jwd@chromium.org>
Reviewed-by: Frank Liberato <liberato@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602111}

Fixed the received_bytes field for offline pages to OfflineItem conversion.
Also added all the missing fields to the conversion unit tests.

Bug: 897841
Change-Id: I823a84bc36a9d07c2f955f756c91412d22fa59ae
Reviewed-on: https://chromium-review.googlesource.com/c/1294404
Commit-Queue: Shakti Sahu <shaktisahu@chromium.org>
Reviewed-by: Carlos Knippschild <carlosk@chromium.org>
Reviewed-by: Shakti Sahu <shaktisahu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602110}

This fixes the bug where we see two titlebars for PWA windows, and
fixes a longstanding TODO to add needed parameters to the
CreateWindowParams structure.

Update the mojo struct CreateWindowParams to include parameters used
by the various NativeWidgetMac::CreateNSWindow overrides. Include in
these parameters a WindowClass parameter to indicate the subclass of
NativeWidgetMacNSWindow to use.

Add the overrideable method NativeWidgetMac::PopulateCreateWindowParams
to populate the CreateWindowParams structure.

Add plumbing in BrowserWindowFrame to call back into the browser process
to get the overridden titlebar height. Add similar plumbing to
BrowserNativeWidgetWindow to implement _handleFocusToolbarHotKey. With
this in place, BrowserWindowFrame et al no longer have any dependencies
on browser-process classes.

Move BrowserWindowFrame and NativeWidgetMacFramelessNSWindow from
//chrome/browser/ui/views/ over to //ui/views_bridge_mac.

Bug: 897866
Change-Id: I04d9dd57d2bb98f98899349f2810198103e286b8
Reviewed-on: https://chromium-review.googlesource.com/c/1295251Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Reviewed-by: ccameron <ccameron@chromium.org>
Commit-Queue: ccameron <ccameron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602109}

Bug: 894043
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Id777b3e30ce6f9d84b2935630559c62a251d07af
Reviewed-on: https://chromium-review.googlesource.com/c/1289749
Commit-Queue: Aaron Krajeski <aaronhk@chromium.org>
Reviewed-by: Fernando Serboncini <fserb@chromium.org>
Reviewed-by: Robert Kaplow (sloooow) <rkaplow@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602108}

The bug here is that we were calling XRCanvasInputProvider::Stop() in
our destructor (ie - during garbage collection), where we should not
consume gc objects, since they may already be destroyed.

The fix is simply to not call Stop at all during destruction. If the
XRSession terminates, Stop() will be called through a different path.
Otherwise, if XRCanvasInputProvider is destroyed, it means the canvas
must also be destroyed because the canvas holds a strong reference to
XRCanvasInputProvider.

BUG=894718

Change-Id: Ic339769fb0207e6ac569709703760245c72974d1
Reviewed-on: https://chromium-review.googlesource.com/c/1294726Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Brandon Jones <bajones@chromium.org>
Commit-Queue: Bill Orr <billorr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602107}

All of these tests now pass.

BUG=889101,891489
TEST=test only change

Change-Id: I3f71af680c57c6e4c584156d098fad07f351b27b
Reviewed-on: https://chromium-review.googlesource.com/c/1297059Reviewed-by: Jun Mukai <mukai@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602106}

MD Refresh style was missing.

Bug: 897904
Change-Id: I89eff26e796db9c0c5b0e090c08fd2c00f419e17
Reviewed-on: https://chromium-review.googlesource.com/c/1295316Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602105}

* Removes the log state CHANNEL_CLOSING, which is actually not a log state.
* Adds channel_is_closing_ flag instead.

This way, it's possible to check in WebRtcLoggingHandlerHost::StoreLogInDirectory and WebRtcLoggingHandlerHost::DoUploadLogAndRtpDumps if the log is in closed state or not when channel is closing to avoid multiple upload/store attempts.

Multiple stores/uploads could happen if channel is closing and a store or upload operation has been issued around the same time.

Bug: 807547
Change-Id: I5e41d5a02095044582c06037d440d22a2edc0be2
Reviewed-on: https://chromium-review.googlesource.com/c/1296538Reviewed-by: Tommi <tommi@chromium.org>
Commit-Queue: Henrik Grunell <grunell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602104}

histogram_functions and single_sample_metrics

Specifically: 
Change-Id: Ic60fd12e6d6b464240cc09398cd2faac02550770
Reviewed-on: https://chromium-review.googlesource.com/c/1296324Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Fernando Serboncini <fserb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602103}

We'd like to be able to measure the impact of Surface Synchronization. To do
this we want to know how long elapses from LocalSurfaceId allocation until the
Surface is embedded by Viz.

This change has both ParentLocalSurfaceIdAllocator and ChildLocalSurfaceIdAllocator
also save the allocation time.

Then adds piping so that the allocation time is forwarded all the way to Viz.
Where the delta is calculated.

Bug: 655231
TEST: Manual testing of histograms reports on Android, Windows, Mac, Linux, Chrome OS.
And running all associated unit tests.

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Ie3eb35cfe6b5e68b1c113824e3bc79ea99a989e8
Reviewed-on: https://chromium-review.googlesource.com/c/1281231
Commit-Queue: Jonathan Ross <jonross@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Reviewed-by: Jesse Doherty <jwd@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Fady Samuel <fsamuel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602102}

Add the "os-wow64" attribute to the metadata.
Example:
 os-arch: "x86_64",
 os-name: "Windows NT",
 os-version: "10.0.16299",
 os-wow64: "enabled",

On windows, it's possible to run a 32-bit version of chrome on a 64-bit
arch. Unfortunately, there is no way to differentiate traces from these
two scenarios.

This is useful for slow-reports since stacksampling doesn't work in
32-bit.

R=ssid@chromium.org

Change-Id: I24c3ba21c9de9a93eb1fb6e8b19e4d34d11120e1
Reviewed-on: https://chromium-review.googlesource.com/c/1296812
Commit-Queue: Etienne Bergeron <etienneb@chromium.org>
Reviewed-by: ssid <ssid@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602101}

Backgrounds must paint under the border when the border is not solid
even if the border color is opaque.

Bug: 898247
Change-Id: I1eed15b9c17b22cd0ddba65073638a1f8a16c30d
Reviewed-on: https://chromium-review.googlesource.com/c/1297173Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602100}

This is a refactor CL and it should not change any existing UI.

The affected pages are as follows:
- On startup site entry in chrome://settings
- chrome://settings/siteData
- chrome://settings/searchEngines
- chrome://settings/content/zoomLevels
- chrome://settings/handlers
- chrome://settings/content/usbDevices
- chrome://settings/content/all
- All the pages in "Content settings" that use site-list-entry, such as
  chrome://settings/content/paymentHandler

Bug: 890118
Change-Id: I35e00406999cf30012db557b10dd418cef67a69d
Reviewed-on: https://chromium-review.googlesource.com/c/1277995
Commit-Queue: Yue Cen <rsgingerrs@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602099}

When network service is enabled, data saver site-breakdown gets the
services and downloads data usage from DataUseMeasurement.

Bug: 808498

Change-Id: I9ec7c98e67b5e8db531a345de1f5f89824efa807
Reviewed-on: https://chromium-review.googlesource.com/c/1295729Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Commit-Queue: rajendrant <rajendrant@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602098}

When full browser is not launched, we should create InProgressDownloadManager
to handle all the operations.

BUG=842245

Change-Id: I2687000288c9459c8df8099ff4721a2b6755d96e
Reviewed-on: https://chromium-review.googlesource.com/c/1297237
Commit-Queue: Min Qin <qinmin@chromium.org>
Reviewed-by: Xing Liu <xingliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602097}

This change adds several methods to PriorityQueue allowing comparison of
Pointer positions, advancing a Pointer towards the beginning of the
queue, and finding the first element matching a predicate. In addition,
unique_ptr values are now supported.

Bug: None
Change-Id: If00616cabed9a30f8b8743335d63f0231442b3fe
Reviewed-on: https://chromium-review.googlesource.com/c/1294297Reviewed-by: Matt Menke <mmenke@chromium.org>
Commit-Queue: Lily Chen <chlily@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602096}

https://skia.googlesource.com/skia.git/+log/c88cc779efdb..07055a3ee7ce


git log c88cc779efdb..07055a3ee7ce --date=short --no-merges --format='%ad %ae %s'
2018-10-23 reed@google.com update dox for vertical-text demise
2018-10-23 jvanverth@google.com Check for valid initialization of ReflexHash
2018-10-23 mtklein@google.com add a few more ways to convert images to imgcvt
2018-10-23 brianosman@google.com Hoist color space xform creation out of GrTextureProducer
2018-10-23 jvanverth@google.com Check for finite segments when inserting into ActiveEdgeList
2018-10-23 pirama@google.com Add back -Wover-align


Created with:
  gclient setdep -r src/third_party/skia@07055a3ee7ce

The AutoRoll server is located here: https://autoroll.skia.org/r/skia-autoroll

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel

BUG=chromium:867813
TBR=brianosman@chromium.org

Change-Id: Ic019cb3732c7d0131e372f8bb90dcead78146935
Reviewed-on: https://chromium-review.googlesource.com/c/1297014Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Mike Klein <mtklein@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602095}

It is not a general purpose substitute for the default std::string
constructor. Do the same for base::EmptyString16() and base::string16().

Change-Id: I405b94dba0a761ba12bc3e40f712142ba3886d9b
Reviewed-on: https://chromium-review.googlesource.com/c/1295312
Commit-Queue: Lei Zhang <thestig@chromium.org>
Reviewed-by: Evan Stade <estade@chromium.org>
Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602094}

Findit suspects that it was caused by a v8 update. TBR owners for
further investigation.

TBR=kozy@chromium.org
NOTRY=true

Bug: 898062
Change-Id: I9a77f0d40f73d57f0fd54588ffd96a74d98dd2c1
Reviewed-on: https://chromium-review.googlesource.com/c/1297392Reviewed-by: Yi Gu <yigu@chromium.org>
Commit-Queue: Yi Gu <yigu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602093}

This CL adds the step-indicator element that would show dots of different
colors. The welcome_app element is responsible for setting the total and
active index for each module's step-indicator.

Bug: 874146
Change-Id: I7813d6d64f57759ceab5ce4b60e59a45db2dc161
Reviewed-on: https://chromium-review.googlesource.com/c/1285309
Commit-Queue: Scott Chen <scottchen@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Reviewed-by: Hector Carmona <hcarmona@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602092}

TBR=twellington@chromium.org

Bug: 898165
Change-Id: Id519840866ae56a2ee795ee73ba505a1a3645559
Reviewed-on: https://chromium-review.googlesource.com/c/1297057Reviewed-by: Becky Zhou <huayinz@chromium.org>
Commit-Queue: Becky Zhou <huayinz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602091}

To prevent lag and stuttering, limit hittests on mousemove events to
50ms = 20Hz.

Bug: 853581
Change-Id: I28f1f142df4c96be9c95d87cfd69c052d776a870
Reviewed-on: https://chromium-review.googlesource.com/c/1289297
Commit-Queue: James Wallace-Lee <jamwalla@chromium.org>
Reviewed-by: Katie Dektar <katie@chromium.org>
Reviewed-by: David Tseng <dtseng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602090}

This reverts commit 0602efcc.

Reason for revert: 

We don't actually want to stop scripts when the overlay is tapped. 

Original change's description:
> [Autofill Assistant] Initial impl of OnClickOverlay
> 
> Bug: 806868
> Change-Id: I22b21ccbb386e89d5ac2b0cd8d80e53cc14b447a
> Reviewed-on: https://chromium-review.googlesource.com/c/1282362
> Commit-Queue: Ganggui Tang <gogerald@chromium.org>
> Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#599980}

TBR=rouslan@chromium.org,gogerald@chromium.org

# Not skipping CQ checks because original CL landed > 1 day ago.

Bug: 806868
Change-Id: Id8b55687d2faead941f82ce0c4889606539dd9c6
Reviewed-on: https://chromium-review.googlesource.com/c/1296602Reviewed-by: Stephane Zermatten <szermatt@chromium.org>
Reviewed-by: Ganggui Tang <gogerald@chromium.org>
Commit-Queue: Ganggui Tang <gogerald@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602089}

Bug: 898286
Change-Id: I4f3b40696968aabe712a95424d2bb725d35ef4e1
Reviewed-on: https://chromium-review.googlesource.com/c/1297252Reviewed-by: Miguel Casas <mcasas@chromium.org>
Commit-Queue: Emircan Uysaler <emircan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602088}

I helped start this, so I guess it's fair that I also do the reviews.

BUG=

Change-Id: Ic3622f28207380159626903ffbbe34f60bd73b43
Reviewed-on: https://chromium-review.googlesource.com/c/1297350
Commit-Queue: Robert Liao <robliao@chromium.org>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602087}

Previously the generated jni method name for org.chormium.jni_example.foo()
would collide with the name org.chromium.jni.example.foo() because . would be
replaced with _, but _ in class/package/method names were not escaped.

Change-Id: I3911a278c1b5d67269e4c746e114262c4fb36629
Bug: 898261
Reviewed-on: https://chromium-review.googlesource.com/c/1297075Reviewed-by: agrieve <agrieve@chromium.org>
Reviewed-by: Eric Stevenson <estevenson@chromium.org>
Commit-Queue: Aiden Benner <abenner@google.com>
Cr-Commit-Position: refs/heads/master@{#602086}

Bug: 896828
Change-Id: I6376b04e01e962e45e1b1218097e8446d26dc3b3
Reviewed-on: https://chromium-review.googlesource.com/c/1289511Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602085}

Close touch selection ui in Mash on events outside the browser window.
(global pre-target handlers are not supported in window service clients)
This follows and refines the new pattern in TouchSelectionControllerImpl.

Bug: 896973, 884394
Test: Text touch selection ui hides as expected in Views and Content.
Change-Id: Iedba63a7ce5d5f70f9763cf540d26ee69cee5f28
Reviewed-on: https://chromium-review.googlesource.com/c/1292274
Commit-Queue: Michael Wasserman <msw@chromium.org>
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602084}

This races with session initialization and can cause display prefs to
fail to be saved properly. Exposed pretty consistently when making
subtle changes to Mojo dispatch timing.

The fix forces DisplayPrefs to wait for the first user session to be
started if a storage attempt happens prior to that.

Bug: 872074
Change-Id: I40f9070b6a6421e8fa3bef2da44ab9e854d3d3c8
Reviewed-on: https://chromium-review.googlesource.com/c/1296547Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Commit-Queue: Ken Rockot <rockot@google.com>
Cr-Commit-Position: refs/heads/master@{#602083}

This CL is based on:
https://chromium-review.googlesource.com/c/chromium/src/+/1292430

Bug: 806868
Change-Id: Ib5f1f7eb55d899161d43d60b685f126c51f0c85a
Reviewed-on: https://chromium-review.googlesource.com/c/1292590
Commit-Queue: Ganggui Tang <gogerald@chromium.org>
Reviewed-by: Stephane Zermatten <szermatt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602082}

When window is hiding, there are several mojo messages are
exchanged and then Ash will pick up the new focused window and
notifies to the client through OnWindowFocused(). If the
OnWindowFocused() happens between SetFocus(nullptr) and its
response, the client will ignore the new focus.

Since SetFocus(nullptr) is anyways ignored on the server,
this means the client shouldn't send SetFocus(nullptr). It should
reset the focus within the client, but it shouldn't propagate
to the server.

BUG=897875
TEST=manually checked, the edits on the tests clarify the case too

Change-Id: I33439664354ee8fad646fe4b96682e6b726a794c
Reviewed-on: https://chromium-review.googlesource.com/c/1296680Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Jun Mukai <mukai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602081}

This CL removes RootWindowController::ActivateKeyboard and
DeactivatteKeyboard and replaces them with calls into
AshKeyboardController, simplifying the relationship.

Bug: 843332
Change-Id: I78cde4b9b22ba1c9406cbc44dc90af41d4ce37bb
Reviewed-on: https://chromium-review.googlesource.com/c/1294691
Commit-Queue: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Reviewed-by: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602080}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/f4c4ce79c2d8..76181e617aa7


git log f4c4ce79c2d8..76181e617aa7 --date=short --no-merges --format='%ad %ae %s'
2018-10-23 hidehiko@chromium.org Update paladin board assignment for bvt-tast-cq.


Created with:
  gclient setdep -r src/third_party/chromite@76181e617aa7

The AutoRoll server is located here: https://autoroll.skia.org/r/chromite-chromium-autoroll

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=chrome-os-gardeners@chromium.org

Change-Id: I295e003e754de5d83be04c06d812fb3165c23ee2
Reviewed-on: https://chromium-review.googlesource.com/c/1297003Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#602079}

This uses some deprecated Intel mesa APIs but isn't actually Chrome OS
specific. Remove it to minimize Chrome OS #ifdefs.

Bug: 898234
Test: compile
Change-Id: I855e734646e0ff7b57150cf9d342156ea5a693aa
Reviewed-on: https://chromium-review.googlesource.com/c/1297239Reviewed-by: Daniel Nicoara <dnicoara@chromium.org>
Commit-Queue: Michael Spang <spang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602078}

If the sampler stoped a thread at prolog of a chrome function, use the
LR register to find the next return address.

BUG=859260

Change-Id: Ic20d793ee11a8b0fe3edc9438c0f12ccc19f487c
Reviewed-on: https://chromium-review.googlesource.com/c/1265560
Commit-Queue: ssid <ssid@chromium.org>
Reviewed-by: Egor Pasko <pasko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602077}

This CL renames AnimationWorkletThread to a new class,
AnimationAndPaintWorkletThread, in preparation for doing off-thread
PaintWorklet. The idea is that both AnimationWorklet and PaintWorklet
will share the same thread, since both do similar operations and we
don't need a separate thread for each.

Bug: 890759
Change-Id: Id9c78fa726ee2c04336ffc824cf9cdff285eed5c
Reviewed-on: https://chromium-review.googlesource.com/c/1286285Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Yi Gu <yigu@chromium.org>
Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602076}

Bug: 896530
Change-Id: Ifb2c9fae46e8a8c0c02d23fd5a3f36cd1a183cff
Reviewed-on: https://chromium-review.googlesource.com/c/1294392
Commit-Queue: Roger Tawa <rogerta@chromium.org>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602075}

The AutoRoll server is located here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


CQ_INCLUDE_TRYBOTS=luci.chromium.try:fuchsia_arm64_cast_audio;luci.chromium.try:fuchsia_x64_cast_audio
TBR=cr-fuchsia+bot@chromium.org

Change-Id: I6afca89e560fcfb120e034541e406c82f6d61d01
Reviewed-on: https://chromium-review.googlesource.com/c/1297015Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#602074}

Bug: 898169
Change-Id: I2cd883b81a111242691b038ff512652e5faa2a94
Reviewed-on: https://chromium-review.googlesource.com/c/1297055Reviewed-by: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602073}