GitLab

Tbr=kainino@chromium.org

Bug: dawn:449, dawn:323, dawn:399
Change-Id: I3f1892acad7c636e8c10f852510ed89972411f62
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2226914
Commit-Queue: Kai Ninomiya <kainino@chromium.org>
Reviewed-by: Kai Ninomiya <kainino@chromium.org>
Reviewed-by: Austin Eng <enga@chromium.org>
Auto-Submit: Austin Eng <enga@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774407}

ChromeBackForwardCacheBrowserTest.WebBluetooth Test is flaky.
It is reported as a hidden flake as it passes on retries.

Cause identified:
The test configures a mock Bluetooth adapter first and then performs a
web Bluetooth API call. Although in some executions, it is observed that
the browser has already started the initialization of the default
Bluetooth adapter, when the test configures the mock adapter changing
the adapter pointer, causing that the callbacks from the default adapter
try to use an already released adapter pointer, thus reading from a
nullptr, and crashing the test.

Fix proposed:
Move the MockBluetoothAdapter out from being configured at the specific
test and instead be a class member and configured at test setup.
By doing this the mock adapter is configured from the
beginning avoiding the callback issue observed with the default
Bluetooth adapter.

Bug: 1087190
Change-Id: I3f2e8bd4159f072712f1082f05e35ec24f9b2f5b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2220627
Commit-Queue: Carlos Frias <carlos.frias@microsoft.com>
Reviewed-by: Alexander Timin <altimin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774406}

This will now be enabled by default, but disabled on specific
problematic boards. See go/tethering-client-expansion for
details.

Change-Id: Ia9988e3d6ad3b249f9a80d78b8f8607129218137
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2222296
Commit-Queue: Max Li <themaxli@chromium.org>
Reviewed-by: Ryan Hansberry <hansberry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774405}

Bug: 1070409
Change-Id: I488a2edafed79e209f4ab89d56a54d4dd031b2eb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2224422Reviewed-by: Yusuke Sato <yusukes@chromium.org>
Commit-Queue: Nigel Tao <nigeltao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774404}

This is consistent with the other Alt shortcuts for which we also
have Search shortcuts (Home, End, Bksp) and will aid in the possible
future deprecation/removal of the Alt shortcuts.

Bug: 1090186
Change-Id: Ifce1a066fb5bd5b27850625f759bbf815042147c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2227052
Auto-Submit: Peter Collingbourne <pcc@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Zentaro Kavanagh <zentaro@chromium.org>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Commit-Queue: Ahmed Fakhry <afakhry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774403}

These UMAs are some of the few that help us understand how casting is
used in Chrome, and should be kept around.

Bug: 1088675, 1088676, 1088677, 1088678, 1088679
Change-Id: I1e07e24e58d43f3b1ac4c240d5072466b15222b4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2227174
Auto-Submit: Thomas Guilbert <tguilbert@chromium.org>
Commit-Queue: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774402}

Extend the forced colors mode flag and the high contrast histogram
from M85 to M88.

Bug: 1088533,970285
Change-Id: I565ade742857c64c53a13eee8de8eaf745c21cf0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225752Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Alison Maher <almaher@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#774401}

AX-Relnotes: Omnibox accessibility reliability
Bug: 943105, 1039422
Change-Id: Icf6adebabdcd7d9627c58f3c7260fc5359043fab
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2226061
Commit-Queue: Aaron Leventhal <aleventhal@chromium.org>
Commit-Queue: Tommy Li <tommycli@chromium.org>
Auto-Submit: Aaron Leventhal <aleventhal@chromium.org>
Reviewed-by: Tommy Li <tommycli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774400}

Version "20200601.0" is basically the same as "2019.11.12.0", only with
a generic metrics model name in the meta JSON file.

Note: The version schema is changed from "yyyy.mm.dd.sub" to
"yyyymmdd.sub", that's because Omaha server automatically changes
"2020.06.01.0" to "2020.6.1.0", while we want to keep the origin date
string. All the future versions will be "yyyymmdd.sub".

