GitLab

The re-layout signals trickle down when things change in the shelf
config, there is no need for components to take care of observing those
changes themselves (and it triggers gratuitous layout calls).

Bug: 1042918, 1049355, 1044306
Change-Id: I9a5cff364723aae1887bb3b8fc52714e95ebd946
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2067814Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Manu Cornet <manucornet@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743711}

Removes SharedWorker exposure of MediaSource API from the
MediaSourceInWorkers blink runtime feature. Later work, following
enabling of MSE-on-DedicatedWorker in upcoming CLs, might still happen
to let MSE be usable in SharedWorker contexts.

BUG=878133,1054566

Change-Id: I902ffed4a80337843f3d4bb7ded64a8b2a173ec1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2068922Reviewed-by: Dan Sanders <sandersd@chromium.org>
Commit-Queue: Matthew Wolenetz <wolenetz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743710}

Changes the telemetry_chrome_test_without_chrome target to always
include minidump-related data dependencies instead of only on ChromeOS
and Android. This ensures that any tests run using the target will
have up-to-date tools.

Two dependencies are still excluded on Windows because they are
explicitly not defined for Windows builds in Breakpad.

Bug: 1040502
Change-Id: If7454cd706ac0b43c62b67ab0bd216ea725e37e5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2068742Reviewed-by: Caleb Rouleau <crouleau@chromium.org>
Commit-Queue: Brian Sheedy <bsheedy@chromium.org>
Auto-Submit: Brian Sheedy <bsheedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743709}

This CL moves chromeOS strings for internet pages from
settings_strings.grdp to os_settings_strings.grdp. It continues
the process of moving all chromeOS specific strings.

Bug: 967883
Change-Id: Ifadbe4ec79e2158d7730456653f1e226bb0a991f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2067540
Commit-Queue: Nnamdi Theodore Johnson-kanu <tjohnsonkanu@google.com>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743708}

https://swiftshader.googlesource.com/SwiftShader.git/+log/48d08d644c30..847856089dc3

git log 48d08d644c30..847856089dc3 --date=short --first-parent --format='%ad %ae %s'
2020-02-21 amaiorano@google.com Replace target_cpu with current_cpu in Build.gn files

Created with:
  gclient setdep -r src/third_party/swiftshader@847856089dc3

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: I0832611bbd33fd49f4218b8a898b9982fc16184c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2068674Reviewed-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@{#743707}

While build for android on arm and arm64, ChromeDriver can be built
using host toolchain.

Bug: 1050709
Change-Id: I085cc3d34c836bb89699f5e717d686435a7d4dbf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2068637Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: John Chen <johnchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743706}

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

https://chromium.googlesource.com/external/github.com/videolan/dav1d.git/+log/19ce77e0b9ec..296d1dc00641

$ git log 19ce77e0b..296d1dc00 --date=short --no-merges --format='%ad %ae %s'
2020-02-21 ltrudeau cli: Replace malloc + memset(0) with calloc in input.c
2020-02-21 ltrudeau cli: remove init_[de]muxers() functions
2020-02-20 ltrudeau Replace malloc+memset(0) with calloc
2020-02-18 janne-vlc CI: update aarch64 docker image to buster with meson 0.49
2020-02-13 martin arm: cdef: Do an 8 bit implementation for cases with all edges present
2020-02-14 martin arm32: cdef: Fix a typo for consistency
2020-02-15 gramner cli: Implement line buffering in print_stats()
2020-02-12 martin arm: cdef: Remove leftover unused labels and macro parameters
2020-02-10 martin arm64: looprestoration: NEON implementation of SGR for 10 bpc
2020-02-09 martin arm64: looprestoration: Prepare for 16 bpc by splitting code to separate files
2020-02-10 martin arm: looprestoration: Add 8bpc to existing function names, add HIGHBD_*_SUFFIX
2020-02-04 martin looprestoration: Add a bpc parameter to the init func
2020-02-09 martin arm: looprestoration: Improve scheduling in box3/5_h slightly
2020-02-05 martin arm: Use int16_t for the tmp intermediate buffer
2020-02-06 martin arm: looprestoration: Fix a comment
2020-02-10 jb NEWS: Official naming is AVX2, not AVX-2
2020-02-01 martin arm64: mc: Reduce the width of a register copy
2020-02-01 martin arm64: mc: Use two regs for alternating output rows for w4/8 in avg/w_avg/mask
2020-02-01 martin arm64: mc: Simplify avg/w_avg/mask by always using the w16 macro
2020-02-09 jb Update NEWS for 0.6.0
2020-02-06 martin arm64: mc: NEON implementation of warp for 16 bpc
2020-02-06 martin arm64: cdef: Add NEON implementations of CDEF for 16 bpc
2020-02-06 martin arm: cdef: Prepare for 16bpc

