GitLab

The Polymer 2 version is not used anymore, therefore no auto-generation
is necessary and the v3 version can be directly checked in.

Fixed: 1042545
Change-Id: I5054477c0b7427f4ec6b760e5da3eac904af2320
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003114
Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org>
Auto-Submit: Demetrios Papadopoulos <dpapad@chromium.org>
Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732590}

This CL adds more tests for Timing-Allow-Origin checks in ElementTiming
and LargestContentfulPaint with multiple redirects. Before, we had tests
for:
* Single cross-origin response with a TAO header (image-TAO.sub.html).
* Multiple redirects, with '*' TAO header (multi-redirect-image.html).

This CL renames the latter to be more descriptive and adds:
* Same-origin redirect tests (should pass without TAO headers).
* Multi-cross-origin redirect tests with various TAO header values.

Bug: 1003943
Change-Id: Id44f0f18f143c8ca4ee3ca40c2383fa2ae22590c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2001070
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Reviewed-by: Yoav Weiss <yoavweiss@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732589}

This seems to be a majority of the failures for invalid deserialization
errors with PaintOpBuffers and its unclear whether this is just fallout
from failure to deserialize an inlined SkTextBlob or a caching error.

Skip performing a crash dump for the cache error cases to make this
clearer.

R=ericrk@chromium.org

Bug: 1019634
Change-Id: Ia882b918dc0630a89c7507fb0154f6fb08ee0087
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2001584
Auto-Submit: Khushal <khushalsagar@chromium.org>
Reviewed-by: Eric Karl <ericrk@chromium.org>
Commit-Queue: Khushal <khushalsagar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732588}

There is a data race in
LayerTreeHostScrollbarsPixelTest.HugeTransformScale caused by
TestGpuServiceHolder being initialized before the command line options
for Vulkan are set in LayerTreeTest::RunTest(). The test was not running
using Vulkan, and was passing as a false positive.

Set |renderer_type_| in the constructor of LayerTreeTest and move the
command line initialization there to make sure that these options are
set before any of the test body code is run. To clean up, remove
RendererType from the LayerTreePixelTest::RunTest() variants, and
replace some direct checks to |renderer_type_|.

Bug: 1040259
Change-Id: If47923b5ba21190733d584b0a709276c46710527
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003171Reviewed-by: kylechar <kylechar@chromium.org>
Commit-Queue: Sean Gilhuly <sgilhuly@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732587}

Change-Id: Id3998f7ae6dd0de5449a184481afd392e549b889
Bug: 1042531
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003070
Commit-Queue: Cathy Li <chili@chromium.org>
Reviewed-by: Justin DeWitt <dewittj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732586}

Previously this caused SharedImageStub::
MakeContextCurrentAndCreateFactory() to get a kSuccess and use nullptr
as |context_state_|.

Bug: 1027768
Change-Id: Icc8c7c2e5efa3e8a5aa24d1c340b4f355a6a5ed5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1997638
Commit-Queue: Kramer Ge <fangzhoug@chromium.org>
Reviewed-by: Eric Karl <ericrk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732585}

When the feature is enabled shelf navigation controls (home and back
button) and overview button will be hidden from shelf (in favor of
gesture navigation). The feature is disabled by default.

BUG=1012814

Change-Id: I372a11efec9e9ed5b0e92c0a73b9b4a9c739c493
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1995776
Commit-Queue: Toni Baržić <tbarzic@chromium.org>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Reviewed-by: Manu Cornet <manucornet@chromium.org>
Reviewed-by: Xiaoqian Dai <xdai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732584}

Manual tests run:
- Tab traverse forwards
- Tab traverse backwards
- ChromeVox traverse forwards
- ChromeVox traverse backwards
- Click inside non-navigable card
- Tap inside non-navigable card
- Click inside navigable card
- Tap inside navigable card
- Tab traverse multiple cards

Bug: b:146351046
Change-Id: I72bb661765792ec0d222c39dd82df3f0795d6d81
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003219Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Commit-Queue: David Black <dmblack@google.com>
Cr-Commit-Position: refs/heads/master@{#732583}

* Adjust the width of the '+' button in new tab variation from 48dp to
56dp.
* Properly tint the '+' button for light/dark mode.

Bug: 1042606, 1042015
Change-Id: I47a29b9d29ab7a5d719ec183c4c88de240eb399e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2005549
Auto-Submit: Yue Zhang <yuezhanggg@chromium.org>
Reviewed-by: Theresa  <twellington@chromium.org>
Commit-Queue: Yue Zhang <yuezhanggg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732582}

