GitLab

Change-Id: I6906bf97ca2ce09b09af82e965fc41f69dc36e47
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2025832
Commit-Queue: Sophie Chang <sophiechang@chromium.org>
Reviewed-by: Michael Crouse <mcrouse@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736464}

When the system firmware update includes MRC training update it can
cause the system to boot slower after the update is applied. Also the
graphics module is not available to notify the user about the MRC
training. So notify the user about slow reboot beforehand. Here are the
screenshots of the user notification with and without a slow boot user
notification.
With slow boot user notification:
https://screenshot.googleplex.com/w5GJ3VYpnbP
Without slow boot user notification:
https://screenshot.googleplex.com/pv28UdisnXS

Bug: b/129056373
Change-Id: I3c70007688ad8f4ab727721a696edfbe06535f7c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1831005
Commit-Queue: Karthikeyan Ramasubramanian <kramasub@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736463}

Ran into this while investigating android_browsertests failures on
android-pie-x86-fyi-rel. A failing test w/ a TypeParam was being
incorrectly parsed as UNKNOWN despite clearly failing. This CL fixes
that case.

Change-Id: Iad47e1620b2f0b98348097302ca39a8342e1a116
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2028252
Commit-Queue: John Budorick <jbudorick@chromium.org>
Reviewed-by: Ben Pastene <bpastene@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736462}

This change implements the IsStructure() method, which returns true
if a node's role is a subclass of the Structure abstract role.
Please see the aria spec for more details:

https://www.w3.org/TR/wai-aria-1.1/#structure

To keep the code clean and organized, this change also implements
a few helper methods for a couple other aria abstract roles, such as
Landmark and Select.

Change-Id: If8ff7d6d59f217af85c9b1bd5e853b00b4052e33
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2023194
Commit-Queue: Akihiro Ota <akihiroota@chromium.org>
Reviewed-by: Nektarios Paisios <nektar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736461}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/2ee95beaf33d..a74b12c57c26


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

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

Change-Id: Ib9672cd539310a9712a886fc45f51749021922d0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2028175
Auto-Submit: Bence Béky <bnc@chromium.org>
Reviewed-by: Zhongyi Shi <zhongyi@chromium.org>
Commit-Queue: Zhongyi Shi <zhongyi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736459}

This hardcodes the package IDs of dynamic attributes to 0x2 and throws
an error in WebLayer if the package ID does not end up being 0x2. This
should not affect WebView, since WebView does not depend on any dynamic
attributes.

The *_pb2.py files were generated from the Resources.proto and
Configuration.proto files in the Android frameworks/base repo.

Bug: 1045262
Change-Id: Ic04c150c5c8709f59f738a84068c0b738f0c4643
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2018493Reviewed-by: Richard Coles <torne@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Clark DuVall <cduvall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736458}

https://skia.googlesource.com/skia.git/+log/d960cc31b658..8354717302ce

git log d960cc31b658..8354717302ce --date=short --first-parent --format='%ad %ae %s'
2020-01-29 egdaniel@google.com Remove asTextureProxyRef from SkSpecialImage.
2020-01-29 reed@google.com extract font from run

Created with:
  gclient setdep -r src/third_party/skia@8354717302ce

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 reed@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: reed@google.com
Change-Id: I6d013d9bc257f66abe54c8ac0160d24338b07fd3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2028017Reviewed-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@{#736457}

This reverts commit f2520c7f.

Reason for revert: The failures are only on "refs/branch-heads/3945",
not on master branch. See crbug.com/1039506#c11

Original change's description:
> Disable two failing tests in NGInlineCursorTest
> 
> Failing on android-arm64-stable-tests:
> NGInlineCursorTest/NGInlineCursorTest.CulledInlineWithAtomicInline/1
> NGInlineCursorTest/NGInlineCursorTest.CulledInlineWithFloat/1
> 
> BUG=1046338
> NOTRY=true
> TBR=chouinard@chromium.org,kojii@chromium.org
> 
> Change-Id: Ic4c94abe09498302c813bb4d48a47a28cc6a3bd4
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2023494
> Commit-Queue: Tim Volodine <timvolodine@chromium.org>
> Reviewed-by: Tim Volodine <timvolodine@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#735851}

TBR=timvolodine@chromium.org,kojii@chromium.org,chouinard@chromium.org

Change-Id: Icf33bdc9750c93701206666e346110fe7ca228e7
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 1046338
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2025748Reviewed-by: Koji Ishii <kojii@chromium.org>
Reviewed-by: Tim Volodine <timvolodine@chromium.org>
Commit-Queue: Tim Volodine <timvolodine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736456}