Created with:
  roll-dep src/third_party/dav1d/libdav1d

TBR=wolenetz

Change-Id: I1196c42c5c40d7006cd8a6e299467785ba90284e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2068756Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Reviewed-by: Matthew Wolenetz <wolenetz@chromium.org>
Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743704}

This reverts commit 0b623dbf.

Reason for revert: Still can't reproduce out of the bot.
Disabling the test with the proper feature flag so the flag can be
enabled on ToT since this has already launched (and the problem seems
test specific). Will work on fix for the test in a separate CL.
TBR-ing, since this is identical to the last reland, except using the
correct flag to disable test.

Original change's description:
> Revert "Reland "Enable passive mixed content warning by default""
>
> This reverts commit a4abe593.
>
> Reason for revert: [sheriff]:
> Consistent failures on linux-chromeos-chrome:
> https://ci.chromium.org/p/chrome/builders/ci/linux-chromeos-chrome
> First failed run:
> https://ci.chromium.org/p/chrome/builders/ci/linux-chromeos-chrome/3306
>
> Original change's description:
> > Reland "Enable passive mixed content warning by default"
> >
> > This reverts commit 562af1be.
> >
> > Reason for revert: Failing test was disabled since it should run with autoupgrades disabled, will investigate and fix why InitAndDisableFeatures is not doing that separately
> >
> > Original change's description:
> > > Revert "Enable passive mixed content warning by default"
> > >
> > > This reverts commit 0a37869a.
> > >
> > > Reason for revert: Causing failure of DidChangeVisibleSecurityStateTestWithAutoupgradesDisabled.DidChangeVisibleSecurityStateObserver in browser_tests on linux-chromeos-chrome
> > > Example failure: https://ci.chromium.org/p/chrome/builders/ci/linux-chromeos-chrome/3194
> > >
> > > Original change's description:
> > > > Enable passive mixed content warning by default
> > > >
> > > > Sets the feature to enabled by default and removes the config from
> > > > fieldtrial_testing_config.json in preparation for launch.
> > > >
> > > > Bug: 1025276
> > > > Change-Id: Iffcdd2153491de25b7038a609776255bbdacf2ac
> > > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2053024
> > > > Commit-Queue: Carlos IL <carlosil@chromium.org>
> > > > Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
> > > > Reviewed-by: Emily Stark <estark@chromium.org>
> > > > Auto-Submit: Carlos IL <carlosil@chromium.org>
> > > > Cr-Commit-Position: refs/heads/master@{#741506}
> > >
> > > TBR=rkaplow@chromium.org,estark@chromium.org,carlosil@chromium.org
> > >
> > > # Not skipping CQ checks because original CL landed > 1 day ago.
> > >
> > > Bug: 1025276
> > > Change-Id: I20e9dc38d83036c7b17d91de24c23ebae3049de9
> > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2058970
> > > Reviewed-by: Bret Sepulveda <bsep@chromium.org>
> > > Commit-Queue: Bret Sepulveda <bsep@chromium.org>
> > > Cr-Commit-Position: refs/heads/master@{#741860}
> >
> > TBR=rkaplow@chromium.org,estark@chromium.org,bsep@chromium.org,carlosil@chromium.org
> >
> > # Not skipping CQ checks because original CL landed > 1 day ago.
> >
> > Bug: 1025276
> > Change-Id: I9e2043fc150b9225bc32537b0cee669f1836802a
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2062671
> > Commit-Queue: Carlos IL <carlosil@chromium.org>
> > Reviewed-by: Emily Stark <estark@chromium.org>
> > Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#742366}
>
> TBR=rkaplow@chromium.org,estark@chromium.org,bsep@chromium.org,carlosil@chromium.org
>
> Change-Id: I554708d53c87488e8f199c52b32dd2d62471bb1d
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Bug: 1025276
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2062416
> Reviewed-by: Sergey Poromov <poromov@chromium.org>
> Commit-Queue: Sergey Poromov <poromov@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#742551}

TBR=rkaplow@chromium.org,estark@chromium.org,bsep@chromium.org,poromov@chromium.org,carlosil@chromium.org

Change-Id: Ica754c5662e6165dfdd535acbf0833d8b6467082

Bug: 1025276
Change-Id: Ica754c5662e6165dfdd535acbf0833d8b6467082
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2065336Reviewed-by: Carlos IL <carlosil@chromium.org>
Commit-Queue: Carlos IL <carlosil@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743703}

Aggregate PageLoad:PaintTiming.NavigationToFirstContentfulPaint by gender and generation, independently.

The previous config only aggregated by gender+generation (together) but not by either on its own.

Bug: 1006806
Change-Id: I973272d058298ff1b272cf97e4755c0d383ebab6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2067811Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Commit-Queue: Alexei Svitkine <asvitkine@chromium.org>
Auto-Submit: Roger McFarlane <rogerm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743702}

