GitLab

This is a follow-up of https://crrev.com/c/2189716. As including
//net/quic/quic_transport_client.h from
//services/network/public/cpp/quic_transport_error_mojom_traits.h
led to build errors this CL splits the net::QuicTransportError
definition into a new file.

Bug: 1069744
Change-Id: I406a0d2f8f1c682aa9b36ad48eb6629e281f12c9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2203242
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Eric Roman <eroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#769616}

Profile::DestroyOffTheRecordProfile function without arguments is
deprecated and replaced with a function that receives the OTR profile.
The few remaining use cases of the function are replaced with the new
API and the old function is removed.

Bug: 1033903
Change-Id: Ie417f4ef12f449774c658228dc3850b65811b3bf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2196168Reviewed-by: Mihai Sardarescu <msarda@chromium.org>
Reviewed-by: Sergey Ulanov <sergeyu@chromium.org>
Reviewed-by: Karan Bhatia <karandeepb@chromium.org>
Commit-Queue: Ramin Halavati <rhalavati@chromium.org>
Cr-Commit-Position: refs/heads/master@{#769615}

VariationsClient::IsIncognito returns true for all off-the-record
profiles and is always initialized with BrowserContext::IsOffTheRecord.
To remove misinterpretations, the function is renamed to IsOffTheRecord.

This CL does not create any behavioral change.

Bug: 968028, 1074201
Change-Id: I19a0a81794e7838c8f882faa6aeab9d7b085f756
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2202980Reviewed-by: Colin Blundell <blundell@chromium.org>
Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Reviewed-by: Jesse Doherty <jwd@chromium.org>
Reviewed-by: Mihai Sardarescu <msarda@chromium.org>
Commit-Queue: Ramin Halavati <rhalavati@chromium.org>
Cr-Commit-Position: refs/heads/master@{#769614}

TBR=thakis@chromium.org

Cq-Include-Trybots: chrome/try:mac-chrome
Cq-Include-Trybots: chrome/try:win-chrome
Cq-Include-Trybots: chrome/try:win64-chrome
Bug: 1071576
Change-Id: I69d9d2756f10835942dfd47d8ab239cc35443c30
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2206217Reviewed-by: Yuke Liao <liaoyuke@chromium.org>
Commit-Queue: Yuke Liao <liaoyuke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#769613}

This reverts commit 03ac3720.

Caused syncing breakages; see bug.

Tbr: tluk@chromium.org
Bug: 1083381
Change-Id: I46516c7a8a2969bf58f188dcc0f91789f338d4fb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2206214Reviewed-by: George Burgess <gbiv@chromium.org>
Reviewed-by: Erik Chen <erikchen@chromium.org>
Commit-Queue: George Burgess <gbiv@chromium.org>
Cr-Commit-Position: refs/heads/master@{#769612}

Disable geolocation-api/watchPosition-page-visibility.html blink web test.
It's flaky on OSX.

TBR=scheib@chromium.org

Bug: 1083824
Change-Id: Ice34348bc3e9e6de24b04859269c04d379b2be7d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2206194Reviewed-by: Alexey Baskakov <loyso@chromium.org>
Commit-Queue: Alexey Baskakov <loyso@chromium.org>
Cr-Commit-Position: refs/heads/master@{#769611}

We should use the default value if the key does not exist. And if the
key does not exist and no default value is specified, set the value to
null.

Bug: 980846
Test: Manually
Change-Id: I82d7a7e35284d0816da8a0cc09853c5106a705e0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2131667
Auto-Submit: Wei Lee <wtlee@chromium.org>
Reviewed-by: Shik Chen <shik@chromium.org>
Commit-Queue: Wei Lee <wtlee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#769610}

This will allow WebLayer to reuse webshare java code.

1. Portions of share are moved to //components/browser_ui/share
   * ShareDialogAdapter
   * ShareImageFileUtils[Test]
   * ShareParams
     - saveLastUsed and shareDirectly are only used in Chrome, so are
       removed from shareParams. saveLastUsed is implemented with a
       TargetChosenReceiver.
   * parts of ShareHelper
     - TargetChosenReceiver and some helper functions
     - custom share dialog for sdk <= 21

2. Almost all of webshare is moved to //components/browser_ui/webshare
   * ShareServiceImplementationFactory is left behind
   * WebShareDelegate interface is introduced to delegate the share
     implementation (Chrome passes off to the Activity's ShareDelegate)

Bug: 1066285
Change-Id: I0d211c0996e1517267413aa3e569f0cbde21d3e0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2181491
Auto-Submit: Evan Stade <estade@chromium.org>
Commit-Queue: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Reviewed-by: Kyle Milka <kmilka@chromium.org>
Reviewed-by: Eric Willigers <ericwilligers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#769609}

This reverts commit 91cc0984.

Reason for revert: Other tests still flaking on mac
eg. https://ci.chromium.org/p/chromium/builders/ci/Mac10.11%20Tests/50389

Original change's description:
> Reland "Implement capture of metrics events for web app daily
> interaction."
> 
> Disabled 3 tests on Mac as they are failing/flaky.
> 
> Original CL: crrev.com/c/2160638
> Revert CL: crrev.com/c/2203240
> 
> Original change's description:
> > Implement capture of metrics events for web app daily interaction.
> >
> > Captures basic static information on all web apps used and more detailed
> > sums of foreground/background duration and session count for installed
> > web apps that are set to open in a window.
> >
> > WebAppMetrics now listens on BrowserList events and TabStripModel
> > changes in order to determine when web apps move into the foreground or
> > background. It keeps a record of the last time each web app was seen so
> > that intervening time can be counted as foreground time if switching
> > away from the web app (and background time if switching to the web app).
> >
> > Tbr: achuith@chromium.org
> > Bug: 1026148
> > Bug: 1081187
> > Change-Id: Iae6460c678b59380cf0fad8408e2014918bc2864
> > Fixed: 1026148
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2160638
> > Commit-Queue: Glen Robertson <glenrob@chromium.org>
> > Reviewed-by: Dominick Ng <dominickn@chromium.org>
> > Reviewed-by: Alan Cutter <alancutter@chromium.org>
> > Auto-Submit: Glen Robertson <glenrob@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#769125}
> 
> TBR=achuith@chromium.org,dominickn@chromium.org
> 
> Fixed: 1026148
> Bug: 1026148
> Bug: 1081187
> Bug: 1083813
> Change-Id: I38d92958255c4db055ddfa3b731de9309dd7219c
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2206060
> Commit-Queue: Glen Robertson <glenrob@chromium.org>
> Reviewed-by: Glen Robertson <glenrob@chromium.org>
> Reviewed-by: Alan Cutter <alancutter@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#769600}

TBR=achuith@chromium.org,alancutter@chromium.org,dominickn@chromium.org,glenrob@chromium.org

Change-Id: I7d5ca8e984f305f0a56d0f6f49941e26beb816f7
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 1026148, 1081187, 1083813
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2206294Reviewed-by: Glen Robertson <glenrob@chromium.org>
Commit-Queue: Glen Robertson <glenrob@chromium.org>
Cr-Commit-Position: refs/heads/master@{#769608}

This CL helps with:

1. Meeting one of the requirements that says "Ideal proposal should be
   as close to a drop-in replacement for raw pointers as possible"

2. Compiling a handful of places in Chromium that depend on these
   operators.  So far we know about:
     .../blink/renderer/core/css/parser/css_parser_token_range.h:45
     third_party/blink/renderer/platform/json/json_parser.cc:187
     third_party/blink/renderer/platform/json/json_parser.cc:85
     components/metrics/file_metrics_provider_unittest.cc:252

Bug: 1073933
Change-Id: Icb69c906dd1cfad2cc6242e81517969ff0da344c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2199177Reviewed-by: Bartek Nowierski <bartekn@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Bartek Nowierski <bartekn@chromium.org>
Cr-Commit-Position: refs/heads/master@{#769607}

Instead of the ctor registering the newly created scheduler with the
"parent" scheduler (page scheduler for frame scheduler, main thread
scheduler for page scheduler), the parent now creates the new child
scheduler and then registers it.

Change-Id: I903ac5d459827fabbce86b6b5a95b747f856e9ce
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2198447
Commit-Queue: Tal Pressman <talp@chromium.org>
Reviewed-by: Alexander Timin <altimin@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#769606}

https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/85ae1392c509..074a542237bb

git log 85ae1392c509..074a542237bb --date=short --first-parent --format='%ad %ae %s'
2020-05-18 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update DevTools DEPS.

Created with:
  gclient setdep -r src/third_party/devtools-frontend/src@074a542237bb

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

... to ListBoxSelectType.
This function is used for |option:-internal-spatial-navigation-focus|
selector matching, and it's unnecessary for menulist SELECTs because
OPTIONs in menulist SELECTs are not rendered by CSS.

This CL has no behavior changes.

Bug: 1052232
Change-Id: Id71c303ebe75113acb767656b41fd4b21eb5a972
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2206136
Commit-Queue: Yoshifumi Inoue <yosin@chromium.org>
Auto-Submit: Kent Tamura <tkent@chromium.org>
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#769604}

This CL replaces the PrintHostMsg_DidPrepareDocumentForPreview
IPC message with a new DidPrepareDocumentForPreview Mojo method
in the PrintPreviewUI interface.

Bug: 1008939
Change-Id: I0ecdb60982baf3074af290005502204080f9cc44
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2201496
Commit-Queue: Julie Kim <jkim@igalia.com>
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Reviewed-by: Sam McNally <sammc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#769603}

This is towards allowing apps to run with no windows open.

Two different messages differentiated here:
- applicationWillBecomeActive (aka Focus)
  - happens when any window in the app is focused, or when the app
    is command-tabbed to be active
  - should focus existing windows
- applicationShouldHandleReopen (aka Reopen)
  - happens when the dock icon is clicked
  - should launch a new window if no window is open

It used to be that Focus was used by legacy apps and ignored by
PWAs. Also, Focus was used to re-open the app (inappropriately), and
also was used to close the app if it somehow was uninstalled while
still running.

Update the legacy app behavior to open new windows only on Reopen,
and remove the "close the app" behavior.

The next step here will be to handle Reopen for PWAs, and to allow
them to keep running even if no windows are open.

Bug: 1080729
Change-Id: I5bf86e7e7874b71c030d8dc9c5440ee7fec430d2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2197231
Commit-Queue: ccameron <ccameron@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Cr-Commit-Position: refs/heads/master@{#769602}

Change-Id: I0ad2659380ca0792dc7b779e3669186720be5896
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2203786Reviewed-by: Nancy Wang <nancylingwang@chromium.org>
Reviewed-by: Jeevan Shikaram <jshikaram@chromium.org>
Commit-Queue: Nancy Wang <nancylingwang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#769601}

interaction."

Disabled 3 tests on Mac as they are failing/flaky.

Original CL: crrev.com/c/2160638
Revert CL: crrev.com/c/2203240

Original change's description:
> Implement capture of metrics events for web app daily interaction.
>
> Captures basic static information on all web apps used and more detailed
> sums of foreground/background duration and session count for installed
> web apps that are set to open in a window.
>
> WebAppMetrics now listens on BrowserList events and TabStripModel
> changes in order to determine when web apps move into the foreground or
> background. It keeps a record of the last time each web app was seen so
> that intervening time can be counted as foreground time if switching
> away from the web app (and background time if switching to the web app).
>
> Tbr: achuith@chromium.org
> Bug: 1026148
> Bug: 1081187
> Change-Id: Iae6460c678b59380cf0fad8408e2014918bc2864
> Fixed: 1026148
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2160638
> Commit-Queue: Glen Robertson <glenrob@chromium.org>
> Reviewed-by: Dominick Ng <dominickn@chromium.org>
> Reviewed-by: Alan Cutter <alancutter@chromium.org>
> Auto-Submit: Glen Robertson <glenrob@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#769125}

TBR=achuith@chromium.org,dominickn@chromium.org

Fixed: 1026148
Bug: 1026148
Bug: 1081187
Bug: 1083813
Change-Id: I38d92958255c4db055ddfa3b731de9309dd7219c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2206060
Commit-Queue: Glen Robertson <glenrob@chromium.org>
Reviewed-by: Glen Robertson <glenrob@chromium.org>
Reviewed-by: Alan Cutter <alancutter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#769600}

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

Cq-Include-Trybots: luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast
Tbr: cr-fuchsia+bot@chromium.org
Change-Id: Ic5d203135090b43762fb8870b3e4bd81bc236dc7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2205865Reviewed-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@{#769599}

Disable document-level-wheel-event-listener-passive-by-default.html
blink web tests. It's flaky on OSX.

TBR=foolip@google.com

Bug: 1083820
Change-Id: I45825417ff760ff95c439d357170627c6acfe09e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2206139
Commit-Queue: Alexey Baskakov <loyso@chromium.org>
Reviewed-by: Alexey Baskakov <loyso@chromium.org>
Cr-Commit-Position: refs/heads/master@{#769598}

Every new method in exo::KeyboardDelegate causes a lot of warning logs
when running exo_unittests.
This CL makes tests use NiceMock so that adding new method won't
generate 'Unexpected call' warning anymore.

Test: exo_unittests
Change-Id: I7fef2958c66f3a5d440e9cbabaa33d7c4c0dd5c5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2203159Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Commit-Queue: Yuichiro Hanada <yhanada@chromium.org>
Cr-Commit-Position: refs/heads/master@{#769597}

This patch rehauls logging in ArcNetHostImpl:
 - Remove most VLOGs which were used in the past for development of new
 features but are not useful anymore and only add noise to logs.
 - Remove a couple of ERROR logs for the same reason.
 - Drop some ERROR logs to WARNING level when some shill properties are
 not found.
 - Add new ERROR logs for various failure callback invocations and
 net.mojom APIs serverd by ArcNetHostImpl.

BUG=crbug:823460
BUG=b:145960788
TEST=Compiled, flashed eve, basic connectivity tests.

Change-Id: I7fcb4306f2156c24633a43cbd9618267c3ca256e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2203079
Commit-Queue: Hugo Benichi <hugobenichi@google.com>
Reviewed-by: Yusuke Sato <yusukes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#769596}

This is needed to correctly isolate any DNS requests made by PPAPI in
the context of one page from those made in the context of other pages.

This is a reland of a CL that has been reverted 3 times due to flaky
tests on the bots. Unable to figure out what's going on with the tests,
and unable to repro locally, I've finally given up on them. The way
they were failing is likely due to DNS cache issues, rather than due to
the code itself being flaky.

Bug: 1021661
Change-Id: I261e9890198586ede4ad71377800206dd1a7eedc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2199682Reviewed-by: Eric Orth <ericorth@chromium.org>
Reviewed-by: Raymes Khoury <raymes@chromium.org>
Commit-Queue: Matt Menke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#769595}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/9e5a41a61ae5..4f2b72ed4f28


Created with:
  gclient setdep -r src-internal@4f2b72ed4f28

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 loyso@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: loyso@google.com
Change-Id: Ie888f00108bbf6252688858d44f63aa9e2afaf7f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2205864Reviewed-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@{#769594}

AccessibilityFocusHighlightBrowserTest.DrawsHighlight test is flaky of OSX.

TBR=dtseng@chromium.org

Bug: 1083806
Change-Id: I2a2524e5aeb1a775d58af25c19bdf3f0a0d53bd1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2206135Reviewed-by: Alexey Baskakov <loyso@chromium.org>
Commit-Queue: Alexey Baskakov <loyso@chromium.org>
Cr-Commit-Position: refs/heads/master@{#769593}

This reverts commit 652185a0.

Reason for revert: breaks internal tests with cleartext network violation

Original change's description:
> Default enable QUIC in Cronet Android and IOS.
>
> This change introduces no API changes. But API documents need to be updated.
>
> Change-Id: Ibc347df79066de704c5be0683c5b658ba6e1896a
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2168553
> Commit-Queue: Renjie Tang <renjietang@chromium.org>
> Reviewed-by: Zhongyi Shi <zhongyi@chromium.org>
> Reviewed-by: Misha Efimov <mef@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#765334}

TBR=mef@chromium.org,zhongyi@chromium.org,renjietang@chromium.org


Change-Id: Ieaf036a010dc501c246a2aeedae824c2e7a35f98
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2205121Reviewed-by: Zhongyi Shi <zhongyi@chromium.org>
Reviewed-by: Victor Vasiliev <vasilvv@chromium.org>
Commit-Queue: Victor Vasiliev <vasilvv@chromium.org>
Cr-Commit-Position: refs/heads/master@{#769592}

Disable AccessibilityHitTestingBrowserTest.
CachingAsyncHitTestMissesElement_WithPinchZoom
test. It times out on Linux.

TBR=kschmi@microsoft.com

Bug:1083805

Change-Id: I40927d173d8440f5e126119dbb4c85a8ace77e56
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2206133Reviewed-by: Alexey Baskakov <loyso@chromium.org>
Commit-Queue: Alexey Baskakov <loyso@chromium.org>
Cr-Commit-Position: refs/heads/master@{#769591}

This CL update existing file icons in launcher search to new GM2 design.
I've tested (looked at the icon) on some formats (archive, gform, gsite,
folder, gslide, gsheet, gdoc, pdf) and it looked fine.

Bug: 1081586
Change-Id: I68ad2443928605fbe0550855f6adb08c026d81b5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2195107Reviewed-by: Noel Gordon <noel@chromium.org>
Reviewed-by: Jia Meng <jiameng@chromium.org>
Commit-Queue: Thanh Nguyen <thanhdng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#769590}

Moves static functions and enums associated with sharing action to
FileTasks. This is due to the fact that sharing with Android apps can
take a path through FileTasks without touching FileManagerCommands. This
CL just prepares the code for the additional UMA records, without
actually adding new recoding actions.

Bug: 1063169
Change-Id: Ic8833574241c0d9502b77356dbbb58c44211cf81
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2198849Reviewed-by: Luciano Pacheco <lucmult@chromium.org>
Commit-Queue: Bo Majewski <majewski@chromium.org>
Cr-Commit-Position: refs/heads/master@{#769589}

There's a race condition with the right-click emoji menu:

1. User clicks "emoji".
2. We change the input_view_url to be the emoji url.
3. We then force the keyboard to show by enabling it temporarily.
4. This will wake up the extension JS code if it's been suspended.
5. Extension JS will listen to 'onActivate' which triggers the engine to
   re-enable.
6. Enabling will reset the input_view_url to be the url specified in the XKB
   manifest and we overwrite the emoji URL set in step 2.

Hence, we need to prevent step 6 from overidding. A crude way to do this to add
a boolean flag to indicate whether the inputview url is currently overridden.
If it's overridden, then enabling the engine should not reset the inputview url.

This is not an ideal solution, but it's the simplest with lowest impact.

Bug: 887612
Change-Id: I5530bb09ab9127bd0c56e86f8e08c89db84b0047
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2198856
Commit-Queue: Darren Shen <shend@chromium.org>
Reviewed-by: Shu Chen <shuchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#769588}

(1) The mojom interface is generated with the script
"chromeos/services/machine_learning/public/mojom/roll_mojoms.sh"
from https://chromium-review.googlesource.com/c/chromiumos/platform2/+/2160576

(2) An implementation and fake implementation are also added for
unit_tests.

Tested: unit tests passed.

Bug: 1054621

Change-Id: Ib74cdaf2332e7003d85601484a4d400bb06c3a66
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2198318Reviewed-by: Charles . <charleszhao@chromium.org>
Reviewed-by: Andrew Moylan <amoylan@chromium.org>
Reviewed-by: Sam McNally <sammc@chromium.org>
Commit-Queue: Charles . <charleszhao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#769587}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/1775de4b56cc..9e5a41a61ae5


Created with:
  gclient setdep -r src-internal@9e5a41a61ae5

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 tluk@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: tluk@google.com
Change-Id: If2c7c4ef9b0414b2824220e0c24bc6827385cea3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2205863Reviewed-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@{#769586}

When saving the CRX file to the cache, we have assumed(before this CL)
without any check that its extension id and version are the same as we
expect from the update manifest. If the time of update request on the
client is close to the extension version update, we may encounter the
issue of cache inconsistency: save cache entry marked with one version,
while in fact it's another.

This CL fixes this problem by inserting in the cache only when the crx
meets the expected requirements from the manifest. This insertion logic
has hence, been moved extension_downloader to the extension_updater
which sets |expectations_passed_callback_| in the crx_installer. This
callback is invoked when the crx passes the expectations and inserts
a new entry in the cache. It also holds the responsibility to delete
the crx file in case cache does not exist or insertion fails.

Browser tests are also included in the CL to verify this fix. A new
update manifest file has been added for testing which mentions an
incorrect version for the contained crx file.
Also fixed the existing tests that fail due to having incorrect
extension version for their crx file.

Bug: 1047637
Change-Id: I6bc291b3f5d21e536a5d8350d34d3dcc222c8f5a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2179543Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: Sergey Poromov <poromov@chromium.org>
Reviewed-by: Oleg Davydov <burunduk@chromium.org>
Commit-Queue: Saurabh Nijhara <snijhara@google.com>
Cr-Commit-Position: refs/heads/master@{#769585}

TBR=thakis@chromium.org

Cq-Include-Trybots: chrome/try:mac-chrome
Cq-Include-Trybots: chrome/try:win-chrome
Cq-Include-Trybots: chrome/try:win64-chrome
Bug: 1071576
Change-Id: I34b70612605b04288bd374ce33c9227fe9f7c4f3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2205981Reviewed-by: Yuke Liao <liaoyuke@chromium.org>
Commit-Queue: Yuke Liao <liaoyuke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#769584}

https://dawn.googlesource.com/dawn.git/+log/a5d54d70915b..275a95c1dc64

git log a5d54d70915b..275a95c1dc64 --date=short --first-parent --format='%ad %ae %s'
2020-05-17 shuizhuyuanluo@gmail.com Fix missing headers with libstdc++ (GCC 10.1)

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

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

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

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

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

This CL:
- Makes WebappActivity use CustomTabActivityTabController
- Deletes WebappActivityModule
- Registers for webapps observers which record custom tab metrics:
  - CustomTabNavigationEventObserver
  - CustomTabObserver
  - PageLoadMetricsObserver

BUG=1082578

Change-Id: I18f2fb38460012dcc79823816667df4569391c3f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2197527
Commit-Queue: Peter Kotwicz <pkotwicz@chromium.org>
Reviewed-by: Peter Conn <peconn@chromium.org>
Cr-Commit-Position: refs/heads/master@{#769582}

https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/1752fd9bc82b..85ae1392c509

git log 1752fd9bc82b..85ae1392c509 --date=short --first-parent --format='%ad %ae %s'
2020-05-17 bmeurer@chromium.org Update acorn to 7.2.0

Created with:
  gclient setdep -r src/third_party/devtools-frontend/src@85ae1392c509

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: chromium:1009927
Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com
Change-Id: I91dcafa3d1ac5ca9a9c4567e97eb16998335aabe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2205861Reviewed-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@{#769581}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/a4653273a837..1775de4b56cc


Created with:
  gclient setdep -r src-internal@1775de4b56cc

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 tluk@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: tluk@google.com
Change-Id: I80449412e793f82c32725acd3a48f3ae930b9724
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2205859Reviewed-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@{#769580}

Previously we request one photo link and then download the photo to
display. But on lock screen we only have limited time to use the access
token, therefore, we request and handle a batch of photo link request.

Bug: b/148462257
Test: new unittests
Change-Id: I42a258f87e5d8b0b452a9b6b40fa981c4d2f6065
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2189697
Commit-Queue: Tao Wu <wutao@chromium.org>
Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#769579}

await set_permission, which is an async function. Somehow, this was
missed in https://crrev.com/c/2065346 and https://crrev.com/c/2200278,
causing some of these tests to flake (1/10 times).

Bug: 1083268, 1082747
Change-Id: Iedf7e63a02d200c76df0aaa431980493c6a35e61
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2204838
Auto-Submit: Darwin Huang <huangdarwin@chromium.org>
Commit-Queue: Victor Costan <pwnall@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#769578}

This CL applies fixes similar to a previous: we do not assume that the
first callback to the PerformanceObserver will include the mousedown
entry and instead abort and wait until a further callback which does
include it.

Bug: 1074048
Change-Id: Ifdf01b0abae025fa67f3ff355324d4b6204111a8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2204618
Auto-Submit: Nicolás Peña Moreno <npm@chromium.org>
Commit-Queue: Yoav Weiss <yoavweiss@chromium.org>
Reviewed-by: Yoav Weiss <yoavweiss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#769577}