Bug: 1067048
Test: Tested on DUT
Change-Id: I6b738698fd9b06c9edc666803630115509a736fe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2226104
Commit-Queue: Xinglong Luan <alanlxl@chromium.org>
Reviewed-by: Andrew Moylan <amoylan@chromium.org>
Reviewed-by: Joshua Pawlicki <waffles@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774399}

Change-Id: Id0cade394c0e730348f0bbbf5329444412f172a4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225015Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Tal Pressman <talp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774398}

The new function will allow SysmemBufferWriter users to get direct
mapping to the buffer if they need it.

Bug: b/158033083
Change-Id: Id6aeabf415a65f859d6d0add7015a8a7868946ca
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2206339
Commit-Queue: Sergey Ulanov <sergeyu@chromium.org>
Reviewed-by: David Dorwin <ddorwin@chromium.org>
Reviewed-by: Kevin Marshall <kmarshall@chromium.org>
Auto-Submit: Sergey Ulanov <sergeyu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774397}

The expected default is false, as that is what is used at other layers:
  * net::HttpAuthPreferences
  * prefs::kEnableAuthNegotiatePort
  * key::kEnableAuthNegotiatePort

Using true can cause problems with integrated auth, as it constructs SPNs in the less common way.

Bug: 924746
Change-Id: I2d09f0c72aa2ac8d8f60c1e2adfeb92c379d336b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225531
Commit-Queue: Eric Roman <eroman@chromium.org>
Commit-Queue: Will Harris <wfh@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Reviewed-by: Will Harris <wfh@chromium.org>
Auto-Submit: Eric Roman <eroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774396}

When a user has a web app installed then uninstalled via policy we leave
behind some policy install info in their prefs. This info is used by
CanCreateWebApp() to determine whether there is an app already installed
by policy.
This causes a bug where users cannot install web apps after they've been
removed from policy.

This CL updates the check to also check whether the app is actually
installed and not just check for the presence of the pref data.

Bug: 1090182
Change-Id: I736118cec4e0b1ff34ae335965dc7b8816c20837
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2224417
Auto-Submit: Alan Cutter <alancutter@chromium.org>
Commit-Queue: Dominick Ng <dominickn@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774395}

The histograms show no major regressions on Canary/Dev. We'll need the
increased data volume from Beta to validate the model performance
improvements. Before doing so, enable the new model version in field
trials. This should have no effect, since this parameter chooses a
model version in communication with remote SB servers.

Bug: 1054056
Change-Id: Ifa10a303d880cb05c5176a8813b2bece06a992f0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2216389
Commit-Queue: Daniel Rubery <drubery@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774394}

Android uses the dynamic color gamut to change gamuts as needed based
on the content being displayed. There is a Finch experiment for this
which is rolled out to 50% of Canary and Dev channels.

This CL adds a field trial for that Finch experiment so bots can test
the config.

Change-Id: I112a9dc0f8edb99b39f227a81a7785527717db95
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225622
Commit-Queue: Chris Blume <cblume@chromium.org>
Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774393}

The TODO was introduced in crrev.com/c/548875.

Bug: None
Change-Id: I03f6061787278b04976c53c79760447a98c03346
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2227045Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Yi Gu <yigu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774392}

Users can easily lose work if they drag/drop a file or URL into a tab
that does not consume the dropped data (e.g. as a file upload). Rather
than navigating the current tab (blowing away whatever was in it),
instead open the dropped URL in a new foreground tab.

Bug: 451659
Change-Id: Ic7010a3c933d7747d4b70fefa4d0a5380448c58c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2213459Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Michael Wasserman <msw@chromium.org>
Reviewed-by: Darwin Huang <huangdarwin@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Commit-Queue: Eric Lawrence [MSFT] <ericlaw@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#774391}

