GitLab

Bubbles are anchored to the app menu button by default. In immersive not
revealed mode, the app menu button is drawn somewhere offscreen. To
avoid the bubble being placed partially offscreen, return a null anchor
view. This will cause the bubble to be drawn in the top left corner,
just like regular fullscreen.

Test: browser_tests ImmersiveModeControllerAshWebAppBrowserTest.PermissionsBubbleAnchor
Change-Id: I1aeaea0da64d3a301a898ae5e7778d123eb2e433
Fixed: 1087143
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2311896Reviewed-by: Peter Boström <pbos@chromium.org>
Reviewed-by: Wei Li <weili@chromium.org>
Commit-Queue: Sammie Quon <sammiequon@chromium.org>
Cr-Commit-Position: refs/heads/master@{#792013}

https://skia.googlesource.com/skia.git/+log/e94b4e1b49a3..66d19211aa8f

2020-07-27 jmbetancourt@google.com remove skar_java from skia android projects

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 borenet@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: 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: borenet@google.com
Change-Id: I8c17082f3f57fc88a4d5260a14a100a628cbdbf2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2318734Reviewed-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@{#792012}

https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/0bf389ba6cb5..478f7fed94ec

2020-07-27 zhin@chromium.org Import changes to wast mode in CodeMirror
2020-07-27 jacktfranklin@chromium.org Component bridges: support overriding fields
2020-07-27 aerotwist@chromium.org Migrate console_counters to devtools_entrypoint
2020-07-27 sigurds@chromium.org [bandaid] Let issue banner scroll out of view in console
2020-07-27 janscheffler@chromium.org Migrate `front_end/javascript_metadata` to `devtools_entrypoint`
2020-07-27 janscheffler@chromium.org Migrate `front_end/heap_snapshot_model` to `devtools_entrypoint`
2020-07-27 jacktfranklin@chromium.org Component bridges: support types that extend types
2020-07-27 aerotwist@chromium.org Migrate text_utils to devtools_entrypoint

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:1094596,chromium:1096481,chromium:1101738
Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com
Change-Id: I2148a05d6b2835067ef6dbff7a0e470ca479a71c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2318736Reviewed-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@{#792011}

Currently this will just focus on getting product names referenced the
same way in all policies.

Change-Id: I53a2442c79f18f79c5c31d89c01e10c74a1e8e87
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2303528
Commit-Queue: Chris Sharp <csharp@chromium.org>
Reviewed-by: Owen Min <zmin@chromium.org>
Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#792010}

This change adds MANIFEST_URL_CHANGED to InstallableStatusCodes, and
adds support for InstallableManager reporting this error (as well as
reporting when a navigation happens or when the renderer exists).

Then it modifies the AppBannerManager class to listen for this result
when it fetches the manifest or checks if a tab is installable.

Finally, it modifies AppBannerManager to also listen for manifest url
changes, and when the occur outside of calls to the InstallableManager
(as these will be reported by the method above), it resets its state
and restarts the request.

Possible upgrades:
 * Add the rate limiter in AppBannerManager for retrying (or just count
   the number of retries & stop after X times)

Design doc:
https://docs.google.com/document/d/1HjN4JL9DCaTNuLj29ieqJEsexpfAzfJnoVrqY7SWvd8/edit

R=dominickn@chromium.org

Bug: 792299
Change-Id: Ia26c727d68d50ebee1966ed0e0318874e1843fe7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2300828
Commit-Queue: Daniel Murphy <dmurph@chromium.org>
Auto-Submit: Daniel Murphy <dmurph@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Cr-Commit-Position: refs/heads/master@{#792009}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/f81afad16767..2ddb3ecf006e

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 mahmadi@google.com,adithyas@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: luci.chrome.try:linux-chromeos-chrome
Bug: chromium:1085419,chromium:635745,chromium:912681
Tbr: mahmadi@google.com,adithyas@google.com
Change-Id: I1de6964735d1b35c81966c4f7e96a78e4910ba10
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2320202Reviewed-by: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Reviewed-by: Moe Ahmadi <mahmadi@chromium.org>
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#792008}

This moves all the favicon related functionality out of
HistoryBackend into FaviconBackend. FaviconBackend is owned
by HistoryBackend. FaviconBackend indirectly talks to
HistoryBackend by way FaviconBackendDelegate.

BUG=1076463
TEST=covered by tests

Change-Id: If9927019b4539174d36daaf02597fcf1f1ad5c35
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2314990Reviewed-by: Peter Kotwicz <pkotwicz@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#792007}

https://swiftshader.googlesource.com/SwiftShader.git/+log/3b2cd31c7400..a681d12639f4

2020-07-27 caramelli.devel@gmail.com Add Wayland support for Vulkan WSI

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

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

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

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_chromium_msan_rel_ng;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86
Bug: None
Tbr: swiftshader-team+autoroll@google.com
Change-Id: I69dbd30ca9f70279eaa518975edc8471338b7e14
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2318735Reviewed-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@{#792006}

Bug: 1108786
Change-Id: Ie498760184517698d3ef0346f996fa09a7c44960
No-Try: True
Tbr: mahmadi@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2321305Reviewed-by: Adithya Srinivasan <adithyas@chromium.org>
Commit-Queue: Adithya Srinivasan <adithyas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#792005}

This implements the changes from https://github.com/WICG/native-file-system/pull/200.

Change-Id: I9702f9888c4f0fff2084143ac6077b8484dfce16
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2298296Reviewed-by: Trent Apted <tapted@chromium.org>
Reviewed-by: Will Harris <wfh@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Commit-Queue: Marijn Kruisselbrink <mek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#792004}

This CL merges the function PseudoStyleForElementInternal with its
non-internal wrapper PseudoStyleForElement.

This is a step towards unifying the two very similar codepaths of
StyleForElement and PseudoStyleForElement.

There should be no behavior change.

Change-Id: Iad0dfd59c8081de5ec68bbc5120e4cf28eee7954
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2317960
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Reviewed-by: Oriol Brufau <obrufau@igalia.com>
Cr-Commit-Position: refs/heads/master@{#792003}

This was originally postponed to make the branch deadline.

Bug: 968640
Change-Id: I5066bd1f161e25428f872819bfc92bb16f4c7c35
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1668070
Commit-Queue: Erik Jensen <rkjnsn@chromium.org>
Reviewed-by: Yuwei Huang <yuweih@chromium.org>
Reviewed-by: Joe Downing <joedow@chromium.org>
Cr-Commit-Position: refs/heads/master@{#792002}

Changes:
- added one more recording including a tracking loss
- added 3 test cases exercising anchors API
- slightly tweaked XrTestFramework to allow for specifying timeouts
explicitly so that the longest anchor test does not time out

Bug: 992035
Change-Id: Ied3db9b459c72cbc1826d8a9e2e7edec90cbaae4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2314663
Commit-Queue: Piotr Bialecki <bialpio@chromium.org>
Reviewed-by: Brian Sheedy <bsheedy@chromium.org>
Reviewed-by: Klaus Weidner <klausw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#792001}

This patch adds two new @font-face descriptors to override the default
font metrics. Though we don't have a stable spec at the moment, we land
it behind a flag to make testing and discussion easier.

Design doc: https://bit.ly/39qATQ4

Bug: 1098355
Change-Id: I2623a9385fe6e9fbfccf2e04cb5892f4aba37872
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2316780Reviewed-by: Koji Ishii <kojii@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#792000}

This change uses native_theme_base.cc to update the styling for the checkbox native controls in dark mode.

Bug: 1099579
Change-Id: Iafb167aa2f24c304ac2292178beb4d6bdb24a451
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2311697Reviewed-by: Mason Freed <masonfreed@chromium.org>
Reviewed-by: Yu Han <yuzhehan@chromium.org>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Commit-Queue: Sam Sebree <sasebree@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#791999}

When the apps grid enters cardified state, all icons are scaled down
84%. We need to scale down the folder circle proportionally, to avoid
clipping at the top edges.

Bug: 1108644
Change-Id: I95b97d6d3db15c0313a92bbffbd5f70ffb4e071e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2315094Reviewed-by: Toni Baržić <tbarzic@chromium.org>
Commit-Queue: Ana Salazar <anasalazar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791998}

Browser tests for the ML service is added to the Optimization Guide
path where the service will be used first.

Bug: 1108334
Change-Id: I5ec1845f9043546e89b49776e95ccdc391ea1e90
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2320748Reviewed-by: Lei Zhang <thestig@chromium.org>
Reviewed-by: Sophie Chang <sophiechang@chromium.org>
Reviewed-by: Michael Crouse <mcrouse@chromium.org>
Commit-Queue: Jia Li <jiakl@google.com>
Cr-Commit-Position: refs/heads/master@{#791997}

A new script has been added to count and optionally output cycles in
package graphs. A limit to cycle size must be supplied, ideally around 5
or 6 to keep the script runtime low since the number of cycles is
exponential.

For more detailed usage, see `./count_cycles.py -h`.

Bug: 1106484
Change-Id: I01923eaab24eb3c6641a23039c80f60a0bc0e212
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2303054
Commit-Queue: James Long <yjlong@google.com>
Reviewed-by: Samuel Huang <huangs@chromium.org>
Reviewed-by: Mohamed Heikal <mheikal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791996}

This is cleaning up uses of base::Unretained(this) in the cros_healthd
service connection. There are cases where the service connection could
be destroyed before the callback returns.

Bug: chromium:1108065
Change-Id: I66639581e213cc088080de5ec407f06968b8559c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2311074
Commit-Queue: Trent Begin <tbegin@chromium.org>
Reviewed-by: Paul Moy <pmoy@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791995}

Bug: 1000989
Change-Id: I7ae5d8279cb46866e28a4393d8cdc0d3ae21bcd0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2315901Reviewed-by: dpapad <dpapad@chromium.org>
Commit-Queue: My Nguyen <myy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791994}

Removes unnecessary defines, chooses correct path based on
OzonePlatform feature usage.

-----

PS: Please note that this is a temp solution that will help to choose
between ozone and non-ozone X11 build. The switch that will be used
to choose the path is --enable-features=UseOzonePlatform. Once
non-Ozone X11 path is removed (hopefully by Q1 2021 depending on how
th finch trial goes), the wrapper will be removed.

Please also note that it's impossible to build use_x11 && use_ozone
without some hacks in PlatformCursor code. The changes to that are
on their way to upstream.

----

Bug: 1085700
Change-Id: I5fced0993b55d0dedd9661d9845ff3b347b7bf4e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2315885Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Maksim Sisov (GMT+3) <msisov@igalia.com>
Cr-Commit-Position: refs/heads/master@{#791993}

Select file dialogs are implemented in ash-chrome via
SelectFileDialogExtension, which requires an aura::Window owning window
for the dialog.

Top-level windows in lacros-chrome are represented in ash-chrome via
ShellSurface objects. Pass an ID for the shell surface over mojo from
lacros-chrome to ash-chrome and use it for window parenting.

The ID is a string: "org.chromium.lacros.<unguessable-token>", e.g.
"org.chromium.lacros.8B93BD96131616984961C7790B5E9A62". Lacros creates
an ID for each WaylandToplevelWindow and uses xdg_shell's set_app_id
method to set it. This is similar to how ARC++ encodes an Android
task ID in the app ID, e.g. "org.chromium.arc.12345".

The ID is sent as a string to provide future flexibility (in case we
need to encode different window types, like "lacros_popup") and because
it felt like an appropriate return type for the cross-platform method
ui::PlatformWindow::GetInternalWindowId().

Feature design doc at go/lacros-select-file

Bug: 1090587
Test: multiple simultaneous file open dialogs spawn/stack/close correctly
Change-Id: I7b2cdb934480f72f5dbb3523922d30cf5df0376a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2301119
Commit-Queue: James Cook <jamescook@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Reviewed-by: Luciano Pacheco <lucmult@chromium.org>
Reviewed-by: Erik Chen <erikchen@chromium.org>
Reviewed-by: Jorge Lucangeli Obes <jorgelo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791992}

For privacy concerns there is a push to add feature policy and Secure
Context requirements to gamepads. We are adding these behind a flag now
so that we can more easily coordinate the rollout with other browsers.

Bug: 1099544
Change-Id: Ic64ae35d74692eaf29f618f8fdbb49cf7a143751
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2269718
Commit-Queue: James Hollyer <jameshollyer@chromium.org>
Reviewed-by: Oliver Chang <ochang@chromium.org>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Reviewed-by: Matt Reynolds <mattreynolds@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791991}

Bug: 1109750
Change-Id: I2c2f95f427d41dfd98ec230dd4a89f0997635d3c
Tbr: apaseltiner@chromium.org, johnidel@chromium.org
No-Try: True
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2321399Reviewed-by: Adithya Srinivasan <adithyas@chromium.org>
Commit-Queue: Adithya Srinivasan <adithyas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791990}

The implementation to use layer transforms to resize the bubble
is no longer used due to recent optimizations. Removing this code
and the extra view containers that were required for it.

Bug: 1024530
Change-Id: I71e5cecbc51011b16c0b7d0da09464ea4562eacd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2318693
Commit-Queue: Ahmed Mehfooz <amehfooz@chromium.org>
Reviewed-by: Tim Song <tengs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791989}

Bug: b:159021439
Change-Id: Ie1cd845dc910af48d241e5193a2d39ff7e1bd106
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2294940
Auto-Submit: Anand K Mistry <amistry@chromium.org>
Reviewed-by: Brian White <bcwhite@chromium.org>
Reviewed-by: Ken Rockot <rockot@google.com>
Commit-Queue: Brian White <bcwhite@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791988}

