GitLab

Add the "webauthn:virtualAuthenticators" capability. This capability is
supported (i.e. returns true) only on desktop.

See https://w3c.github.io/webauthn/#sctn-automation-webdriver-capability

Bug: chromedriver:3321
Change-Id: Id05b641325e825beca65987b7b66f651325a16a0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2017183
Commit-Queue: John Chen <johnchen@chromium.org>
Reviewed-by: John Chen <johnchen@chromium.org>
Auto-Submit: Nina Satragno <nsatragno@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734715}

This CL converts ApplicationMediaCapabilities mojom interface client
in chromecast to use BrowserInterfaceBroker.

Bug: 936482
Change-Id: I711d4312316d96195f980ac0cc7b3dc1ea786b4c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1957622Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Reviewed-by: Oksana Zhuravlova <oksamyt@chromium.org>
Reviewed-by: Sean Topping <seantopping@chromium.org>
Commit-Queue: Miyoung Shin <myid.shin@igalia.com>
Cr-Commit-Position: refs/heads/master@{#734714}

The order of priority is: allow > allowAllRequests > block >
upgradeScheme > redirect.

This is implemented by including the action in the lower 8 bits of the
priority that is persisted in the flatbuffer ruleset. To make room for
this, the peristed priority is expanded from uint to uint64.

Bug: 1026733
Change-Id: I3207175bd3a92a2bd945ca428f493d1af3252739
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1952284
Commit-Queue: Theodore Dubois <tbodt@google.com>
Reviewed-by: Karan Bhatia <karandeepb@chromium.org>
Reviewed-by: Charlie Harrison <csharrison@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734713}

Bug: 1042474
Change-Id: I6b2f2fa280b6739819fc7e8f4fb266f1e7bb9453
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003616
Commit-Queue: Matthew Mourgos <mmourgos@chromium.org>
Reviewed-by: Manu Cornet <manucornet@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734712}

Sometimes the surface appears to resize to 0x0 when being destroyed.
If this happens and the surface id is invalid at the point where the
surface aggregator replaces the invalid surface with a solid color
quad and that triggers a DCHECK

So just don't emit 0x0 quads at all

Bug: b/147673681
Test: None
Change-Id: Icc89bff8c9b6d21560390285721637bf8cf608f9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2013801
Commit-Queue: Albert Chaulk <achaulk@chromium.org>
Reviewed-by: Daniele Castagna <dcastagna@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734711}

This reverts commit eeb29c79.

Reason for revert: This fix was tested again and was working as intended, and was deemed more maintainable than the alternative solution.