Some manual edits have been recorded in the form of "NOTE" comments,
since the generation script still has some bugs.

Bug: 1081815
Change-Id: I2d2fb4cf82d0b1467a0afd335cd61a3c68688990
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2212998Reviewed-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Commit-Queue: dpapad <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774390}

Custom scrollbar parts don't have children. They act more like special
replaced elements. Letting LayoutCustomScrollbarPart inherit
LayoutReplaced can reduce cost.

Change-Id: I496aa9c331485a2ff4a0bbe5c9f2b542abce79ac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2226924Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774389}

https://webrtc.googlesource.com/src.git/+log/a6c70741e76f..3c9ae1fd8fb7

2020-06-02 hta@webrtc.org Adds fix for closing a prenegotiated DC without sending data.

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/+doc/master/autoroll/README.md

Bug: None
Tbr: webrtc-chromium-sheriffs-robots@google.com
Change-Id: Ia3f824210022436e715304a5a149e2b9cc40b69a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2227158Reviewed-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@{#774388}

This reverts commit cd9df201.

Reason for revert: Failing on Mac, see bug

Original change's description:
> Main frame's context menu should exclude frame-specific commands.
> 
> If content::ContextMenuParams includes a non-empty |frame_url|, then the
> context menu (the menu shown after right clicking in a frame) includes
> frame-specific commands like "View frame source" and/or "Reload frame".
> Before r749036 / 82.0.4084.0, context menu shown for the main frame
> would exclude such frame-specific items.  This behavior has regressed
> in r749036, because it failed to preserve the following logic from
> //third_party/blink/renderer/core/page/context_menu_controller.cc:
> 
>   if (selected_frame != page_->MainFrame())
>     data.frame_url = WebURL(UrlFromFrame(selected_frame));
> 
> and instead started to unconditionally populate the |frame_url| field in
> RenderFrameHostImpl::OnContextMenu.  This CL fixes the regression.
> 
> Bug: 1085040
> Change-Id: I149447654bee858037a4230828e2c4a7b3c7c0bf
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2212995
> Reviewed-by: Istiaque Ahmed <lazyboy@chromium.org>
> Reviewed-by: Nasko Oskov <nasko@chromium.org>
> Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#774333}

TBR=nasko@chromium.org,lazyboy@chromium.org,lukasza@chromium.org,lazyboy@google.com

Change-Id: I39ca90cca707409aede5a46f27f300528b4d5d57
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 1085040, 1090564
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225246Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774387}

Newer library features are required for //clank code.

Size regression without resource filters:
 * 244,995 bytes, 941 methods
 * https://chromium-review.googlesource.com/c/chromium/src/+/2165449/8

Size regression with just Layouts, Calendar and AlertDialog removed
(AlertDialog is referenced by an unused layout):
 * +134,038 bytes, 344 methods
 * https://chromium-review.googlesource.com/c/chromium/src/+/2197526

"With this particular widget we rolled our own, then unrolled out own
since the savings own since the savings seemed to not quite outweigh
the cost on a subsequent update and we'd be rolling our own again."


Bug: 1064727
Change-Id: Idd02c3540a6e91e54d2fa5dc9a79bd851162bcfb
Binary-Size: Size increase from library. Reduced from 244,955.
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2165449Reviewed-by: Ted Choc <tedchoc@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Reviewed-by: Theresa  <twellington@chromium.org>
Reviewed-by: Danyao Wang <danyao@chromium.org>
Reviewed-by: Ryan Sleevi <rsleevi@chromium.org>
Commit-Queue: benjamin joyce <bjoyce@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774386}

https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/6380ab5a1d67..88bc40da7991

2020-06-02 anubmat@microsoft.com Add Serviceworker respondWith Timeline to network panel

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/+doc/master/autoroll/README.md