Three changes:

1- Avoid returning a raw pointer to chrome::mojom::PrerenderCanceler
   from GetPrerenderCanceller helper functions in favor returning a
   mojo::PendingRemote<chrome::mojom::PrerenderCanceler>. This avoids
   the need to schedule a DeleteSoon (in the renderer case) to cleanup
   the memory associated with that object later.

2- By returning a mojo::PendingRemote<..> instead of a raw pointer to
   the interface, it is no longer necessary to manually PostTask before
   accessing that interface. A mojo::PendingRemote<..> can instead be
   bound to a mojo::Remote<..> that implicitly schedules function calls
   on the right thread. The PostTask is implicit.

3- Make PrerenderContents support having multiple bound cancelers. This
   makes the above possible. In the renderer, the canceler is acquired
   immediately instead of lazily, and that is extra cost (an extra IPC)
   in the case where a canceler is not needed. This only happens for a
   page being prerendered, and so that overhead should be relatively
   small and seems worth the benefit of simple code.

Change-Id: If43a1f6fa607f07eded8511639898ea99a023cd6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2023358
Commit-Queue: Darin Fisher <darin@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736455}

This reduces repetition from having to declare the CIPD package in every
module and simplifies refactoring to move builder functions to a common
location.

Change-Id: Iffae18ace2a58682d6fbe5b61ec12f7fdc0e5d86
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2025883
Commit-Queue: Garrett Beaty <gbeaty@chromium.org>
Reviewed-by: Aaron Gable <agable@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736454}

https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/717f1ef10178..82c1b418e2fb

git log 717f1ef10178..82c1b418e2fb --date=short --first-parent --format='%ad %ae %s'
2020-01-29 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update DevTools DEPS.
2020-01-29 almuthanna@chromium.org Add JSON Summary coverage report

Created with:
  gclient setdep -r src/third_party/devtools-frontend/src@82c1b418e2fb

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/devtools-frontend-chromium
Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.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: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com
Change-Id: I02effec2855d4490f29ed893870f86fdcb24c2a9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2028016Reviewed-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@{#736453}

This test may crash on Windows. See bug for details.

TBR=mmenke@chromium.org

Bug: 1035127
Change-Id: I7d476c95a6e3463b5fe9a38707263d44f7e4922c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2028049Reviewed-by: Yi Gu <yigu@chromium.org>
Commit-Queue: Yi Gu <yigu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736452}

Specifically, adding #cr_define_end comments in all files that use
cr.define() as required by the auto-generation tools.

The BUILD.gn targets that actually make use of these special comments
will be added in a follow up CL.

Eventually these special comments/metadata will be removed, when
the Polymer 3 version of Settings is actually checked-in (and no longer
auto-generated).

Bug: 1026426
Change-Id: I02ee25d71928a103d397c070854fde1a78ebd1c1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1999281Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736451}

Using wpt-import in Chromium df3250dd.

Note to sheriffs: This CL imports external tests and adds
expectations for those tests; if this CL is large and causes
a few new failures, please fix the failures by adding new
lines to TestExpectations rather than reverting. See:
https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md

NOAUTOREVERT=true
TBR=robertma

No-Export: true
Change-Id: I900a0a0c44f84de9cb312e05f0f2269e771dbe32
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2028407Reviewed-by: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#736450}

This is a reland of cb98eddd

This fixes a crash caused by a call to GetStringFUTF16() with a format string that didn’t have placeholders.