Original change's description:
> Revert "[Autofill Auth] Adding capability to disable WebAuthn UI from Autofill"
> 
> This reverts commit 69671ce5.
> 
> Reason for revert: Tested in Canary, and the flow stops immediately after authentication. Will try to debug this, and possibly just go ahead with the long term solution right away.
> 
> Original change's description:
> > [Autofill Auth] Adding capability to disable WebAuthn UI from Autofill
> > 
> > Providing an option to disable WebAuthn UI from InternalAuthenticatorImpl.
> > 
> > By disabling WebAuthn UI, modal dialogs will stop conflicting between the two
> > components and this will give Autofill full control over the user experience.
> > 
> > Bug: 949269
> > Change-Id: Ibf88cdb0f014c022371546df54d10e2c9eb7bc24
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1948916
> > Commit-Queue: Manas Verma <manasverma@google.com>
> > Reviewed-by: Martin Kreichgauer <martinkr@google.com>
> > Reviewed-by: Jared Saul <jsaul@google.com>
> > Reviewed-by: sebsg <sebsg@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#722230}
> 
> TBR=sebsg@chromium.org,jsaul@google.com,martinkr@google.com,manasverma@google.com
> 
> Change-Id: Iab4507114f3e19e59acddd49ea89244ee7390048
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Bug: 949269
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1955910
> Reviewed-by: Manas Verma <manasverma@google.com>
> Commit-Queue: Manas Verma <manasverma@google.com>
> Cr-Commit-Position: refs/heads/master@{#722571}

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

Bug: 949269
Change-Id: Ib4ca1fc4eb1d0032864385d8c66c926c6e6d1a5a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2017647Reviewed-by: Martin Kreichgauer <martinkr@google.com>
Reviewed-by: Manas Verma <manasverma@google.com>
Reviewed-by: Jared Saul <jsaul@google.com>
Commit-Queue: Manas Verma <manasverma@google.com>
Cr-Commit-Position: refs/heads/master@{#734710}

Newly added static lib dependencies prevent the unittests from loading
on non-desktop Windows skus such as Hololens. The delayloads allow this
to succeed.

Bug: 1045092
Change-Id: Icc9d24ff0a3b4e31895574f6ecac2b5b761aa185
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016664Reviewed-by: Alexander Cooper <alcooper@chromium.org>
Commit-Queue: Cliff Smolinsky <cliffsmo@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#734709}

All events are being sent to the ARC notification window, so we need a special
case to forward click and tap events to the message center widget when the ARC
notification is slid out.

BUG=965603

Change-Id: I7a0c4653c2bb0eef5dbf1c8708f33fa96ee4567e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016282Reviewed-by: Ahmed Mehfooz <amehfooz@chromium.org>
Commit-Queue: Tim Song <tengs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734708}

RenderWidgetHostViewGuest has been removed, so there is no longer a need
to check whether a RWHVAura is related to a guest. We also add a DCHECK
to ensure the view is not a child frame which would make this a bad cast.

Bug: 533069
Change-Id: Ie71f246d3a524865a1217dd4e1521a5c5c60c295
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2017182Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Commit-Queue: Kevin McNee <mcnee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734707}

Change-Id: If7dcc1d250162ac5bd315d163b4f49fc0aa16b61
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016352Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Commit-Queue: John Lee <johntlee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734706}

This change removes the old "CookieStore" flag and adds 2 new flags
"CookieStoreDocument" and "CookieStoreWorker". The APIs are divided
as follows.

CookieStoreDocument:
-'CookieStore': ['get', 'getAll', 'set', 'delete', 'onchange']
-'CookieChangeEvent': ['changed', 'deleted']

CookieStoreWorker:
-'ServiceWorkerRegistration': ['cookies']
-'CookieStoreManager': ['getSubscriptions', 'subscribe', 'unsubscribe']


Change-Id: I8dd3fd8419576a70aae3cf5012d96fb7f8afb2ce
Bug: 1044245
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2008588Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Commit-Queue: Ayu Ishii <ayui@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734705}

This CL ensures that KaleidoscopeWebUIControllerFactory is enabled
before attempting to register it.

Bug: 1044216
Change-Id: I0ed2b42c7bc1264b89a075d06c023463f932a385
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2012834Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Becca Hughes <beccahughes@chromium.org>
Commit-Queue: Tommy Steimel <steimel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734704}

Move strings that belong to OS Settings Personalization section out
of Appearance string section of browser settings string provider, and
into OS settings string provider.

Bug: 967888
Change-Id: Ib96b0635e304a136ebe137916903b6d9ef5bd87f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2013497Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Commit-Queue: Regan Hsu <hsuregan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734703}

Opening the inline settings now triggers another surface created event, which
is not currently expected by the ArcAccessibilityHelperBridge. If the
corresponding tree already exists, then we should just return early.

TEST=manually verified
BUG=1042554

Change-Id: Ic689184f54c4a737ddd35d7ed05e42b09d3c21bf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003197Reviewed-by: David Tseng <dtseng@chromium.org>
Commit-Queue: Tim Song <tengs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734702}

This CL updates implementors of MouseCursorMonitor and
MouseCursorMonitor::Callback in line with
https://webrtc-review.googlesource.com/c/src/+/166560