Bug: chromium:1066579
Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com
Change-Id: I6a7aba9f0ad97b130dad465cff51bbc906943ba7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2227271Reviewed-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@{#774385}

App browsers can now support tab strips and should be included in
some of the calls to IsBrowserTypeNormal.

Added function IsTabStripSupported and changed calls relating to
tablet mode in BrowserNonClientFrameViewAsh and
ImmersiveModeControllerAsh to use it rather than IsBrowserTypeNormal.

Bug: 1090208
Change-Id: I158e24debf44cd68b62725d96e8c287944af4dbf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2226236
Commit-Queue: Joel Hockey <joelhockey@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774384}

This moves it out of the site isolation error section. This appears to
be a bug in the spec for intersection-observer when dealing with a
child local root, and not a bug in the implementation of site isolation
or the test (since it's testing a bad spec).

R=szager@chromium.org

Bug: 1007229
Change-Id: I639cb6ddb1d1a82df837fb0ba466922d29151943
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2222910
Commit-Queue: danakj <danakj@chromium.org>
Reviewed-by: Stefan Zager <szager@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774383}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/e5cd744fe49e..76a2918f55cd

2020-06-02 vadimsh@chromium.org [lucicfg] Update to 1.14.5.

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

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

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

Bug: chromium:1082296,chromium:1085650
Tbr: agable@chromium.org
Change-Id: I325049adfcc60828bb7e7dd253b1f5a6db3a0418
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2227164Reviewed-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@{#774382}

Sometimes TrayItemView::SetVisible() can be called repeatedly.
An example is PowerTrayView() -- its SetVisible() can be called
periodically based on the power status. That causes animation
and AnimationProgressed(), but that is redundant.

Bug: 1082562
Test: manually
Change-Id: I45573360edda49572975966d1a84d4d067edbf13
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2223432Reviewed-by: Tim Song <tengs@chromium.org>
Commit-Queue: Jun Mukai <mukai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774381}

Tbr: sandromaggi@chromium.org
Bug: 1090215
Change-Id: I381c018c9a0b763dbb39a468754c78c895b8a9b5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2227181Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774380}

BUG=None
TEST=None

Change-Id: I1d562f0e930b27ab90d814b9ff97c033582e2070
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2226069Reviewed-by: Ian Barkley-Yeung <iby@chromium.org>
Commit-Queue: Miriam Zimmerman <mutexlox@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774379}

Bug: 1078169
Change-Id: I62bd049309a19ef41bb503fcaff8e1c7ed998847
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225533Reviewed-by: Wei-Yin Chen (陳威尹) <wychen@chromium.org>
Commit-Queue: Yue Zhang <yuezhanggg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774378}

Bug: 1089495
Change-Id: I8af3f627d076a03a58c61d183f63216ac31add79
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2226000Reviewed-by: Tsuyoshi Horo <horo@chromium.org>
Reviewed-by: Brian White <bcwhite@chromium.org>
Commit-Queue: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774377}

Under critical memory pressure the system is probably already swapping
out memory and making heavy use of IO. Adding to that is not desirable.
Furthermore, scheduling a task to write files to disk risks paging-in
memory that was already committed to disk which compounds the problem.

Bug: 1087530
Change-Id: I2f5ba6e703eef0d804e6f4d99dd504c7eadf7740
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2227029Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Reviewed-by: Sébastien Marchand <sebmarchand@chromium.org>
Commit-Queue: Oliver Li <olivierli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774376}

The targeter can be null and in that case it should use the parents.

Bug: b/157910224
Test: covered by unittest. also tested manually. see bug for repro step.
Change-Id: I13db092a6ee062ef9547aec70b6f7cd077558e2d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225854
Commit-Queue: Mitsuru Oshima <oshima@chromium.org>
Reviewed-by: Jesse Schettler <jschettler@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774375}

The file name doesn't match because the intended next CL is to rewrite
ScopedXPCUpdateServiceMock as ScopedXPCServiceMock that takes the
@protocol for the XPC service as an argument, and modify the existing
test to use it in this manner. I figured splitting it into two CLs
would simplify the review.