This is a preparation for fixing hit test of black backgrounds in
CompositeAfterPaint (crbug.com/937573). The new method finds the
background color from the first drawable display item in a layer after
we paint the layer.

In case that the first paint chunk is just for a blank background of
an ancestor like:
  <div id="parent" style="will-change: transform">
    <div id="child" style="position: relative;
         height: 100px; background: blue"></div>
  </div>
we'll use the child's background color as the
safe_opaque_background_color of the layer created for parent.

This also avoids unnecessary safe_opaque_background_color in
PaintChunks that are not used to set that of the layer.

Bug: 937573
Change-Id: Idf8e1c8fd9bb49cfd83fec41964589c28d9b4eba
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2068640Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743701}

We changed the highlight path generator / ink drop api a bit and this
got regressed. The ink drop was changed to use clipping based on the
the highlight path generator which also creates the path for the focus
ring by default. Since this component wants different paths for focus
rings and ink drops, separate the two.

Test: manual
Bug: none
Change-Id: I7bd9b654c9d40d066e20288fb0e6f79dda62f385
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2068753Reviewed-by: Tim Song <tengs@chromium.org>
Reviewed-by: Ahmed Mehfooz <amehfooz@chromium.org>
Commit-Queue: Sammie Quon <sammiequon@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743700}

This test was flaky most likely because it was previously a
SettingsPageBrowserTest which is known to be flaky. Converted to a
more targeted CrSettingsBrowserTest instead.

Also stop referring to the private |defaultSettingLabel_()| method
from tests. Instead properly export it with cr.define().

This is in preparation of upcoming changes in
settings-site-settings-page.

Bug: 709442,1032584
Change-Id: I4435e4e03a3c7e0f303bd70f39f2fd8cb99199bd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2067547
Auto-Submit: Demetrios Papadopoulos <dpapad@chromium.org>
Commit-Queue: John Lee <johntlee@chromium.org>
Reviewed-by: John Lee <johntlee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743699}

https://chromium.googlesource.com/chromium/src/third_party/freetype2.git/+log/49f3394d7a53..6e49dff0052a

git log 49f3394d7a53..6e49dff0052a --date=short --first-parent --format='%ad %ae %s'
2020-02-21 wl@gnu.org [psaux] Make `t1_decoder_parse_metrics' handle `op_div' (#57519).

Created with:
  gclient setdep -r src/third_party/freetype/src@6e49dff0052a

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/freetype-chromium
Please CC bungeman@google.com,drott@google.com,thestig@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:linux_chromium_msan_rel_ng;luci.chromium.try:linux-blink-rel;luci.chromium.try:mac10.12-blink-rel;luci.chromium.try:mac10.13_retina-blink-rel;luci.chromium.try:win10-blink-rel;luci.chromium.try:win7-blink-rel
Bug: None
Tbr: bungeman@google.com,drott@google.com,thestig@google.com
Change-Id: I3756ba4bb86fc1939c703cb799c23614256c6ac2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2068669Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Reviewed-by: Ben Wagner <bungeman@chromium.org>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Ben Wagner <bungeman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743698}

Enable requestStorageAccess.sub.window.html test on Mac because two
tests virtual/storage-access-api/external/wpt/storage-access-api/requestStorageAccess.sub.window.html
external/wpt/storage-access-api/requestStorageAccess.sub.window.html
failed on
https://ci.chromium.org/p/chromium/builders/ci/Mac10.11%20Tests, but I
reverted the expectation file change.