Bug: 1043325
Change-Id: I24f7d574d4993f73c2a9413600d2d6563159cda3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2013754Reviewed-by: Joe Downing <joedow@chromium.org>
Commit-Queue: Joe Downing <joedow@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734701}

New Rev: 201330a4e7a527dfc6d73bbb3c297562edcf28f8

Change-Id: I8d47c1944a43d1ea96cd572a1ff41ea378ba255b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2017676
Commit-Queue: Johannes Henkel <johannes@chromium.org>
Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734700}

The present CL follows up after [1] which implements functionality where
you can drag an overview window from one display and drop into overview
on another display. The problem is that after you do so with a browser
window and then end overview, the caption buttons (Minimize, Maximize,
and Close) on that browser window may not work. I observe the problem on
a test device (nautilus) but not in the emulator.

[1] https://chromium-review.googlesource.com/c/chromium/src/+/2008237

Bug: 961170
Change-Id: I15f6bcec8116cbe853737682735865a77827d196
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2013866
Commit-Queue: Avery Musbach <amusbach@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734699}

ChildProcessSecurityPolicyTest.HandleExtendsSecurityStateLifetime was
failing because it was triggering citadel enforcements. This change
makes sure the process_id is properly locked so that the test doesn't
fail the citadel check.

Change-Id: I7a94892e090e88fc5915ee7e61e898146cb8716d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2017991
Commit-Queue: Aaron Colwell <acolwell@chromium.org>
Commit-Queue: Alex Moshchuk <alexmos@chromium.org>
Reviewed-by: Aaron Colwell <acolwell@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Auto-Submit: Aaron Colwell <acolwell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734698}

Extract part of the common utility function in Homepage related test to
HomepageTestRule.

Bug: 1036470
Change-Id: I19b6feb55deff54b94c025ab6319eeeeb7e48650
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2013740
Auto-Submit: Wenyu Fu <wenyufu@chromium.org>
Commit-Queue: Wenyu Fu <wenyufu@chromium.org>
Reviewed-by: Wei-Yin Chen (陳威尹) <wychen@chromium.org>
Reviewed-by: Theresa  <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734697}

The migration of the <certificate-manager> component itself has been
done in previous CLs. Here chrome://certificate-manager is simply
modified to display the Polymer 3 version of <certificate-manager>

Bug: 965770
Test: Navigate to chrome://certificate-manager. There should be no HTML Imports related warnings in DevTools.
Change-Id: I68f8aac10c9cf3aa94853670b0201beb87e4aebc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2013860Reviewed-by: James Cook <jamescook@chromium.org>
Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734696}

Mac trybots were switched in crrev.com/c/1918372, this completes the
migration, switching Android, Linux and Windows manual GPU trybots.

Also removes gpu-fyi-try-win-xr-builder-64, since it doesn't have a
corresponding pool, and looks like it can't be used for the intended
purpose of pinpoint jobs.

Bug: 1020753, 977735
Change-Id: I7800d10c137010c08bb4ff10cd966dc62df9a161
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015548
Commit-Queue: Yuly Novikov <ynovikov@chromium.org>
Reviewed-by: Aaron Gable <agable@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734695}

BUG=1044730

Change-Id: I9b664dfea146371672d1e6488f34fdbd0a4fcb0e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2013495
Commit-Queue: Archana Simha <archanasimha@chromium.org>
Reviewed-by: Istiaque Ahmed <lazyboy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734694}

Bug: 1045122

Change-Id: I54beac2185515cf91b6225f9ce1588f2d2ae65e4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015430
Commit-Queue: Maksim Orlovich <morlovich@chromium.org>
Reviewed-by: Eric Orth <ericorth@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734693}

Currently, if experimental fling animation feature is turned on,
FlingControllerTest fails with an exception as
ScreenWin::GetPixelsPerInch() returns zero. As there is no display
instantiated while running FlingController unittest,
GetScreenWinDisplayNearestDIPPoint returns default ScreenWin object which
has zero value for pixels per inch.