Original change's description:
> Add legacy TLS interstitial warning
>
> This adds a new interstitial page for the legacy TLS warning. It
> generally follows the SSL interstitial, but with different strings and
> a different icon (the (i) info icon).
>
> The test interstitial is available at chrome://interstitials/legacy-tls
>
> Screenshot: https://drive.google.com/file/d/1MkWCqWKtQwo7k-ybYjKotYJDjTzRwcd0/view
>
> This also refactors the legacy TLS browsertest classes slightly, basing
> them on SSLUITest rather than CertVerifierBrowserTest, brings in the
> mock cert verifier explicitly. It also adds a SetPolicy() method to
> SSLUITestBase (to complement the EnablePolicy() method, but for policies
> that take base::Value types, in this case for the SSLVersionMin policy).
> Overall, this makes for a slightly simpler class structure and lets us
> reuse all of the infrastructure setup by SSLUITest (since
> CertVerifierBrowserTest is fairly simple in comparison).
>
> The new cert error is introduced in https://crrev.com/c/1894616. Support
> for the control site list will be added in https://crrev.com/c/1906779.
>
> Bug: 896013, 1039756
> Change-Id: Ic3242178239ac8c68d02fe0a2a21a52638146580
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1940707
> Commit-Queue: Christopher Thompson <cthomp@chromium.org>
> Reviewed-by: Mustafa Emre Acer <meacer@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#736197}

Bug: 896013, 1039756, 1046696
Change-Id: I35df3efb3f5e7fcc44211a9497724cb5a68d7d91
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2027890
Commit-Queue: Mustafa Emre Acer <meacer@chromium.org>
Auto-Submit: Christopher Thompson <cthomp@chromium.org>
Reviewed-by: Mustafa Emre Acer <meacer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736449}

Also adds the sandbox_linux_unittests filter file to the bot as a
follow-up to crrev.com/c/2020615.

Bug: 1034001, 1045623
Change-Id: I13970aaca28fb4fd71868301d4a82748d6889fb0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2027896
Commit-Queue: John Budorick <jbudorick@chromium.org>
Commit-Queue: Ben Pastene <bpastene@chromium.org>
Auto-Submit: John Budorick <jbudorick@chromium.org>
Reviewed-by: Ben Pastene <bpastene@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736448}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/db1cab866afd..cd8060e73e83

git log db1cab866afd..cd8060e73e83 --date=short --first-parent --format='%ad %ae %s'
2020-01-28 linxinan@chromium.org chromite: add owners for api/gen/test_platform
2020-01-28 bpastene@chromium.org cros_chrome_sdk: Remove support for optionally enabling clang.
2020-01-28 pprabhu@chromium.org config: Set quota account for synchronous bvt suite
2020-01-28 vapier@chromium.org qemu: fix race when installing binaries
2020-01-28 cjmcdonald@chromium.org Make toolchain changes directly imply a full source build
2020-01-28 mmortensen@google.com Fix goma_artifacts output proto update for stats/counterz.
2020-01-28 lamontjones@chromium.org api: call toolchain.BundleArtifacts endpoints.
2020-01-28 lamontjones@chromium.org toolchain_util: BundleChromeClangWarningsFile.
2020-01-28 lamontjones@chromium.org chroot_lib: add chroot_path method.
2020-01-28 saklein@chromium.org workon_helper: Minor cleanup.

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

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/chromite-chromium-autoroll
Please CC chrome-os-gardeners@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:chromeos-kevin-rel
Bug: None
Tbr: chrome-os-gardeners@google.com
Change-Id: Ie2f969f8f6936e029331ff6e79e24653b95fa33b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2028007Reviewed-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@{#736447}

Bug: 951969, 936273
Change-Id: I59a980ee3f7af519b8916d0831c738c1ada84f98
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1988838
Commit-Queue: Josh Nohle <nohle@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736446}