The fuchsia.media.drm.ContentDecryptionModule sends an event upon the
completion of provisioning[1]. This is an indication that the CDM is
ready for use. This CL pends the CDM creation callback until after the
OnProvisioned event has been received, ensuring the CDM is ready prior
to any calls being made to it.

[1] https://fuchsia.dev/reference/fidl/fuchsia.media.drm#fuchsia.media.drm/ContentDecryptionModule.OnProvisioned

Bug: fuchsia: 13619
Change-Id: Ie119daa58610b2cab0cade14b7dbf1ef93b3dcfc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2315000
Commit-Queue: RJ Ascani <rjascani@google.com>
Reviewed-by: Sergey Ulanov <sergeyu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791987}

These tests were moved to a different directory in upstream WPT.
Deleting them under their old names will allow wpt-import to run and
avoid lint errors about these tests not existing under their new name.
Once import runs (and renames the tests on the chromium side), they will
be re-added to the expectations files under their new path.

TBR=rmhasan

Bug: 1110003
Change-Id: I50fedbd09a0d493d47b2765ee6d871d4395e25bc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2321049Reviewed-by: Luke Z <lpz@chromium.org>
Reviewed-by: Rakib Hasan <rmhasan@google.com>
Commit-Queue: Rakib Hasan <rmhasan@google.com>
Cr-Commit-Position: refs/heads/master@{#791986}

Bug: 1105004,1105005,1105006,1105010
Change-Id: Ida229c9aa88a86891b1b5c0985bc50ae693a4ef6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2307329
Auto-Submit: Ilya Nikolaevskiy <ilnik@chromium.org>
Commit-Queue: Brian White <bcwhite@chromium.org>
Reviewed-by: Brian White <bcwhite@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791985}