The group name has been changed to Enabled_20191111 some time back

Change-Id: Ifb62c159f9ac02d21bece604e17ccb22e3464b91
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2002744Reviewed-by: Jesse Doherty <jwd@chromium.org>
Commit-Queue: Min Qin <qinmin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732581}

Currently, when a group is moved, there is a tab-moved event that is
fired for every single tab in the group. This leads to issues when
trying to preserve the parent-child relationship of the TabGroup
and the TabElement when certain tab-moved events have fired before
others and leads to temporary re-ordering of tabs within the group.

This CL coalesces multiple tab-moved events to a synthetic group-moved
event only after every tab-moved event is fired, so that the TabGroup
element is only moved once.

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

This includes switching into a grouped tab and tab creation.

Bug: 1040657
Change-Id: I48aa185a8be5a383bb4253061b5860d1cd73b022
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1995955Reviewed-by: Peter Boström <pbos@chromium.org>
Reviewed-by: Jesse Doherty <jwd@chromium.org>
Reviewed-by: Connie Wan <connily@chromium.org>
Commit-Queue: Charlene Yan <cyan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732579}

The identity pill has been launched and was enabled by default. It can
now be enabled permanently.

Change-Id: I01d1fe957d81c5729dc10e3f40a81864773c1240
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2000117Reviewed-by: Jan Krcal <jkrcal@chromium.org>
Reviewed-by: Jesse Doherty <jwd@chromium.org>
Auto-Submit: David Roger <droger@chromium.org>
Commit-Queue: Jesse Doherty <jwd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732578}

This is still useful, increase the milestone.

Bug: 1037425
Change-Id: I667130d5594f76fce5413b13a01a0c8087c12484
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1997553Reviewed-by: Jesse Doherty <jwd@chromium.org>
Commit-Queue: Jesse Doherty <jwd@chromium.org>
Auto-Submit: Alex Newcomer <newcomer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732577}

Removing the histogram because we have historically not looked at it
and we now have UKM which will give us more accurate data

BUG=1042133

Change-Id: Ib8d05040b017586bd7ef653d505d9d6e0a8e4dd1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2001853
Commit-Queue: Peter Kotwicz <pkotwicz@chromium.org>
Reviewed-by: Glenn Hartmann <hartmanng@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732576}

When merging 2 pending layers, merge rect_known_to_be_opaque if
possible instead of just use that of the home pending layer.

This also fixed a bug that the home layer's rect_known_to_be_opaque
should be updated when the merged state is different from its
previous state.

Thanks pdr@ for contributing the UniteRectsKnownToBeOpaque()
algorithm.

Bug: 701991, 1029620
Change-Id: Id8d5d1b35c12959069176d7de18e59c636ac122c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2001235Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732575}

TBR=fserb@chromium.org

Change-Id: I05a35c241e4f9793675c6a56e38362928ce831b2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2001292Reviewed-by: Khushal <khushalsagar@chromium.org>
Reviewed-by: Fernando Serboncini <fserb@chromium.org>
Commit-Queue: Khushal <khushalsagar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732574}

- Remove an extra heading under "Rebaselining using try jobs" >
  "Options".
- Add doc for '--patchset=n'.
- Add link to local manual rebaselining.

TBR=robertma@chromium.org

Change-Id: I54d1daf6754707009c08cbc53791a70262bca206
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2005408
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Robert Ma <robertma@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732573}

The issue happened when an SVG background image was painted with a very
small background size rounded to zero, causing infinite tile scale and
DCHECK failure in ClipRectOp.

Bug: 1039762
Change-Id: Ia94ce2fd350b28696ef8068bd0e756bfc6d87a72
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2002839
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Fredrik Söderquist <fs@opera.com>
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Reviewed-by: Kevin Marshall <kmarshall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732572}

This reverts commit 3c4c13ac.

Reason for revert: Made ChromeVoxBackgroundTest.SelectSingleBasic flaky