TBR=brandm@microsoft.com

Bug: 1053903
Change-Id: I348c8a387346ee2a4e8980a2fe6d84e4e5272232
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2068253
Commit-Queue: Lan Wei <lanwei@chromium.org>
Reviewed-by: Lan Wei <lanwei@chromium.org>
Auto-Submit: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743697}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/1eb16f67982b..4dc5b7792fe1

git log 1eb16f67982b..4dc5b7792fe1 --date=short --first-parent --format='%ad %ae %s'
2020-02-21 ehmaldonado@chromium.org git-cl: Fix split branch name

Created with:
  gclient setdep -r src/third_party/depot_tools@4dc5b7792fe1

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/depot-tools-chromium-autoroll
Please CC agable@chromium.org 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

Bug: chromium:1054888,chromium:998922
Tbr: agable@chromium.org
Change-Id: Ib3b93f8b637682b6a678f6a15de2a96d5afc2766
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2068757Reviewed-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@{#743696}

This reverts commit 9e4bb6d6.

Reason for revert: maybe still flaky and requires the blink changes (crbug/1054968)

Original change's description:
> Fix nav predictor url indeterminism by inserting based on creation time
> 
> (and also strip out fragment when merging nav predictor URLs)
> 
> Bug: 1051365
> Change-Id: Ie19fb6756b71dae3ef36522871c08518a506761b
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2062925
> Commit-Queue: Sophie Chang <sophiechang@chromium.org>
> Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#743638}

TBR=sophiechang@chromium.org,ryansturm@chromium.org

Change-Id: Ia767fae8e83bd1d69c4b5412715b241e5f98025e
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 1051365
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2068861Reviewed-by: Sophie Chang <sophiechang@chromium.org>
Commit-Queue: Sophie Chang <sophiechang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743695}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/a807309f3547..c7cc1e35fd4b