BUG=1088586

Change-Id: I9e7f546407e4a8216209201715a8c1a047512199
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2320066Reviewed-by: Brian White <bcwhite@chromium.org>
Commit-Queue: Brian White <bcwhite@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791984}

This CL re-enables flaky tests, the underlying issue should have been
fixed by https://crrev.com/c/2280467

Bug: 246308, 1099384
Change-Id: I76aed73aea7143b73c93aaefb2d7d1060ada4bc3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2283396
Commit-Queue: Vasiliy Telezhnikov <vasilyt@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791983}

Change-Id: I4efd4d948cf58f697714b71233cc3122c9566c78
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2319340
Auto-Submit: Garrett Beaty <gbeaty@chromium.org>
Reviewed-by: Stephen Martinis <martiniss@chromium.org>
Reviewed-by: Rakib Hasan <rmhasan@google.com>
Commit-Queue: Stephen Martinis <martiniss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791982}

We're now flashing the devices as part of the LKGM CL tryjobs, so we
no longer have to confine ourselves to the compile-only bot.

Bug: 1057152
Change-Id: Iab4118f97cd65c5def6c1a0e73263c7621237811
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2316292Reviewed-by: Garrett Beaty <gbeaty@chromium.org>
Commit-Queue: Ben Pastene <bpastene@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791981}