Original change's description:
> Move LayoutMenuList::DidUpdateActiveOption() to HTMLSelectElement
> 
> Also,
>  - Remove LayoutMenuList::DidSelectOption().
>  - Add HTMLFormControlElement::UpdateFromElement() to add
>   DidUpdateMenuListActiveOption() to each of
>   LayoutMenuList::UpdateFromElement() calls.
> 
> This CL is a preparation to build a LayoutNG counterpart of LayoutMenuList.
> This CL has no behavior changes.
> 
> Bug: 1040828
> Change-Id: If7917af101119a830e899a50711a6c1491e22eb3
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003164
> Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
> Commit-Queue: Kent Tamura <tkent@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#732313}

TBR=yosin@chromium.org,tkent@chromium.org,kojii@chromium.org

Change-Id: I4f571b72f01f0494fc855c1ceb3841e7ff02a963
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 1040828
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2006268Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732571}

Current implementation of FilterOperation::MapRectReverse() for a blur
filter actually does a forward (outset) map of the rect. This patch
fixes the erroneous behavior by supporting MapRectReverse() to map
backward for a blur filter.

Bug: 916583
Change-Id: I43bf4498b89e18ba9c2d1eb341e977944e2226c4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1986646Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Md. Hasanur Rashid <hasanur.r@samsung.com>
Cr-Commit-Position: refs/heads/master@{#732570}

This CL implements the functionality for the download shelf UX to trigger
deep scanning. No code currently generates the necessary DownloadCheckResult
to generate this UX. It also fixes a minor UX issue where the
deep_scanning_label_ was clickable, preventing the open_now_button_ from
triggering.

Bug: 1020418
Change-Id: I32d1c2144246db6286a994ecb08147d3fd511584
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994301
Commit-Queue: Daniel Rubery <drubery@chromium.org>
Reviewed-by: Mark Pearson <mpearson@chromium.org>
Reviewed-by: Xing Liu <xingliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732569}

- Use Browser in TabGridCoordinator and TabGridMediator instead
  of using TabModel.
- The usage of TabModel to restore session inside TabGridMediator haven't
  been removed, will remove it later after updating the main controller
  to use the sessionRestorationObserver to check for restoration in
  progress.
- Update the TabSwitcher protocol's setOtrModel to be setOtrBrowser.
- The TabSwitcher protocol and its users heavily depends on TabModel so
  it will be converted to use browser gradually.
- Added couple helper methods to access the browser in the mainController.
- TabGrid still uses TabModel where it calls the tabSwitcher delegate,
  this will be changed in a following CL with changing the protocol it
  self.
- Update tests who uses these classes accordingly.

Bug: 1042277, 783777
Change-Id: If02cd3128083169b0f9e0956190d8350ce1990fd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2001849
Commit-Queue: Mohammad Refaat <mrefaat@chromium.org>
Reviewed-by: Mark Cogan <marq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732568}

The BrowserWindow resize metrics have not been relevant since the
cancelation of mus+ash project. So remove these metric.

Some summary from the data collected:
. BrowserWindow.Resize.StepCount:
    - < 2 at 75%ile.
    - ~11 at 90%ile.
    - ~29 at 95%ile.
. BrowserWindow.Resize.StepInterval
    - ~15ms at 50%ile.
    - ~50ms at 90%ile.
    - ~112ms at 95%ile.
. BrowserWindow.Resize.Duration
    - ~500ms at 50%ile.
    - ~1.8s at 90%ile.
    - ~1.7s at 95%ile.

BUG=975256, 975800, 1036977

Change-Id: I41324aba843fb414ccefc20e386ddefa091532ec
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1987916
Commit-Queue: Sadrul Chowdhury <sadrul@chromium.org>
Commit-Queue: Steven Holte <holte@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Auto-Submit: Sadrul Chowdhury <sadrul@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732567}

Bug: 951969, 936273
Change-Id: I55b52e0c687533bab2e50b63423970d9f2ba8ab2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1986960
Auto-Submit: Josh Nohle <nohle@chromium.org>
Commit-Queue: Josh Nohle <nohle@chromium.org>
Reviewed-by: Mark Pearson <mpearson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732566}

Change-Id: I89e6820f1920698f7fc44b625f7f3428c27d20fc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003292
Commit-Queue: Piotr Bialecki <bialpio@chromium.org>
Reviewed-by: Klaus Weidner <klausw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732565}