This test started to timeout on Linux:
https://analysis.chromium.org/p/chromium/flake-portal/flakes/occurrences?key=ag9zfmZpbmRpdC1mb3ItbWVyfgsSBUZsYWtlInNjaHJvbWl1bUBibGlua193ZWJfdGVzdHNAaHR0cC90ZXN0cy9tZWRpYS9hdXRvcGxheS9kb2N1bWVudC11c2VyLWFjdGl2YXRpb24tY3Jvc3Mtb3JpZ2luLWZlYXR1cmUtcG9saWN5LWhlYWRlci5odG1sDA

TBR=beccahughes@chromium.org
NOTRY=True

Bug: 995663
Change-Id: I9a0d4bd2f63b1616b12999aaf7a500563401234f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2027901Reviewed-by: Yi Gu <yigu@chromium.org>
Commit-Queue: Yi Gu <yigu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736445}

Native Java Unittests can now simply enable/disable features for
individual tests using, for example:
@NativeJavaTestFeatures.Enabled({"Feature1", "Feature2"})
or
@NativeJavaTestFeatures.Disabled("Feature3")

This will generate a test method body that creates a ScopedFeatureList
with the specified feature overrides set.

Bug: 783819
Change-Id: I6473f6b9584e3faa1c19277a6c8eb6f4cf280677
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2015442
Commit-Queue: Michael Thiessen <mthiesse@chromium.org>
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Reviewed-by: (gone) Eric Stevenson <estevenson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736444}

Bug: 1044521
Change-Id: Ib7350579495f4774a05980c763d1fe453a4c179b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2024074Reviewed-by: Henrik Boström <hbos@chromium.org>
Commit-Queue: Steve Anton <steveanton@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736443}

This reverts commit eec2c8df.

Reason for revert: 
An exception for the zh-HK ByteOrderMarks has been added.
https://chromium-review.googlesource.com/c/chromium/src/+/2026149

Original change's description:
> Revert "[Android] don't map zh-hk to zh-tw in bundle builds."
> 
> This reverts commit 43fcd55d.
> 
> Reason for revert: 
> 
> Suspecting this change caused the compile failure at https://cr-buildbucket.appspot.com/build/8889983375245058816.
> 
> Original change's description:
> > [Android] don't map zh-hk to zh-tw in bundle builds.
> > 
> > To give Clank language parity with Android 27 new locales are being
> > added.  26 of those locales have been added in two previous CLs:
> > 
> >    - https://crrev.com/c/1941058
> >    - https://crrev.com/c/1952288
> > 
> > zh-hk was skipped because currently resources for it are mapped to
> > zh-tw.  This CL skips that mapping for bundle builds where zh-hk is
> > now included. zh-hk is still mapped to zh-tw in apk builds.
> > 
> > There is an increase in size even when language splits are used in
> > bundles.  A bug has been created to look into this:
> > - APK Bundles wastes a lot of space in resources.arsc (400kb)
> > - https://crbug.com/1031645
> > 
> > Bug: 1034774
> > Binary-Size: Size increase is unavoidable (see above).
> > Change-Id: I4edb9d5213e8dd3443522deee5395e500af34371
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1970258
> > Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
> > Reviewed-by: (gone) Eric Stevenson <estevenson@chromium.org>
> > Commit-Queue: Trevor  Perrier <perrier@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#736071}
> 
> TBR=yfriedman@chromium.org,tedchoc@chromium.org,agrieve@chromium.org,estevenson@chromium.org,perrier@chromium.org
> 
> Change-Id: I6748ad1e997bb5e2e05d6a99a52fd3e3595253fd
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Bug: 1034774
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2026151
> Reviewed-by: Chan Li <chanli@chromium.org>
> Commit-Queue: Chan Li <chanli@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#736091}

TBR=yfriedman@chromium.org,tedchoc@chromium.org,agrieve@chromium.org,chanli@chromium.org,estevenson@chromium.org,perrier@chromium.org

Change-Id: I934feb29c7f8b032236ce2e0cc4c4c8c38de5511
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 1034774
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2026427Reviewed-by: Megan Jablonski <megjablon@chromium.org>
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Commit-Queue: Trevor  Perrier <perrier@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736442}