This is part of a larger effort to force users to provide
GrDirectContext when manipulating texture-backed images.

Bug: skia:104662
Change-Id: Ic21ba05d0f13d9e597bb3eac49ac818209b1c1c9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2313301
Commit-Queue: Adlai Holler <adlai@google.com>
Auto-Submit: Adlai Holler <adlai@google.com>
Reviewed-by: Robert Phillips <robertphillips@google.com>
Cr-Commit-Position: refs/heads/master@{#791980}

Change-Id: Ia91ea60c9dc239cac598153f422911ac84ca7cab
Bug: b/157458681
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2320070
Auto-Submit: Nick Harper <nharper@chromium.org>
Commit-Queue: David Schinazi <dschinazi@chromium.org>
Reviewed-by: David Schinazi <dschinazi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791979}

kUserInteraction task source will align the pointer lock events with the
mouse events. It will also help spec consistency.

Bug: 1109007
Change-Id: I6426874161fc772a27640831617e70f941737b2e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2316808Reviewed-by: James Hollyer <jameshollyer@chromium.org>
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Commit-Queue: James Hollyer <jameshollyer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791978}

Re-enables the Telemetry minidump tests on most platforms. They were
disabled due to flakiness, but further investigation shows that the
flake rate was relatively low, and some flakes were caused by unrelated
issues, e.g. platform-wide issues.