This CL adds a list of Georgian characters that look like Latin
characters. A domain consisting only of these characters and not
having a .ge ccTLD or other Georgian TLDs such as .გე will be
converted to punycode, as is done for other whole-script-confusables
such as Cyrillic and Hebrew.

This CL also reorders and regroups some of the recent test cases.

No popular domain is affected by this change.

Bug: 722167
Change-Id: Ib68b3ef68ac55576141b9cb2cd6096d149456227
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1990326
Commit-Queue: Mustafa Emre Acer <meacer@chromium.org>
Commit-Queue: Joe DeBlasio <jdeblasio@chromium.org>
Reviewed-by: Joe DeBlasio <jdeblasio@chromium.org>
Reviewed-by: Mustafa Emre Acer <meacer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732564}

Updates UpdateYPositionAndOpacity::UpdateYPositionAndOpacity to reset
transforms for views whose transform might have been changed in
ContentsView::AnimateToViewState(). This will ensure that the views are
positioned appropriatelly, and prevent them from animating as app list
view drag starts.

BUG=1042740

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

Previously no setup was done for Chrome OS and the tests assumed that
RealtimeReporting is never enabled on Chrome OS.
Now it covers the same scenarios as on other platforms, but requires
some extensive setup.

In a follow-up CL I'll add Chrome OS specific tests for different
scenarios, e.g.device/user managed/non-managed and etc.

Bug: 1012048
Change-Id: I810ae8c541fa0040ff63a8d7377129246a5473c8
Tests: Unit test updated.
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2002514Reviewed-by: Daniel Rubery <drubery@chromium.org>
Commit-Queue: Sergey Poromov <poromov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732562}

Bug: 1041908
Change-Id: I15dda3f992b930bb7280a3c16639c47d2b054680
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2001285
Commit-Queue: Michael Crouse <mcrouse@chromium.org>
Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Reviewed-by: Sophie Chang <sophiechang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732561}

In the current design HeapObjectHeader sets ObjectStartBitmap in the
constructor, which mixes abstractions and violates single responsibility
principle, since ObjectStartBitmap is managed by a different entity -
NormalPage.

This patch decouples ObjectStartBitmap and HeapObjectHeader.

Bug: 1029379
Change-Id: Iceb7450be7240d9b0765887b3e06663b56da7617
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2002820
Commit-Queue: Anton Bikineev <bikineev@chromium.org>
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732560}

Maps to 'local_discovery.enabled'.

The policy enables controllable features on the local discovery UI
(chrome://devices), which shows discoverable devices near the user
as well as cloud devices registered to them. The local discovery UI
also allows users to add classic printers connected to their computers
to Google Cloud Print.

Fixed: 1011582
Change-Id: Ib905acfc92ae5f10010bca69cae3e611982eb184
Bug: 1011582
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1977193Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Commit-Queue: Daniel Hosseinian <dhoss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732559}

RenderWidgetHostViews can become "inactive", and then "active" again.
This can happen if the origin of a RWHV is still kept alive by another
active RWHV, after the RWHV becomes inactive. Then the inactive RWHV
can become active again if its WebContents navigates back to the
matching origin.

RWHVA destroys SynchronousCompositorHost when it becomes inactive in
UpdateNativeViewTree. However it does not recreate it when RWHVA is
active again later, breaking rendering in Android WebView. Fix this
and also clean up by de-duplicating code to create and destroy
SynchronousCompositorHost.

Bug: 1039586
Change-Id: I7772c9d341f44f5c822f3ac186be236e5d6abf02
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1995841
Commit-Queue: Bo <boliu@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732558}

In order to migrate java.net.URI to GURL the junit tests that rely on
java.net.URI need to be moved to a test apk that supports the native
library.

This change moves the UrlUtilitiesUnitTest unittests and the
UrlUtilitiesTest from junit and ChromePublicTestApk, respectively, to
unit_tests (Android only). These tests should be just as fast as they
were as junit tests (and much faster than chrome_test_apk unit tests).

Bug: 783819
Change-Id: Ic8d27df818563d8caa8e9e7dbac02b9e4557e811
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1998001
Commit-Queue: Michael Thiessen <mthiesse@chromium.org>
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732557}

Just call emplace(k, v), instead of emplace(std::make_pair(k, v)). Also
fix lint errors.