The Advanced Protection deep scanning feature will prompt users enrolled
in the Advanced Protection program to send their files to Google for
malware scanning. While the user needs to choose which files to upload,
admins may be concerned about the potential sharing of data. So this CL
adds a policy which can be used to prevent this prompt from appearing.

Bug: 1020418
Change-Id: I1f3bf1952aa9774bd503256c943179e6fdc81cbb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2024081
Commit-Queue: Daniel Rubery <drubery@chromium.org>
Reviewed-by: Xinghui Lu <xinghuilu@chromium.org>
Reviewed-by: Pavol Marko <pmarko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736441}

Adding SigninCoordinator class for the new implementation of sign-in
UI.
Based on design: http://go/chrome-ios-signin-migration
Related to:
 + crrev.com/c/2025353
 + crrev.com/c/2027809

Bug: 971989
Change-Id: Ib9e07a05cb843a7335bb79b5cf576d7b00e91970
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2025547
Commit-Queue: Jérôme Lebel <jlebel@chromium.org>
Reviewed-by: Gauthier Ambard <gambard@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736440}

This is a two-sided patch and will break downstream clank until the following is landed:
https://chrome-internal-review.googlesource.com/c/clank/internal/apps/+/2473783

There are no changes to this reland. The fix for the original revert is
in the other patch linked above.

This is a reland of da0bf646

Original change's description:
> Rename CopylessPaste to DocumentMetadata to reuse the class for other purposes
>
> Bug: 1044244
> Change-Id: I7af8208b8c5a25f247b09cc0cbe55d44934f1d2d
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2020604
> Reviewed-by: Becca Hughes <beccahughes@chromium.org>
> Reviewed-by: Kentaro Hara <haraken@chromium.org>
> Reviewed-by: Daniel Cheng <dcheng@chromium.org>
> Commit-Queue: Sam Bowen <sgbowen@google.com>
> Cr-Commit-Position: refs/heads/master@{#735612}

TBR=dcheng@chromium.org,haraken@chromium.org

Bug: 1044244
Change-Id: I5348c86f79e39539d21956f82981a3e6d49d7009
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2026409Reviewed-by: Natalie Chouinard <chouinard@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Becca Hughes <beccahughes@chromium.org>
Commit-Queue: Sam Bowen <sgbowen@google.com>
Cr-Commit-Position: refs/heads/master@{#736439}

If the device supports atomic APIs, use drmModeAtomicCommit to modeset
and disable instead of drmModeSetCrtc.
Abstracted Modeset and Disabled code to HDPM to handle both atomic and
legacy call.
Updated tests to support Connector and CRTC props.

This is a reland of crrev.com/c/1715751

BUG=987274
TEST=HardwareDisplayControllerTest.CheckModesettingSetsProps,
HardwareDisplayPlaneManagerLegacyTest.Modeset,
HardwareDisplayPlaneManagerLegacyTest.DisableModeset,
HardwareDisplayPlaneManagerAtomicTest.DisableModeset, Tested on
Nautilus(Intel), Grunt(AMD) and Cave(Legacy).

Change-Id: I8ac3f81a0c117f3b3489cc0168e934799f387891
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2028168Reviewed-by: Daniel Nicoara <dnicoara@chromium.org>
Commit-Queue: Mark Yacoub <markyacoub@google.com>
Auto-Submit: Mark Yacoub <markyacoub@google.com>
Cr-Commit-Position: refs/heads/master@{#736438}

Scroll indicator is drawn over UiElementContainerView's empty bottom
border to work around issue of drawing over top of Assistant cards.

Visibility of the scroll indicator view is synced to vertical scroll
bar update/visibility events.

Bug: b:112669597
Change-Id: Ib8ae57428bb827913957fdd92168868c181ab4d7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2024285Reviewed-by: Robert Flack <flackr@chromium.org>
Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Commit-Queue: David Black <dmblack@google.com>
Cr-Commit-Position: refs/heads/master@{#736437}

Bug: None
Change-Id: Ia4af230ed8d5200a98eafae136eb96a0bc56fd48
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2028153
Commit-Queue: Leonard Grey <lgrey@chromium.org>
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Auto-Submit: Leonard Grey <lgrey@chromium.org>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736436}

The tests started to timeout in Jan 16. A sample flaky report:
https://analysis.chromium.org/p/chromium/flake-portal/flakes/occurrences?key=ag9zfmZpbmRpdC1mb3ItbWVyUgsSBUZsYWtlIkdjaHJvbWl1bUBibGlua193ZWJfdGVzdHNAaHR0cC90ZXN0cy9kZXZ0b29scy9zZWFyY2gvc2VhcmNoLWluLXNjcmlwdC5qcww

TBR=yangguo@chromium.org

Bug: 1046784
Change-Id: I7ee87bfc88cc22d2e9afaa4d6383cd95eaf2d7f5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2027895Reviewed-by: Yi Gu <yigu@chromium.org>
Commit-Queue: Yi Gu <yigu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736435}

Remove call to DumpWithoutCrashing() and replace with a histogram that
counts instances of unknown PPD color models.

Bug: 1035010
Change-Id: I1bbf1ec423db08f06e66de38fd27b727849b61ba
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2026313
Commit-Queue: Daniel Hosseinian <dhoss@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Reviewed-by: Brian White <bcwhite@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736434}

Bug: None
Change-Id: Ie5214c159e1c14c59dcbd4d4660f33bd44d4a77e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2021287
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: Istiaque Ahmed <lazyboy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736433}