Created with:
  gclient setdep -r src-internal@c7cc1e35fd4b

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: None
Tbr: jbudorick@google.com
Change-Id: Ia66c38c81a6098cc061f20ab72c325eb88ea5420
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2068661Reviewed-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@{#743694}

Four MIME types with the prefix "text/x-ms-" should be treated as file
downloads rather than being rendered as inline content.

Bug: 1054863
Change-Id: I1bf261cc0ee2fdc36290bcc5c04ae3db2531f82c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2068055Reviewed-by: Eric Roman <eroman@chromium.org>
Commit-Queue: Eric Lawrence [MSFT] <ericlaw@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#743693}

https://chromium.googlesource.com/angle/angle.git/+log/a18f414547c9..8df468102d9e

git log a18f414547c9..8df468102d9e --date=short --first-parent --format='%ad %ae %s'
2020-02-21 ynovikov@chromium.org Suppress SwANGLE dEQP failures
2020-02-21 jmadill@chromium.org Refactor DrawCallPerf test parameters.
2020-02-21 spang@chromium.org Implement glImportMemoryZirconHandle & glImportSemaphoreZirconHandle
2020-02-21 geofflang@chromium.org Add geofflang@google.com to OWNERS.

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

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 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: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: None
Tbr: cwallez@google.com
Change-Id: I2adc6495626d016c020963ed1fc106e15d41bccf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2068489Reviewed-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@{#743692}

For whatever reason the autoroller created a new expectation file
instead of just updating the existing root file. Given the unexpected
nature of the fallback path where platform/win ends up pre-empting the
root on all cases, moves the platform/win file to be the root file, so
that it is more explicit.

Fixed: 1054657
Change-Id: I44c8c319edddc7c12e2ba809edff09c78d3a183d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2068651
Commit-Queue: Alexander Cooper <alcooper@chromium.org>
Commit-Queue: Klaus Weidner <klausw@chromium.org>
Auto-Submit: Alexander Cooper <alcooper@chromium.org>
Reviewed-by: Klaus Weidner <klausw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743691}

Change-Id: I602cd2b07029fc7319a916ed95f5bb5f0b6ec440
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2068656Reviewed-by: Owen Min <zmin@chromium.org>
Commit-Queue: Xiang Ji <jxiang@google.com>
Cr-Commit-Position: refs/heads/master@{#743690}

The target views_examples_with_content_exe fails to build due
compile errors related to x11. It turns out that the problem is
the lack of missing build config in ui/views_content_client.

I believe the same error has been happening in Linux X11 builds
too.

Bug: none
Test: autoninja views_examples_with_content_exe
Change-Id: I117fdeb1a1244edade2e78cf66665588ec8ea9a8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2067611Reviewed-by: Allen Bauer <kylixrd@chromium.org>
Commit-Queue: Jun Mukai <mukai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743689}

Bug: 1042224
Change-Id: I6ba8900e18da728e514c6f55d78becbd4f0deed5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2055973Reviewed-by: Joshua Pawlicki <waffles@chromium.org>
Reviewed-by: Sorin Jianu <sorin@chromium.org>
Commit-Queue: Michael Chang <donchan@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#743688}

https://skia.googlesource.com/skia.git/+log/a9733655120b..6fa47769cb65

git log a9733655120b..6fa47769cb65 --date=short --first-parent --format='%ad %ae %s'
2020-02-21 brianosman@google.com In SkRuntimeEffect, use a single shared Compiler instance
2020-02-21 sgilhuly@chromium.org SkiaDawn: Add onBindPipeline()
2020-02-21 jvanverth@google.com Create D3D device and queue
2020-02-21 brianosman@google.com Fail gracefully when encountering 'in fragmentProcessor' in raster backend
2020-02-21 reed@google.com share code around animating the rotating cube
2020-02-21 jlavrova@google.com Bugs
2020-02-21 robertphillips@google.com Revert "Move SkDeferredDisplayList.h into include\core"
2020-02-21 robertphillips@google.com Move SkDeferredDisplayList.h into include\core

Created with:
  gclient setdep -r src/third_party/skia@6fa47769cb65

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 lovisolo@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: None
Tbr: lovisolo@google.com
Change-Id: Idb3668b55c04a1f2bea3ff68217fbabaa73351b0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2068671Reviewed-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@{#743687}

(Relanding with new tests skipped on Mac NVIDIA Retina, which forces
the integrated GPU due to graphics driver bugs.)

Instead of only checking whether the containing frame is same-origin
with respect to the top-level document during
transferControlToOffscreen, check in the OffscreenCanvas constructor,
both for the main thread as well as dedicated workers. Dedicated workers
are same-origin per specification, so always grant access to the
discrete GPU in this scenario.

Add new pixel tests that verify WebGL-rendered OffscreenCanvas into an
ImageBitmapRenderingContext (i.e., where the OffscreenCanvas was not
originally tied to a canvas element). On dual-GPU macOS devices, also
verify the active state of the low-power and high-performance GPUs.

Simplify some of the tests most recently written for low/high-power GPU
switching.

Bug: 1048892
Change-Id: I20b7150029fa83d7fe066b8347bf150a0ed45d21
Tbr: kainino@chromium.org
Tbr: fserb@chromium.org
Tbr: jdarpinian@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2068645Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: James Darpinian <jdarpinian@chromium.org>
Commit-Queue: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743686}

https://android.googlesource.com/platform/external/perfetto.git/+log/8963b1a9e315..c588f36ff15c

git log 8963b1a9e315..c588f36ff15c --date=short --first-parent --format='%ad %ae %s'
2020-02-21 skyostil@google.com Merge "TrackEvent: GCC compatibility fix for using track events in templates"

Created with:
  gclient setdep -r src/third_party/perfetto@c588f36ff15c

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/perfetto-chromium-autoroll
Please CC perfetto-bugs@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

Bug: None
Tbr: perfetto-bugs@google.com
Change-Id: If64f7da5b7cf9e10dddcedc9072772fff1a2cd2f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2068659Reviewed-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@{#743685}

Forgot to set this in the original CL.

Bug: 1040728
Change-Id: I2dad8d6122de28f87a8556642be9992bab99f560
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2068857
Auto-Submit: Sajjad Mirza <sajjadm@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743684}

Bug: 1013584
Change-Id: I7f32e9d5a1e0584e509e5bd08e3346e370bbfcbc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2067318
Commit-Queue: Dominique Fauteux-Chapleau <domfc@chromium.org>
Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Reviewed-by: Daniel Rubery <drubery@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743683}

This CL adds support for passing extras from the native task. The extras
will be sent as a string. It is the responsibility of the caller to
handle the conversion between their params and the string.