Bug: 1084931
Change-Id: I31fab19af04faea49826dc827a45817da3de9397
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2318505
Auto-Submit: Brian Sheedy <bsheedy@chromium.org>
Reviewed-by: Achuith Bhandarkar <achuith@chromium.org>
Commit-Queue: Brian Sheedy <bsheedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791977}

Expands the FontMatchingMetrics object to record (successful or
unsuccessful) local font lookup events in a range of situations, as
enumerated in FontLookupType. The font lookup inputs (e.g. font name)
and a hash of the resulting font data are periodically published.
This will allow for measurement of the privacy impact of local font use.

This cl does not record any font lookup events associated with a binary
or remote CSSFontFaceSource. Metrics reporting in the
OffscreenFontSelector will occur in a separate cl (crrev.com/c/2197604).

Bug: 973801
Change-Id: I8304568af91fc56c1efe4087a9a7effdad234474
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2195493
Commit-Queue: Alex Turner <alexmt@chromium.org>
Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org>
Reviewed-by: Dominik Röttsches <drott@chromium.org>
Reviewed-by: Eric Willigers <ericwilligers@chromium.org>
Reviewed-by: Asanka Herath <asanka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#791976}

chops recently updated the depot_tools input_api, which makes this
possible.

input_api.DEFAULT_ALLOW_LIST -> input_api.DEFAULT_FILES_TO_CHECK
input_api.DEFAULT_BLACK_LIST -> input_api.DEFAULT_FILES_TO_SKIP

For named parameters:
white_list/whitelist -> files_to_check
black_list/blacklist -> files_to_skip

Bug: 1098562
Change-Id: Icc576b50727256d94ad62b985b2c81991a9af49e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2317743
Auto-Submit: James Cook <jamescook@chromium.org>
Commit-Queue: Ken Rockot <rockot@google.com>
Reviewed-by: Ken Rockot <rockot@google.com>
Cr-Commit-Position: refs/heads/master@{#791975}

* Suppress a lint warning that is expected.
* For methods whose visibility is relaxed not only for the reason of
  testing, remove the @VisibleForTesting annotation.

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