TBR=bling-p10-rolls@google.com

Change-Id: I73b9a09913c156a2a38a573139aed7c69bcc16f2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2028169Reviewed-by: Internal Frameworks Autoroller <bling-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Internal Frameworks Autoroller <bling-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#736432}

And resolve a couple of TODOs.

Bug: 1013389
Change-Id: Iae6b9625dce5ec2319cb2b099678cba11f594e6f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2028251
Commit-Queue: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: Lucas Gadani <lfg@chromium.org>
Auto-Submit: Jeremy Roman <jbroman@chromium.org>
Reviewed-by: Lucas Gadani <lfg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736431}

Bug: 1046060
Change-Id: I7748fc85861f88ddc7496975d4a822eac9675f4f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2023234Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Commit-Queue: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736430}

Implements a shim over native GURL, exposing it to Java. Attempting to
use GURL will block on the native library initializing and registering
MainDex (though this is unlikely in practice unless you're manipulating
URLs really early in startup).

The Java object holds onto all necessary objects to reconstruct the
native GURL without re-parsing. This is both to make the Java
implementation fast for the common case, and to avoid a clunky API
requiring destroy() - the native GURL is recreated on-demand.

Relative performance of parse() followed by getHost() on a search
result page URL:
android.net.Uri: ~10.5μs
java.net.URI: ~14.5μs
GURLJava: ~16μs

Repeated getHost() calls:
android.net.Uri: ~90ns
java.net.URI: ~10ns
GURLJava: ~350ns

Why?
Android Uri only parses what you ask for, then caches that as
volatile(?!), so each new thing you ask for causes it to do parsing
work and increase memory usage (and lookups are weirdly slow for a
cached value).
Java URI parses upon creation and caches almost everything that can be
asked for as a separate String (>2x memory usage of GURL).
GURL only stores the uri String (spec) and indices into it, so a new
String is created each time. This could be cached so that memory can be
shared if many callers ask for the same GURL component.


Doc: https://docs.google.com/document/d/1kDKqBaq-b6EbUm0F4ea7ARoksUcj1KUx3qxFuSXEwM4/edit

Bug: 783819
Change-Id: I3e0fbf3505ef6294b6915b44a6fdbd6ca3f5494c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1856622
Commit-Queue: Michael Thiessen <mthiesse@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Reviewed-by: Chris Palmer <palmer@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736429}

This reverts commit 5bd704b2.

Reason for revert: The fix is applied in crrev.com/c/2024497

