GitLab

When posting tasks with base::PostDelayedTask(), explicitly specify whether the
tasks should run on the thread pool on a specific named thread. This is in
preparation for making it always mandatory to specify the destination for posted
tasks.

This patch has no functional changes.

This CL was uploaded by git cl split.

Bug: 968047
Change-Id: I9595134c52d067fc61f8d3c705fa7f21db18b10e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2063168
Commit-Queue: Sami Kyöstilä <skyostil@chromium.org>
Reviewed-by: Finnur Thorarinsson <finnur@chromium.org>
Cr-Commit-Position: refs/heads/master@{#742708}

Switch from a symbol that is no longer present in the macOS SDK to
a string that is undocumented.

Bug: 1053786
Change-Id: Ibed8b3a53a7280182b85e2cfeec7acd0bdabf53e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2063732
Auto-Submit: Avi Drissman <avi@chromium.org>
Commit-Queue: Reilly Grant <reillyg@chromium.org>
Commit-Queue: Matt Mueller <mattm@chromium.org>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Matt Mueller <mattm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#742707}

Fixes Android instrumentation tests that use EmbeddedTestServerRule
leaving behind a zombie server process if they crash. This is typically
not much of an issue, as the next test to use EmbeddedTestServerRule
will pick a free port instead of the one in use, but a number of tests
have to set a static port due to being render tests (and a variable port
will cause the test to fail due to the port being visible in the URL
bar).

Bug: 1019983
Change-Id: I9adcb22e75ebf0f83d15db6c825e896e618e8f36
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2056935Reviewed-by: John Budorick <jbudorick@chromium.org>
Reviewed-by: Alexander Cooper <alcooper@chromium.org>
Commit-Queue: Brian Sheedy <bsheedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#742706}

The current structure looks (in a very abstract form for readability,
e.g. <div class="collapsible"...> -> <collapsible>):
<collapsible>             (stay)
  <expanded>              (remove)
    <line>                (stay)
	  <collapse-button>   (-> collapsible-button)
	  <html-tag>          (stay)
	<collapsible-content> (-> expanded-content)
	  <collapsible>       (stay)
	<line>                (stay)
	  <html-tag>          (stay)
  <collapsed>             (-> collapsed-content,
                              become <text>...</text>,
                              move under <collapsible>)
    <line>                (remove)
	  <expand-button>     (merged to collapsible-button)
	  <html-tag>          (remove)
	  <text>...           (remove)
	  <html-tag>          (remove)

The changed structure looks:
<collapsible>
 <line>
   <collapsible-button>
   <html-tag>
 <expanded-content>
   <collapsible>
 <collapsed-content>...
 <line>
   <html-tag>

The saving in terms of number of elements ranges 20%-30% depending on the size of the text in an XML element. For example, a longer text in XML will create more HTML elements, which means the saving ratio is higher in that case.

Tested XML files (from random searches):
  https://www.sitemaps.org/sitemap.xml
  https://ririkaburbe.tk/sitemap_0.xml
  http://big5.sputniknews.cn/export/rss2/archive/index.xml

Change-Id: Ibfefb175b58bc54c3f31e65456ff832d432d5c6a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2062797
Commit-Queue: Dong-Hwi Lee <leedh@google.com>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#742705}

from chrome:// to components:// and update all references.

Bug: 1052375
Change-Id: I3ecfc036d1b7aa527151db2ed2d9bb7389ae2bc6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2062274
Commit-Queue: Mugdha Lakhani <nator@chromium.org>
Reviewed-by: Colin Blundell <blundell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#742704}

The 3 values are kDefault, kBuiltin, kSystem. When the value is
kDefault, the NetworkContext will check
net::features::kCertVerifierBuiltinFeature for which verifier to use.

This means that services_unittests and other build targets which use the
network service but don't have explicit handling for the
use_builtin_cert_verifier setting will now use the expected default
implementation of the verifier instead of always using the system
verifier.

Bug: 1049869
Change-Id: I74d20c2bb153e34074dc35269927b582eb5c61a2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2058004Reviewed-by: Pavol Marko <pmarko@chromium.org>
Reviewed-by: Clark DuVall <cduvall@chromium.org>
Reviewed-by: Emily Stark <estark@chromium.org>
Commit-Queue: Matt Mueller <mattm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#742703}

This CL removes all studies in fieldtrial_testing_config.json where
neither the study name nor any of enabled or disabled feature names
appear as a string literal elsewhere in the codebase.

Bug: 1045530, 1053702
Change-Id: If46efd7269250a7f3d18ca2d234a72d8e08bde12
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2063133
Commit-Queue: Balazs Engedy <engedy@chromium.org>
Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#742702}

AutofillPopupBaseView should not handle user events for its children.
This CL cleans up user-event functions from AutofillPopupBaseView.

Bug: 1045401
Change-Id: I6fd91fa99b6de060393bd89c2fc2171209882fda
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2050273
Commit-Queue: Vidhan Jain <vidhanj@google.com>
Reviewed-by: Matthias Körber <koerber@google.com>
Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#742701}

This feature is on at 50% of stable with no known issues.

TBR=sadrul@chromium.org

Bug: 620927
Change-Id: I1d2ef64003a56714f648662f1571c8d99fe7a44f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2055184
Commit-Queue: Saman Sami <samans@chromium.org>
Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Cr-Commit-Position: refs/heads/master@{#742700}

incognito.

This CL updates the profile passing to HelpAndFeedback activity from
CredentialLeakDialogBridge. Currently, it is always regular profile,
however it is not safe because of possible data leakage from incognito
to regular profile.

This CL updates CredentialLeakDialogBridge to receive the current
profile (i.e., regular or off-the-record profile) of current tab and
pass it to HelpAndFeedback activity.

Bug: 1041781
Change-Id: Ia36d7d604d41f1dff72ed7acd4ac6dfcdafdb3bf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2063020Reviewed-by: Ramin Halavati <rhalavati@chromium.org>
Reviewed-by: Ioana Pandele <ioanap@chromium.org>
Commit-Queue: Side YILMAZ <sideyilmaz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#742699}

NOTRY=true

Change-Id: Ibef4ab717ab4bc38313abec958434143a7fb3456
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2053930
Commit-Queue: John Chen <johnchen@chromium.org>
Reviewed-by: Caleb Rouleau <crouleau@chromium.org>
Cr-Commit-Position: refs/heads/master@{#742698}

When the enable-reader-mode flag is set, users by default see
the reader mode icon in the omnibox for all articles which can
be distilled by reader mode. This adds a feature variable which
allows users to decide in chrome://settings/appearance whether
they want to be shown the reader mode icon in the omnibox
when available.

Bug: 1041589
Change-Id: I6205323ff4eccf47f8c776829525f34adda0f899
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2039336
Commit-Queue: Katie Dektar <katie@chromium.org>
Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Reviewed-by: Wei-Yin Chen (陳威尹) <wychen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#742697}

Used https://cs.chromium.org/chromium/src/tools/perf/experimental/story_clustering/README.md
to find representative stories.

Bug: 1051558
Change-Id: I2a4169c8549e1ee6ed0b9d78b9ef7819ab791e42
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2050735
Commit-Queue: Timothy Dresser <tdresser@chromium.org>
Reviewed-by: Caleb Rouleau <crouleau@chromium.org>
Cr-Commit-Position: refs/heads/master@{#742696}

Sample run:
https://ci.chromium.org/p/chromium/builders/ci/Deterministic%20Linux/26874

No-Try: true
Bug: 1040247
Change-Id: Idf8f06a1899c8ef66b9b2355f6d9aad57577efa6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2062986Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Sergey Poromov <poromov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#742695}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/2d44550a1bd9..3db377c1c2ae


Created with:
  gclient setdep -r src-internal@3db377c1c2ae

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

https://skia.googlesource.com/skia.git/+log/86b4388fdcb4..5f1ad0dc47b5

git log 86b4388fdcb4..5f1ad0dc47b5 --date=short --first-parent --format='%ad %ae %s'
2020-02-19 mtklein@google.com rm release swiftshader msan bots
2020-02-19 brianosman@google.com Reland "Move runtime shader/colorfilter into SkRuntimeEffect.cpp"
2020-02-19 fmalita@chromium.org Clip-only tiling in Viewer
2020-02-19 brianosman@google.com Switch SPIRV-Cross to use third_party GN template

Created with:
  gclient setdep -r src/third_party/skia@5f1ad0dc47b5

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

BUG=1023913

Change-Id: I8f0364896d0cc5d4480aa293ddf38c61daea617e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2036350
Commit-Queue: Avi Drissman <avi@chromium.org>
Reviewed-by: ccameron <ccameron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#742692}

When tests are initialized, some of them try to set a test input
method factory. However, they fail to do so, because
OzonePlatform::InitializeUi is called earlier. That method does
various initialization and also sets the input method factory.

Previously, we used to set the factory in CreateInputMethod method
if that hasn't been set yet. (see https://crrev.com/c/1531600),
but after https://crrev.com/c/1798263, that functionality was
moved back to InitializeUi. We didn't run any tests with Wayland
and couldn't spot this problem. However, now, I'm enabling
views_unittests, and that problem was hit.

Thus, to fix the issue, let the GtkUi call CreateInputMethod to
give an OzonePlatform chance to set an input method. If it is
not set, then use gtkui provided one.

Bug: 578890
Change-Id: Ic09de5a18a1ff969e1a96977a987f09cac1129f5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2062974Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
Commit-Queue: Maksim Sisov <msisov@igalia.com>
Cr-Commit-Position: refs/heads/master@{#742691}

In r738875 we stopped marking ancestors if overflow recalc flags
were already present, however by mistake the code was checking
SelfNeedsLayoutOverflowRecalc() instead of
ChildNeedsLayoutOverflowRecalc().

This improves the performance in
perf_tests/shadow_dom/v1-small-deep-distribution.html.

BUG=1051342,941180

Change-Id: Ie94432dd6f207b5abc20132a85ee677a7994a9d3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2055084Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Commit-Queue: Manuel Rego <rego@igalia.com>
Cr-Commit-Position: refs/heads/master@{#742690}

Added corresponding unit tests for new conversions.

This change is needed in order to support new changes
to ScrollTimeline, which needs to be able to support
-infinity and infinity values. The infinity values
were already covered, but -infinity values were not.

https://chromium-review.googlesource.com/c/chromium/src/+/2028173

Change-Id: I634860353782cf56a560228bf37903395b400dc6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2038130Reviewed-by: Clemens Arbesser <arbesser@google.com>
Reviewed-by: Yuri Wiitala <miu@chromium.org>
Commit-Queue: Jordan Taylor <jortaylo@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#742689}

https://android.googlesource.com/platform/external/perfetto.git/+log/526921b3db19..7e63268dc86c

git log 526921b3db19..7e63268dc86c --date=short --first-parent --format='%ad %ae %s'
2020-02-19 skyostil@google.com TrackEvent: Switch from ssize_t to ptrdiff_t
2020-02-19 treehugger-gerrit@google.com Merge "traced_perf: enable by default"
2020-02-19 lalitm@google.com Merge "tp: add support for dynamic tables and migrate flamegraph/counter dur"
2020-02-19 lalitm@google.com tp: fix parsing of counter events from Chromium
2020-02-19 treehugger-gerrit@google.com Merge "Improve logging on session creation"
2020-02-19 ilkos@google.com Merge "Normalize special symbols"
2020-02-19 skyostil@google.com Merge "TrackEvent: Fix missing include for 'ssize_t'"
2020-02-19 treehugger-gerrit@google.com Merge "TrackEvent: Fix namespace confusion with trace point"
2020-02-18 ilkos@google.com Merge "Support java.lang.Class remapping"
2020-02-18 treehugger-gerrit@google.com Merge "Add PERFETTO_EXPORT annotations"
2020-02-18 treehugger-gerrit@google.com Merge "TrackEvent: Fix warning about missing braces around std::array initializer."
2020-02-18 treehugger-gerrit@google.com Merge "Expose bytes written to TraceWriter to client API."
2020-02-18 treehugger-gerrit@google.com Merge "Improve logging if creating ftrace fails."
2020-02-18 treehugger-gerrit@google.com Merge "TrackEvent: Add category tags and groups"
2020-02-18 treehugger-gerrit@google.com Merge "Do not log /proc/self/page_idle error in client."
2020-02-18 ddrone@google.com Merge "Parse all fields in ChromeLatencyInfo message"
2020-02-18 taylori@google.com perfetto-ui: Processes with heap profiles first
2020-02-18 treehugger-gerrit@google.com Merge "traced_perf: basic metatracing"

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

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: chromium:149198396,chromium:149804989
Tbr: perfetto-bugs@google.com
Change-Id: If992fbacdb68dd8293a4c758391bf9f4949bce63
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2064348Reviewed-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@{#742688}

Looks like it's no longer needed.

Change-Id: Idbf3d5a8fbd4f75c2c0f7c998e2617b8542dfb5c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2062296
Commit-Queue: Robert Sesek <rsesek@chromium.org>
Auto-Submit: Nico Weber <thakis@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#742687}

When posting tasks with base::PostDelayedTask(), explicitly specify whether the
tasks should run on the thread pool on a specific named thread. This is in
preparation for making it always mandatory to specify the destination for posted
tasks.

This patch has no functional changes.

This CL was uploaded by git cl split.

Bug: 968047
Change-Id: I74434ddac6214f954b040adb8eec904549fc725f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2062338
Commit-Queue: Sami Kyöstilä <skyostil@chromium.org>
Reviewed-by: Camille Lamy <clamy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#742686}

This is a speculative fix, waiting for me to figure out how to trybot
it :)

Change-Id: Ibc74b5cb94eff639abe8c4032fda1714445a69b2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2062678
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#742685}

Prevent sync XHR from being fired in a child frame when the unload handler was attached from a parent document.

As of M80, sync XHR during page dismissal is not allowed by default. However, it was still possible to send a sync XHR request during dismissal by attaching an unload handler defined in the parent document to a child frame from the parent's script. This change prevents that from happening. (Note: It is still possible to schedule a sync XHR during a page dismissal, ie doing a SetTimeout in a beforeUnload handler that will do the synchronous XHR.)

This change also removes some use counters that are no longer needed.

Bug: 1044348
Change-Id: Ieab8fd018d61aecc75241c6d7d01ad6c08eff7da
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2032426
Commit-Queue: Katie Dillon <kdillon@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
Cr-Commit-Position: refs/heads/master@{#742684}

Bug: 1037793
Change-Id: Iee42f82af527875c936310764f323942c8f97023
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2062983Reviewed-by: Richard Knoll <knollr@chromium.org>
Commit-Queue: Alex Chau <alexchau@chromium.org>
Cr-Commit-Position: refs/heads/master@{#742683}

Log these UserActions from the controller, so they get logged on
Android as well.

Bug: 1040091
Change-Id: I2f938d54c376b88d020e2a576d7dd2348c1b64ae
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2063130Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Commit-Queue: Christian Dullweber <dullweber@chromium.org>
Auto-Submit: Christian Dullweber <dullweber@chromium.org>
Cr-Commit-Position: refs/heads/master@{#742682}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/ac15544d..07a0ee92

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

Currently, there are a few kiosk tests which are failing when we most
probably get to STATUS_ERROR of KioskAppData. Let's add a log line
which will indicate whether it's a fake cws issue.

Bug: 1044417
Change-Id: I685d10c7cab773d3b7ee5a9f2d426ef2eea8da59
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2062444Reviewed-by: Sergey Poromov <poromov@chromium.org>
Commit-Queue: Anatoliy Potapchuk <apotapchuk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#742680}

Allow an optional RepeatingCallback<std::string()> to be supplied to
ScopedRunLoopTimeout, to provide an additional message string in case of
timeout.

Update base::test::TaskEnvironment to have DescribeAllPendingTasks'
output appending to the timeout message.

Bug: 1021777
Change-Id: I32ff686924aea50cc56b6f103696bdbde7e8d8fd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2062984
Auto-Submit: Wez <wez@chromium.org>
Reviewed-by: Gabriel Charette <gab@chromium.org>
Commit-Queue: Gabriel Charette <gab@chromium.org>
Commit-Queue: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#742679}

Bug: 710376
Change-Id: I0c28c2cfbc6a034bbe41d68b6b1e021408365ff7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2062339Reviewed-by: Ken Rockot <rockot@google.com>
Commit-Queue: Robert Sesek <rsesek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#742678}

This wipes out obsolete references to Service Manager in service-related
documentation and replaces it with simpler docs reflecting the new
service model.

Bug: None
Change-Id: Iab5662bcc48b34954a9003532cd407058e470282
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2063773
Commit-Queue: Ken Rockot <rockot@google.com>
Reviewed-by: Oksana Zhuravlova <oksamyt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#742677}

This CL gets rid of InputHandlerProxy::RouteToTypeSpecificHandler
and instead, uses InputHandlerProxy::HandleInputEventWithLatencyInfo
so that events get injected at an interface level.

Bug: 1041898
Change-Id: Id371e9fb544ea5906bd09fe4b66e3d2a261adc8d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2001288Reviewed-by: David Bokan <bokan@chromium.org>
Commit-Queue: Rahul Arakeri <arakeri@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#742676}

With the recent ArrayBuffer refactoring, the backing store memory is
announced to the GC when it gets wrapped by a JSArrayBuffer object. The
assumption is that backing store memory is always wrapped by a
JSArrayBuffer object. However, the bug report shows one example where
this is not the case. When an ArrayBuffer is post-messsaged to a Worker
but the Worker never takes the ArrayBuffer out of the message, then
the backing store memory becomes dead before it ever gets wrapped by a
JSArrayBuffer object. Therefore the GC does not know about the memory
used by the backing store and does not trigger garbage collection.

With this CL the MessageEvent now announces the backing store memory to
the GC. With that, garbage collection is triggered, and the backing
store memory is collected as expected.

R=haraken@chromium.org

Bug: chromium:1049005
Change-Id: I517f65a4cb1546ae469be29514183314f62e3d42
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2044272
Commit-Queue: Andreas Haas <ahaas@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#742675}

This reverts commit f9a31275.

Reason for revert: users must have migrated to prefs after 9 months.
Clients that haven't migrated meanwhile will incur in additional data
downloaded from sync servers, and may worst-case run into undeletions if
they were unlikely enough to have pending local deletions.

Previous patch was reverted earlier due to running into sync protocol
violations. This patch also introduces cleaning up of Directory on GUID
mismatch.

Original change's description:
> Reland "Reintroduce sync cache GUID migration logic from directory to prefs"
>
> This reverts commit 631967a6.
>
> Reason for revert: suspect of running into sync protocol violations and the corresponding DCHECK failures.
>
> Original change's description:
> > Revert "Reintroduce sync cache GUID migration logic from directory to prefs"
> >
> > This reverts commit 37ca67ee with
> > various non-trivial updates to the patch due to git conflicts as well
> > as logic having evolved meanwhile.
> >
> > Reason for revert: users must have migrated to prefs after 9 months.
> > Clients that haven't migrated meanwhile will incur in additional data
> > downloaded from sync servers, and may worst-case run into undeletions if
> > they were unlikely enough to have pending local deletions.
> >
> > Original change's description:
> > > Reintroduce sync cache GUID migration logic from directory to prefs
> > >
> > > After some back and forth, we've concluded that there's too much risk
> > > involved in assuming most clients have already migrated to prefs, i.e.
> > > cache GUID and birthday populated.
> > >
> > > As middle ground, we keep considering the values in prefs the
> > > authoritative ones, but if empty, we populate them from the sync
> > > directory. This adds some complexity, but allows us to defer the more
> > > aggressive turndown (disable migration), which in addition can now be
> > > guarded behind a feature toggle.
> > >
> > > Bug: 923285
> > > Change-Id: I11c4814dae1810c34c1473af36ace9a1b517067f
> > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1609242
> > > Commit-Queue: Mikel Astiz <mastiz@chromium.org>
> > > Reviewed-by: Marc Treib <treib@chromium.org>
> > > Cr-Commit-Position: refs/heads/master@{#659030}
> >
> > Bug: 923285
> > Change-Id: I35cad35fdd398db08ee3a5cea82eaee5ebd9e980
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2022787
> > Commit-Queue: Mikel Astiz <mastiz@chromium.org>
> > Reviewed-by: Marc Treib <treib@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#735486}
>
> TBR=treib@chromium.org,mastiz@chromium.org
>
> # Not skipping CQ checks because original CL landed > 1 day ago.
>
> Bug: 923285, 1048771
> Change-Id: Ie19c4d300428d59358921e55800337fbf10f0f64
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2042617
> Commit-Queue: Rushan Suleymanov <rushans@google.com>
> Reviewed-by: Mikel Astiz <mastiz@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#739375}


Bug: 923285, 1048771
Change-Id: I900235b66fd0186aece1d05eb1e99da70f2548b2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2061751
Commit-Queue: Rushan Suleymanov <rushans@google.com>
Reviewed-by: Mikel Astiz <mastiz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#742674}

This change implements obtaining the list of saved passwords in
SavedPasswordsPresenter and makes it listen to appropriate events and
notifying its observers.

Bug: 1047726
Change-Id: Ic859e4f1aca19be36d6df8ef525564dc023191ed
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2063129Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org>
Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org>
Cr-Commit-Position: refs/heads/master@{#742673}

This change adds performance metrics previously used in the
SMS Receiver API to the credential manager. It uses the same histograms
to provide continuity with previous iterations of the API. It adds
the following metrics.

1. Blink.Sms.Receive.TimeSuccess
Time from when the API has been called to when it returns a successful
outcome.

2. Blink.Sms.Receive.TimeCancel
Time from when the API has been called to when the user dismisses the
infobar and returns a cancelled outcome.

Bug: 1045231
Change-Id: I36736e1d8c7919541cb91e23154d142e957d9975
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2055891Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Commit-Queue: Ayu Ishii <ayui@chromium.org>
Cr-Commit-Position: refs/heads/master@{#742672}

Using wpt-import in Chromium 3d601f27.
With Chromium commits locally applied on WPT:
ec83d167 "Update performance.measureMemory to the latest proposal"
d5cd6b98 "SharedWorker: Assign unique names to SharedWorkers to avoid unintentional matching"
48b21f05 "Remove `tentative` flag from Fetch Metadata tests."


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

Directory owners for changes in this CL:
mkwst@chromium.org, andypaicu@chromium.org:
  external/wpt/content-security-policy

NOAUTOREVERT=true
TBR=lpz

No-Export: true
Change-Id: I14b91a1dc5a26e6cdffd3d78f12cbcbf305cf61b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2063073Reviewed-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@{#742671}

Video playback is broken in Ozone/Wayland whenever Wayland compositor
announces that R_8 buffer is supported and sends supported format
modifiers for that buffer type.

Then, when video is played, GbmPixmapWayland is created with format
modifiers supplied by Wayland compositor. However, this result in a video
playback that is garbled.

The reason to this is that the buffer is requested to be linear, which
means no format modifiers should be supplied. I believe it could be
the gbm handling that, but it turns out that messes up and we have
weird behaviour.

Thus, do not use format modifiers if the buffer usage is linear.

Bug: 1050364
Change-Id: I980c462f857b3a462f95677810e3ff2aaaf340c6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2049978Reviewed-by: Michael Spang <spang@chromium.org>
Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Commit-Queue: Maksim Sisov <msisov@igalia.com>
Cr-Commit-Position: refs/heads/master@{#742670}

This is a minimal change adding a struct representing a Trust Tokens
key commitment registry's contents [1], with some slight variations
described in the Trust Tokens design doc (currently internal-only;
working to release a public version).

This is a common ancestor CL of trust token issuance, redemption,
and key commitment fetching and parsing.

[1]:
https://github.com/alxdavids/draft-privacy-pass/blob/master/draft-privacy-pass.md#key-registration-registry

Bug: 1042962
Change-Id: Ic0a20cb266c8133bb3545821b975e813bfb59c50
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2062674
Commit-Queue: David Van Cleve <davidvc@chromium.org>
Reviewed-by: Charlie Harrison <csharrison@chromium.org>
Cr-Commit-Position: refs/heads/master@{#742669}