Change-Id: Ib9ae69f3e21604daf1bcd2297bee960833db5290
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2005088Reviewed-by: Sébastien Marchand <sebmarchand@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732556}

https://swiftshader.googlesource.com/SwiftShader.git/+log/5fc197dc7669..5c6a3c247590

git log 5fc197dc7669..5c6a3c247590 --date=short --first-parent --format='%ad %ae %s'
2020-01-16 capn@google.com Remove the GL_NV_read_depth_stencil extension

Created with:
  gclient setdep -r src/third_party/swiftshader@5c6a3c247590

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/swiftshader-chromium-autoroll
Please CC swiftshader-team+autoroll@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_chromium_msan_rel_ng;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: None
Tbr: swiftshader-team+autoroll@google.com
Change-Id: Iaced2f9f37d65f35413e60c7b7124dc2d401154f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2004893Reviewed-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@{#732555}

- No user visible change in this cl.
- Add new directory for profile card.
- Add basic classes.

Change-Id: Ic09d5f097f712a9c58c1ed666eba22fac1d9236c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1993146Reviewed-by: sebsg <sebsg@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Commit-Queue: Tina Wang <tinazwang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732554}

This is a reland of 4e23e8e8

Patchset 1 is what previously landed. This caused flakes in other
loading predictor browser tests, so I added the holdback to all
of the tests. In a follow-up, I will make sure the tests check
for preconnects on the appropriate URLs.

See https://chromium-review.googlesource.com/c/chromium/src/+/2004181
for revert rationale.

Original change's description:
> Adding a FTT config for PreconnectSameOriginDesktop
>
> This experiment is in canary/dev and should be moved to Beta.
>
> Bug: 1038774
> Change-Id: I4fc9c44e2b68aa58f9eee7210a625103f45edb01
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992684
> Commit-Queue: Ryan Sturm <ryansturm@chromium.org>
> Reviewed-by: Alex Ilin <alexilin@chromium.org>
> Reviewed-by: Ilya Sherman <isherman@chromium.org>
> Reviewed-by: Tarun Bansal <tbansal@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#732219}

Bug: 1038774
Change-Id: Id7bd4bddf5b5812d02a8953d0733f8af73007fb6

TBR=tbansal@chromium.org,alexilin@chromium.org

Change-Id: Id7bd4bddf5b5812d02a8953d0733f8af73007fb6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2004691Reviewed-by: Alex Ilin <alexilin@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Commit-Queue: Ryan Sturm <ryansturm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732553}

https://chromium.googlesource.com/angle/angle.git/+log/01c0d6bd8d7f..bdb0f8a52414

git log 01c0d6bd8d7f..bdb0f8a52414 --date=short --first-parent --format='%ad %ae %s'
2020-01-16 angle-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/vulkan-tools/src 2c436960d2c0..4792a6854238 (3 commits)
2020-01-16 sugoi@google.com Support blendable capability
2020-01-16 angle-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/vulkan-headers/src f63dd5c9d874..881bbb347a08 (1 commits)
2020-01-16 jonahr@google.com Expose GL_ANGLE_framebuffer_blit in NULL backend

Created with:
  gclient setdep -r src/third_party/angle@bdb0f8a52414

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/angle-chromium-autoroll
Please CC jonahr@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_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win-asan;luci.chromium.try:win_optional_gpu_tests_rel
Bug: chromium:1029829
Tbr: jonahr@google.com
Change-Id: I4387a446682487ca735f0423c6bee716a858c125
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2005308Reviewed-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@{#732552}

This CL adds a secondary_title field to media_router.mojom.MediaStatus,
corresponding to the media.metadata.subtitle field in Cast SDK media
status messages, which contains artist names for media.

The artist name is shown in a Cast notification item in Global Media
Controls. Other labels are also rearranged to match the mocks.

Screenshot:
https://drive.google.com/file/d/1Ecr-7WsGFE7Be3MuPvsau3SEUwKPQPJr/view?usp=sharing

Bug: 1042016
Change-Id: Iff3cc50af41ef24e6a4e8ec10090acbffe049f8f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003388
Commit-Queue: Takumi Fujimoto <takumif@chromium.org>
Reviewed-by: Tommy Steimel <steimel@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: mark a. foltz <mfoltz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732551}