Original change's description:
> Revert "Update Deep Scanning upload UI text"
> 
> This reverts commit 75458c57.
> 
> Reason for revert: to unblock reverting https://chromium-review.googlesource.com/c/chromium/src/+/2020891 (crbug.com/1046693)
> 
> Original change's description:
> > Update Deep Scanning upload UI text
> > 
> > Add code to use the appropriate drag-data, drag-file and paste strings
> > instead of just defaulting to the upload strings. Removes the optional
> > part of the access point since it's used to determine the appropriate
> > string now.
> > 
> > Bug: 999145
> > Change-Id: I115cd567f94d9c4ca7a4befdff386ba76163ae20
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2016965
> > Commit-Queue: Dominique Fauteux-Chapleau <domfc@chromium.org>
> > Reviewed-by: Daniel Rubery <drubery@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#735943}
> 
> TBR=drubery@chromium.org,domfc@chromium.org
> 
> Change-Id: I78b6b5c3c3fe10cdd731d84233d20c31cb1a9e00
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Bug: 999145,1046693
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2027547
> Reviewed-by: vitaliii <vitaliii@chromium.org>
> Commit-Queue: vitaliii <vitaliii@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#736301}

TBR=vitaliii@chromium.org,drubery@chromium.org,domfc@chromium.org

Change-Id: I717f12ae775142aa6337d7aefc70c426b19d22f3
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 999145, 1046693
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2026652Reviewed-by: Daniel Rubery <drubery@chromium.org>
Commit-Queue: Dominique Fauteux-Chapleau <domfc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736428}

This reverts commit 86c4251e.

Reason for revert: The fix is applied in crrev.com/c/2024497

Original change's description:
> Revert "Cleanup base::Optional use in Deep Scanning dialog code"
> 
> This reverts commit 0f668c37.
> 
> Reason for revert: Fails Linux MSan Tests crbug.com/1046693.
> 
> Original change's description:
> > Cleanup base::Optional use in Deep Scanning dialog code
> > 
> > 2 instances of optional can be removed from DeepScanningDialog* code to
> > make it more readable:
> > - The access point no longer needs to be optional since all the access
> >   points have been added to Chrome. A default value is still included
> >   in order to simplify tests calling ShowForWebContents.
> > 
> > - The state variable in DeepScanningDialogViews is better as an enum
> >   than an optional bool indicanting pending/success/failure, especially
> >   since a timeout state is very likely in the future.
> > 
> > Change-Id: I767db78e428a607a7cc2dfe39d1d63c0f85c30d7
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2020891
> > Reviewed-by: Daniel Rubery <drubery@chromium.org>
> > Commit-Queue: Dominique Fauteux-Chapleau <domfc@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#735857}
> 
> TBR=drubery@chromium.org,domfc@chromium.org
> 
> Change-Id: Id4814d523935f867ab8fb69942281a6fc8fcf3b0
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Bug: 1046693
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2026970
> Reviewed-by: vitaliii <vitaliii@chromium.org>
> Commit-Queue: vitaliii <vitaliii@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#736302}

TBR=vitaliii@chromium.org,drubery@chromium.org,domfc@chromium.org

Change-Id: I9a094d5d1d3105dd5b5712b0c77e9b0d58788420
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 1046693
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2026355Reviewed-by: Daniel Rubery <drubery@chromium.org>
Commit-Queue: Dominique Fauteux-Chapleau <domfc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736427}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/bf682ef3..4bf20c76

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

https://webrtc.googlesource.com/src.git/+log/26b4cb3fc56c..99d6d8115b37

git log 26b4cb3fc56c..99d6d8115b37 --date=short --first-parent --format='%ad %ae %s'
2020-01-29 minyue@webrtc.org Adding absolute capture timestamp to AudioTrackSinkInterface.

Created with:
  gclient setdep -r src/third_party/webrtc@99d6d8115b37

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/webrtc-chromium-autoroll
Please CC webrtc-chromium-sheriffs-robots@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: webrtc-chromium-sheriffs-robots@google.com
Change-Id: I26bf20559350b612e50f5eeb3f6bcacec542dea5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2028014Reviewed-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@{#736425}