This CL fixes the issue by return default value if the value of pixels
per inch from ScreenWinDisplay is zero.

Change-Id: I9cd7aa2ccfd62fa1896981f09a2dd4a336e49469
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1974620Reviewed-by: Robert Liao <robliao@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Reviewed-by: Daniel Libby <dlibby@microsoft.com>
Reviewed-by: David Bokan <bokan@chromium.org>
Commit-Queue: Robert Liao <robliao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734692}

New methods are added to Tab:
- beginFindInPage
- activateNextFindInPageMatch
- endFindInPage

And a new FindInPageCallback interface is introduced with one method:
- onFindResult

Also add very basic FIP controls to shell to partially exercise the
new API.

Notes:
1. The embedder provides the main find in page UI (the text input).
2. The embedder is responsible for ending the find session as
   appropriate (i.e. when the main find in page UI is dismissed),
   which cleans up the in-page UI, consisting of a results sidebar and
   text highlighting. Commonly this would happen if the user cancels the
   find session or if a navigation occurs.
3. When the active tab loses focus, the find session is ended and the
   result bar is removed.
4. It is generally expected that the embedder-provided find in page UI
   will be hosted in the top view.

TODO:
1. The top controls should be forced visible when the new web contents
   overlay view holds children. That will definitely be desired for
   tab modal dialogs, and is probably desired for find in page as well
   (at least judging by what Clank does).
2. Write tests.

Bug: 1038415
Change-Id: I6183172dc3944157aae2db5ebb0aed983a34bffc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2004072Reviewed-by: Theresa  <twellington@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Evan Stade <estade@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734691}

The test conformance/textures/misc/texture-upload-size.html is flaky on
Android with the OpenGL ES backend:

https://ci.chromium.org/p/chromium/builders/try/android_angle_rel_ng/10962
https://ci.chromium.org/p/chromium/builders/try/android_angle_rel_ng/10935
https://ci.chromium.org/p/chromium/builders/try/android_angle_rel_ng/10931
https://ci.chromium.org/p/chromium/builders/try/android_angle_rel_ng/10871

This CL will suppress the test while the issue is investigated.

Bug: 1044847
Tbr: ynovikov@chromium.org
Change-Id: I068b75df073d2e1c39a0027d5642cccea8e0f1fd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2017644
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Commit-Queue: Yuly Novikov <ynovikov@chromium.org>
Reviewed-by: Yuly Novikov <ynovikov@chromium.org>
Reviewed-by: Jamie Madill <jmadill@chromium.org>
Auto-Submit: Tim Van Patten <timvp@google.com>
Cr-Commit-Position: refs/heads/master@{#734690}

https://dawn.googlesource.com/dawn.git/+log/a5a6e4f5bbda..d87e67684558

git log a5a6e4f5bbda..d87e67684558 --date=short --first-parent --format='%ad %ae %s'
2020-01-23 cwallez@chromium.org Add the webgpu.h swapchain creation path

Created with:
  gclient setdep -r src/third_party/dawn@d87e67684558

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/dawn-chromium-autoroll
Please CC cwallez@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

Cq-Include-Trybots: luci.chromium.try:dawn-linux-x64-deps-rel;luci.chromium.try:dawn-mac-x64-deps-rel;luci.chromium.try:dawn-win10-x64-deps-rel;luci.chromium.try:dawn-win10-x86-deps-rel
Bug: None
Tbr: cwallez@google.com
Change-Id: Id9ebeeab4ccc90df0fd625c21915ab9389cd814e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2017679Reviewed-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@{#734689}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/00bf4462314d..15dccfbf4081


Created with:
  gclient setdep -r src-internal@15dccfbf4081

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll
Please CC jbudorick@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome
Bug: chromium:1039877
Tbr: jbudorick@google.com
Change-Id: I0c2f0afabec7e5cb87497884c58582dc82fa706e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2017654Reviewed-by: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#734688}

Similar to other device policies around, we want to report some
information about the crash reports stored in local devices. This newly
added policy is used to turn on/off the feature. More details can be
found in the policy definition file (policy_templates.json).

Bug: 1040078
Change-Id: I477f2007d210085850a0eb964ccbabea9b47e753
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007420
Commit-Queue: Anqing Zhao <anqing@google.com>
Reviewed-by: Mattias Nissler <mnissler@chromium.org>
Reviewed-by: Sergey Poromov <poromov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734687}

Due to its history, zlib has to support building for environments
without access to basic C functions (e.g. memcpy, memset, etc) or in
environments with odd memory management patterns (e.g. MSDOS).

Therefore, it is good form to use zmemset/zmemcpy/etc for handling
memory and the same applies for initializing a memory block to zero.

Bug: 1032721
Change-Id: I8d898872ca00197cc7e961d7c49e1912073895c2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016772Reviewed-by: Chris Blume <cblume@chromium.org>
Reviewed-by: vikas soni <vikassoni@chromium.org>
Commit-Queue: Adenilson Cavalcanti <cavalcantii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734686}