Bug: 1052639
Change-Id: Ibd20d69a76694350b40d9cbdd9b7dc61abe61d06
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2058771
Commit-Queue: Shakti Sahu <shaktisahu@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743682}

This CL does some refactoring around DomainReliabilityConfig and
DomainReliabilityContext. The main change is to construct the
Google configs lazily to avoid needlessly consuming memory (with
configs that are largely the same) for domains that may never
be visited.

We also now require collector URLs to be https. This was already
the case except in tests.

Bug: 1047437
Change-Id: I6abc43e8123ae98daac417cbd3d9955acb41132f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2055548
Commit-Queue: Lily Chen <chlily@chromium.org>
Reviewed-by: Eric Roman <eroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743681}

This CL adds the implementation for the native scheduler and the native task.
1 - Added bridge classes NativeTaskScheduler, TaskInfoBridge for scheduling.
2 - Added ProxyNativeTask and its JNI counterparts for handling the callback.
3 - Added factory classes for creating the scheduler.
4 - Extras will be added in a later CL

Bug: 1045765
Change-Id: I05851dc330625c8d8133439123e489cd9a7c3ee0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2035051
Commit-Queue: Shakti Sahu <shaktisahu@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743680}

Change-Id: I7e2465a79edcd492de8734cf67c0102197f490d5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2065733
Commit-Queue: Brian Manthos <brianman@microsoft.com>
Commit-Queue: Joshua Pawlicki <waffles@chromium.org>
Reviewed-by: Joshua Pawlicki <waffles@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743679}

1) Fix IsInLastAllocatedRegion() semi-interval check;
2) Simplify GenerationalBarrier() a bit.

Bug: 1029379
Change-Id: If2c23ffc2c9addb7a996b6094e8666b226173466
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2066729
Commit-Queue: Anton Bikineev <bikineev@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743678}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/ddedaa32..e6e23409

Please follow these instructions for assigning/CC'ing issues:
https://v8.dev/docs/triage-issues

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com

Change-Id: Idcbf3d38482c77134715d99c11106ca9f2e505bd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2068561Reviewed-by: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#743677}

As part of this migration, it was realized that
blink::PluginAction::enable was not used, leaving only
blink::PluginAction::type (blink::PluginActionType) left.

Hence, blink::PluginActionType was replaced by
blink::mojom::PluginActionType enum and call sites adapted.

BUG=1051162, 919392

R=dtapuska@chromium.org
TBR=wjmaclean@chromium.org

Change-Id: I176a2f45b5865755f7b4cf08d5740581eba56793
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2066877Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Auto-Submit: Antonio Gomes <tonikitoo@igalia.com>
Cr-Commit-Position: refs/heads/master@{#743676}

This CL adds a temporary workaround to avoid the crash in
content::RenderFrameImpl::UpdateSubresourceLoaderFactories.
This is not a real fix, but only an attempt to suppress
the recent crash spike.

This CL should not be needed once:
1) A real fix is found for https://crbug.com/1013254.
or
2) CorbAllowlistAlsoAppliesToOorCors ships
   (~M83; see https://crbug.com/1013254#c19)

Bug: 1013254
Change-Id: I3e918bd2cdf569e65431c8b62e618fd540394afd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2068638
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Auto-Submit: Łukasz Anforowicz <lukasza@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743675}

The new example test is disabled until the additional layout animation
observer API lands.

Bug: 1044306
Change-Id: I14a259be5bcc5d9710b96a7913a31cd5523e2187
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2051150
Commit-Queue: Manu Cornet <manucornet@chromium.org>
Reviewed-by: Alex Newcomer <newcomer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743674}

This CL moves chromeOS strings for settings printing page from
settings_strings.grdp to os_settings_strings.grdp. It continues
the process of moving all chromeOS specific strings.

Bug: 967883
Change-Id: I72bd1b0b51d197c1b6c4ab2300f943eedbbec0b3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2067667Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Commit-Queue: Nnamdi Theodore Johnson-kanu <tjohnsonkanu@google.com>
Cr-Commit-Position: refs/heads/master@{#743673}

Bug: 1054938
Change-Id: Ia819231bfa212a0eec30b22c84761f47fee1dbea
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2068744Reviewed-by: Joshua Pawlicki <waffles@chromium.org>
Commit-Queue: Mila Green <milagreen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743672}