Bug: 1055876
Change-Id: I5134d8f29124538441fe1430ed3cacbdf56dd186
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225857
Auto-Submit: Adam Norberg <norberg@google.com>
Commit-Queue: Adam Norberg <norberg@google.com>
Reviewed-by: Sorin Jianu <sorin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774374}

Third-party search providers may or may not have third-party NTPs. When
they do not have a third-party NTP, the local-ntp is used to display
the most-visited tiles.

Bug: 1087531
Change-Id: I799e252edba04e07601fc43938688cf1d381d183
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225625Reviewed-by: Moe Ahmadi <mahmadi@chromium.org>
Commit-Queue: Moe Ahmadi <mahmadi@chromium.org>
Commit-Queue: Esmael Elmoslimany <aee@chromium.org>
Auto-Submit: Esmael Elmoslimany <aee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774373}

Roll Chrome Mac PGO profile from chrome-mac-master-1591113598-81d0db8118cc6885d9786065771de10da2a65ecd.profdata to chrome-mac-master-1591127928-6ca3eedb8c11f1c6551de9c000f330ab07bf1259.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-mac-chromium
Please CC jeffyoon@google.com,liaoyuke@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/+doc/master/autoroll/README.md

Cq-Include-Trybots: chrome/try:mac-chrome
Tbr: jeffyoon@google.com,liaoyuke@google.com
Change-Id: I248eeda08bdd7c40a45bd5a97c40ad833627de26
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2227167Reviewed-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@{#774372}

For the case when a menu is active, QuickAnswersView currently is unable
to obtain the focus because that would require activating its top-level
widget, which would cause the menu to disappear like it does on
observing any change in the activated window.

This CL makes QuickAnswerView's widget a child of the menu's owning
widget, as a result of which it can now share the owning widget's
FocusManager and successfully request focus.

This is needed to incorporate keyboard accessibility for the view. Key
or accelerator handling will be added in follow up CLs.

Tests are also added.

Bug: b:152057976
Test: Tested on Chrome OS VM and ran ash_unittests.
Change-Id: I2acbbd5d3f918fffe33d31d8f7764ecf28ffcaec
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2222119Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Abhijeet Singh <siabhijeet@google.com>
Cr-Commit-Position: refs/heads/master@{#774371}

Currently HeapProfilerController uses 24 hours interval for Desktop and
Android. While 24h is good for Desktop, the interval is too big for
Android, which likely has median process up time of less than an hour.

iOS uses 30 minutes interval, which is equal to median process up time
duration.  30m would be more appropriate interval for Android.

Bug: 1090017
Change-Id: Ia8dfc09a75e036265298e3d69ad04fb8cc1b1124
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225359
Commit-Queue: Erik Chen <erikchen@chromium.org>
Auto-Submit: Eugene But <eugenebut@chromium.org>
Reviewed-by: Erik Chen <erikchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774370}

This change
(1) adds dns_over_https to the tests' fake prefs.
(2) makes TestPrivacyPageBrowserProxy usable in its default state.
(3) adds a check for undefined prefs to secure_dns.js, to match the
other privacy preference UI elements.

Bug: 1087444
Change-Id: Ic8fb7e200d515d7a1da541c62ca3e90640e56060
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2223639Reviewed-by: Eric Orth <ericorth@chromium.org>
Reviewed-by: Esmael Elmoslimany <aee@chromium.org>
Commit-Queue: Ben Schwartz <bemasc@chromium.org>
Auto-Submit: Ben Schwartz <bemasc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774369}

I believe this was added when investigating some sort of change in
logic to close idle sockets, but it's no longer being used.

Fixed: 1089020
Change-Id: Iccb2670d9e65b717ceb3763367af3f87a4e2036d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225262Reviewed-by: Charlie Harrison <csharrison@chromium.org>
Reviewed-by: Eric Roman <eroman@chromium.org>
Commit-Queue: Eric Roman <eroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#774368}