https://skia.googlesource.com/skia.git/+log/87211cd0bad8..11b05bc11f27

git log 87211cd0bad8..11b05bc11f27 --date=short --first-parent --format='%ad %ae %s'
2020-01-23 reed@google.com Don't make promises about rowbytes
2020-01-23 egdaniel@google.com Treat GrTextureAdjusters mip copy like other producers, i.e. no fallback.
2020-01-23 michaelludwig@google.com Revert "Increase precision of some quad AA calculations"
2020-01-23 mtklein@google.com basic pass at gradients
2020-01-23 reed@google.com remove some memory-based methods, add rc()
2020-01-23 senorblanco@chromium.org Implement support for framebufferOnly render targets.
2020-01-23 egdaniel@google.com GrPixelConfig is DEAD!!!!!
2020-01-23 halcanary@google.com Fix build when (is_ios && !skia_enable_skottie)
2020-01-23 michaelludwig@google.com Increase precision in barycentric_coord calculations
2020-01-23 egdaniel@google.com Remove fConfig from GrSurfaceDesc.
2020-01-23 bsalomon@google.com Fix issue introduced in 33c0f260d28e28dbb5e34be71ffcbd5165a83bb3
2020-01-23 michaelludwig@google.com Increase precision of some quad AA calculations
2020-01-23 herb@google.com Reland "Specialize SkRectanzier to SkRectanizerSkyline"
2020-01-23 reed@google.com row/col methods
2020-01-23 reed@google.com remove obsolete flag SK_SUPPORT_LEGACY_CANVAS_MATRIX_VIRTUALS
2020-01-23 brianosman@google.com Disable Programs test on MacBook10.1-Metal

Created with:
  gclient setdep -r src/third_party/skia@11b05bc11f27

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/skia-autoroll
Please CC benjaminwagner@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-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
Bug: chromium:10141204,chromium:1038304,chromium:1044862
Tbr: benjaminwagner@google.com
Change-Id: I18cf92a6289d682ad997145d9d245f9009430dc2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016337Reviewed-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@{#734685}

This is a more suitable name for this class as it will be used
to track dedicated workers and shared workers in the future.

Bug: 1041093
Change-Id: I711aff37886fa63ad8b799694b9ab81f8bcf3d10
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993728
Commit-Queue: Patrick Monette <pmonette@chromium.org>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734684}

AppListItemView ctor was calling SetBackgroundBlurEnabled, which depends
on icon_, before the icon view was actually added as the item view child
(and thus before icon_ ptr was set).

BUG=1043908

Change-Id: I9e5b52c8030899a991e08a462f511bff3292e886
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2018123Reviewed-by: Alex Newcomer <newcomer@chromium.org>
Commit-Queue: Toni Baržić <tbarzic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734683}

This is a speculative fix. As per comment #5 on that bug, we are
probably obtaining a WeakPtr from an invalid raw ptr.

Bug: 1038776
Change-Id: I0c2a819d53cd83df1e2042cafb3f7fc94bd681b7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016344
Commit-Queue: Jonathan Backer <backer@chromium.org>
Reviewed-by: Peng Huang <penghuang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734682}

Adds a new option for users in non-managed accounts to clear synced
data from their local device when signing out.

Bug: 1005509
Change-Id: Iae3b599b3ca3698b2a176bd56b470c6787c74367
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007695
Commit-Queue: Nohemi Fernandez <fernandex@chromium.org>
Reviewed-by: Jérôme Lebel <jlebel@chromium.org>
Reviewed-by: Sylvain Defresne <sdefresne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734681}

This should be practically a no-op change since we specify *_ld
explicitly in both the ebuild and in Simple Chrome (for now). But
it will make `gn args --list` print more accurate info wrt these args.

Bug: 937821
Change-Id: I155fd8e2fd6a6275522c768ea96c78eb397a7a7c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2014127Reviewed-by: John Budorick <jbudorick@chromium.org>
Reviewed-by: George Burgess <gbiv@chromium.org>
Commit-Queue: Ben Pastene <bpastene@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734680}

The zero-crossing frequency estimation is very sensitive to the concealment
mechanism in WebRTC. By experimentation this seems to happen
more often in the initial transition of the stream. Skip the
first 200 ms in the verification to make the frequency estimation
more robust.

Restore frequency estimation error limit to +/- 50 Hz.

Bug: none
Change-Id: I8a7169cc20047395cb0c566d98f9d780b73f63d7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2014906
Commit-Queue: Johannes Kron <kron@chromium.org>
Auto-Submit: Johannes Kron <kron@chromium.org>
Reviewed-by: Lambros Lambrou <lambroslambrou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734679}

conformance/textures/misc/canvas-teximage-after-multiple-drawimages.html

Observed failing on Win Vulkan NVIDIA Passthrough,
but skipping on all Win Vulkan Passthrough as ANGLE doesn't actively
support Win Vulkan Passthrough at the moment.

Bug: angleproject:4334
Change-Id: If8add00e24ec6fdaeaeeb5e4626ffb7de86c483d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2017903Reviewed-by: Yuly Novikov <ynovikov@chromium.org>
Commit-Queue: Yuly Novikov <ynovikov@chromium.org>
Commit-Queue: Shahbaz Youssefi <syoussefi@chromium.org>
Auto-Submit: Shahbaz Youssefi <syoussefi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734678}

Context: Android Browser Test has no way to control the Web Contents of
Payment Handler. However, the control is needed, in order to make it
easier to cover Payment App behaviours.

Before change:
Android Browsertest could not run script in the WebContents of Payment
Handler, because the test has no access to the WebContents.

After change:
Android Browsertest could run script in the WebContents of Payment
Handler.

Change:
* Build the plumbs for Android Browser Tests to get the
WebContents from ExpandablePaymentHandler UI.
* Added a test to cover the Payment cancel flow.

Bug: 1042892

Change-Id: I3b8813eed4c3bd05658aae465b888410954c1fd1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2013810
Commit-Queue: Liquan (Max) Gu <maxlg@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734677}

This patch implements the serializer function for skottie draw ops. It
utilizes the transfer cache to avoid moving the entire skottie byte
data across IPC for every frame update.

This functionality is not included in android since android will not be
using it.

To achieve this the following modifications were also
made to the SkottieWrapper class:
  - A unique id is generated using fast hash for a given animation
    byte data.
  - Store the raw byte data in the object.
  - Modify the constructor to differentiate between serializable &
    non-serializable constructors.

Test=Added unit tests for transfer cache and paint op buffer.

Bug: 894635
Change-Id: I9fb7b5e7f761a84e6b6112d6e73e5681e9d86342
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003809
Commit-Queue: Malay Keshav <malaykeshav@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Khushal <khushalsagar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#734676}