GitLab

Some cros windows have a transform applied to them when they're closed.
When reopened they are placed where the transformed window was. The
widget bounds saving uses Window::GetBoundsInScreen which returns bounds
that are affected by the transform on the window. This CL alters that.

Test: added test
Bug: 1109161
Change-Id: Ia577b2372fa78be4cbf1ae4fbe2236fca615dd19
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2373660
Commit-Queue: Sammie Quon <sammiequon@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#819095}

https://skia.googlesource.com/skia.git/+log/c49da0b5192d..82f373c0d713

2020-10-20 johnstiles@google.com Wrap built-in symbol tables when an IRNode is cloned.
2020-10-20 johnstiles@google.com Fix typo in class name.
2020-10-20 robertphillips@google.com Make GrFillRectOp::onPrePrepareDraws also call base class' version
2020-10-20 adlai@google.com Reland "Remove GrContext"
2020-10-20 robertphillips@google.com Rename some of GrThreadSafeCache's member variables
2020-10-20 abarth@google.com [fuchsia] Migrate to new zx::vmar::map method

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 egdaniel@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
Cq-Do-Not-Cancel-Tryjobs: true
Bug: chromium:1108408
Tbr: egdaniel@google.com
Change-Id: I6d86a87ccb5421b03aa0f43cc3ba7b29b390ed51
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2487808Reviewed-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@{#819094}

Bug: 974061
Change-Id: Ifb85f9981d7d4c03481c1f78bd753d434fb5938a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2487692Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#819093}

Previously, grid items were placed according to document order in
PlaceGridItems() in the following change:
https://chromium-review.googlesource.com/c/chromium/src/+/2369673. Now
that the computed grid item positions are available from
https://chromium-review.googlesource.com/c/chromium/src/+/2404110, the
function was refactored to use the final specified/resolved positions
instead of document order.

Furthermore, out of flow items are now being filtered out and stored in
the vector out_of_flow_items_. The look up/calculation for the absolute
and static positioned offset remains a TODO for now.

Bug: 1045599
Change-Id: Ia3ad951983798d6b34f13ef80850736dd374aee8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2444451
Commit-Queue: Ana Sollano Kim <ansollan@microsoft.com>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Ethan Jimenez <ethavar@microsoft.com>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#819092}

This CL removes previous adjustments made to fix GMSCore API face
detection results. This is not needed anymore as GMSCore API has been
improved a lot and results are now similar to Android Face API. See
screenshots at https://crbug.com/1107675#c6

Change-Id: I19fa99fe73163a778a7fba41194d0ddf2021e74a
Bug: 1107675
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2478663Reviewed-by: Reilly Grant <reillyg@chromium.org>
Commit-Queue: François Beaufort <beaufort.francois@gmail.com>
Cr-Commit-Position: refs/heads/master@{#819091}

This was removed from the spec per resolution[1] and incompatible with
never media queries. Improves interop with Gecko which have not seen any
issues with the different serialization.

Removed fast/media test which is covered by existing wpt tests.

[1] https://github.com/w3c/csswg-drafts/issues/5627#issuecomment-712475204

Bug: 1138859
Change-Id: I1483008c81df90f8277dcad7e90c8036c5cc019b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2478992Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#819090}

We're launching this experiment, and we'll merge this flag change back
to M87.

Bug: 1068851
Change-Id: Ic35ff2f6632f075c902137911fc82733c8daec04
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2485353Reviewed-by: Jia Meng <jiameng@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Tony Yeoman <tby@chromium.org>
Cr-Commit-Position: refs/heads/master@{#819089}

This is part of a series of changes to improve crash reporting for
chrome://media-app (& incidentally other clients of crashReportPrivate).

Design doc: go/backlight-better-crash-report

We need chrome/ dependencies for
* determining chrome window type (regular, app, SWA).
* solid testing for opening & closing devtools
https://chromium-review.googlesource.com/c/chromium/src/+/2465407/comment/90edd371_2e37132d/
(that cl will be rebased on this)
And once this is ported, it also makes sense to
* grab app locale from the browser process
* grab renderer uptime with a chrome dep

This also ports crashReportPrivate tests from extensions_browsertests
to browser_tests.

Change-Id: I4bc51f0cb69927ffb07d8045a82b180ed308590b
Bug: b/169635499
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2438099
Auto-Submit: David Lei <dlei@google.com>
Reviewed-by: Ian Barkley-Yeung <iby@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Ben Wells <benwells@chromium.org>
Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org>
Reviewed-by: Trent Apted <tapted@chromium.org>
Commit-Queue: David Lei <dlei@google.com>
Cr-Commit-Position: refs/heads/master@{#819088}

Currently, an EventMetrics object is created for the event once just
before processing the event on the compositor thread, and once just
before processing the event on the main thread. With this change, the
EventMetrics object would be created as soon as the event arrives in the
renderer process and then passed around with the event on compositor and
main threads. There are a few benefits to this, including:
 - The metrics is created with the original timestamp of the event. The
   timestamp of the event might change further down the road, but we
   want to report metrics using the original timestamp.
 - We can add data about event dispatch stages along its path on the
   renderer which would help us report more event dispatch breakdown
   metrics.
 - The logic for determining whether a scroll update is the first one in
   a sequence or not can happen when the event arrives in the renderer
   once, instead of once for the compositor thread and once for the main
   thread.

Bug: 1079116
Change-Id: Ic46b16746d85d323cdb101c4abbfb874513c9439
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2416880
Commit-Queue: Mohsen Izadi <mohsen@chromium.org>
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Jonathan Ross <jonross@chromium.org>
Cr-Commit-Position: refs/heads/master@{#819087}

On the high visibility page, the help text was larger than spec,
and the info icon was getting shrunk down to 15px by flex.

Bug: b/163036847
Change-Id: I8cbc51622100bf5971131cdaae6c5ec1fbdb717a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2481042Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Commit-Queue: Curt Clemens <cclem@google.com>
Cr-Commit-Position: refs/heads/master@{#819086}

Bug: 772945
Change-Id: I4533a53a4a7392c7df43bb6f692ed6fd64a8b065
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2487695
Commit-Queue: Peter Kasting <pkasting@chromium.org>
Commit-Queue: Peter Boström <pbos@chromium.org>
Auto-Submit: Peter Kasting <pkasting@chromium.org>
Reviewed-by: Peter Boström <pbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#819085}

Bug: 1108016
Change-Id: Ia739b0a0f8c7607155ac40dcb6d1c9493265039a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2488386Reviewed-by: Garrett Beaty <gbeaty@chromium.org>
Commit-Queue: Chan Li <chanli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#819084}

Previously the menu button background was set to null when removing the
IPH pulse highlighting. Instead, set back to the original background.

BUG=1134646

Change-Id: Ie4639be34175cf737154b877cb44e29acc74ef5c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2487680Reviewed-by: Patrick Noland <pnoland@chromium.org>
Commit-Queue: Theresa  <twellington@chromium.org>
Auto-Submit: Theresa  <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#819083}

To be consistent with other password manager account storage metrics.

Bug: 1140079
Change-Id: I3eed095d8f92b237d2007feeb80860f0b9086ccc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2487285
Auto-Submit: Mohamed Amir Yosef <mamir@chromium.org>
Commit-Queue: Brian White <bcwhite@chromium.org>
Reviewed-by: Brian White <bcwhite@chromium.org>
Cr-Commit-Position: refs/heads/master@{#819082}

This reverts commit 87336cbd.

Reason for revert: CL used for merge-only, not needed on Master.

Original change's description:
> Disable a set of DumpAccessibilityTree tests
>
> Disables a set of tests that are failing on M87 on Android.
>
> We plan to land on Master, merge into M87, revert on Master (since it
> has been addressed on Master).
>
> BUG=1137967
>
> Change-Id: I6f38149b21df33d1354394322b7bad9ff492dad9
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2481629
> Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org>
> Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#818691}

TBR=dmazzoni@chromium.org,donnd@chromium.org,mschillaci@google.com

Change-Id: Ic68d8d8981c4e332ad331d1e554bc28c9efe8156
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 1137967
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2488341Reviewed-by: Donn Denman <donnd@chromium.org>
Commit-Queue: Donn Denman <donnd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#819081}

https://chromium.googlesource.com/openscreen.git/+log/b92a3f35eee8..a8cdc94e138d

2020-10-20 jophba@chromium.org [Cast Streaming] Remove deprecated ConfiguredReceiver fields

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/openscreen-chromium
Please CC jophba@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:1132109
Tbr: jophba@chromium.org
Change-Id: I3e064f1d336f26f7b108038333bf9010177742d6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2487805Reviewed-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@{#819080}

Actually updates to 1.0.9 as it is win 7 compatible

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

Change-Id: I3090a3df3ad132089fcde0de58f1b59b75fa8d3e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2485100
Commit-Queue: Lachlan Ford <laford@microsoft.com>
Reviewed-by: Alexander Cooper <alcooper@chromium.org>
Cr-Commit-Position: refs/heads/master@{#819079}

Roll Chrome Linux PGO profile from chrome-linux-master-1603195140-c129f14cb6d511df5580572a9de378cf815e87d7.profdata to chrome-linux-master-1603216608-9fdc3766d62145cb23e4981f379b4b4bd1eab8ae.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-linux-chromium
Please CC pgo-profile-sheriffs@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-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I6d8944efc47e627b99d45640717aa1d3aad26c85
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2487950Reviewed-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@{#819078}

Updates the expires_after attribute for 152 histograms that show
frequent access in the past 90 days.  These are the 94% most
frequently used histograms over that time that do not already
have a date later than or within 60 days of 2021-01-18.

TBR=chromium-metrics-reviews@google.com

Change-Id: I59bf7c95315cb6f8b39f1c63a72561ec06f07b59
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2488223Reviewed-by: Chrome Metrics Logs <chrome-metrics-team+robot@google.com>
Commit-Queue: Chrome Metrics Logs <chrome-metrics-team+robot@google.com>
Cr-Commit-Position: refs/heads/master@{#819077}

Roll Chrome Mac PGO profile from chrome-mac-master-1603195140-e7f1aee2c0a50a929699520496ae0e25b15e94bf.profdata to chrome-mac-master-1603216608-7529e831dfcfdc3eeb93d3e8d9f23aaded5766b2.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 pgo-profile-sheriffs@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:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I8661e5f7c72581521134d81c0f628afed44f136a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2487809Reviewed-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@{#819076}

This is part of a migration that replaces the old
<histogram-suffixes> syntax that was used to denote groups
of histogram to the new patterned histogram syntax.

Bug: 758782
Change-Id: Ieb7136dc5d8e59438d9d7fd28f5fa05c81beaa23
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2481464
Commit-Queue: Karthika Pai <karthikapai@google.com>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Weilun Shi <sweilun@chromium.org>
Cr-Commit-Position: refs/heads/master@{#819075}

It wasn't clear whether the supplied parameter is a delta or absolute
value. Hopefully this clears that up.

BUG=none
TEST=none

Change-Id: Ic0921d209c1c11f125cdc6b8821d9bf265c8cd77
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2487683Reviewed-by: Bo <boliu@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#819074}

Change-Id: I0ea9cfaf68ec3dc68cc0fff456add47f1e6ab4ee
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2488382
Commit-Queue: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Peter Wen <wnwen@chromium.org>
Auto-Submit: Andrew Grieve <agrieve@chromium.org>
Reviewed-by: Peter Wen <wnwen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#819073}

Bug: 1105862
Change-Id: I84b07861bf1cc6485a07546347154e6cb9262c53
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2443214Reviewed-by: Brian White <bcwhite@chromium.org>
Commit-Queue: John Lee <johntlee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#819072}

This will block usage of the CDM factory daemon on Chrome OS when in
incognito or guest mode. This is required since a unique identifier is
used in that implementation.

BUG=b:153111783
TEST=Verified daemon is not used in incognito/guest mode

Change-Id: Iba59659fe0e331f2f5f5e3bdfce4ff65895e4386
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2485144
Commit-Queue: Jeffrey Kardatzke <jkardatzke@google.com>
Reviewed-by: Xiaohan Wang <xhwang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#819071}

This config is very unlikely to ship and causes extra load on the
team to maintain. Remove it for now.

Bug: angleproject:5196
Change-Id: I48c6475eacfdb19af2dd664d228261225a13b784
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2485308Reviewed-by: Brian Sheedy <bsheedy@chromium.org>
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Cr-Commit-Position: refs/heads/master@{#819070}

The SGIVideoSyncThread instance may be recreated on context loss.  In
this case, we need to detach the connection from the thread's sequence
so that subsequent threads can reuse it.

R=sunnyps

Bug: 1139015
Change-Id: I9a151597582dcbb22cba87781e94c76a46346f26
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2486286
Auto-Submit: Thomas Anderson <thomasanderson@chromium.org>
Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org>
Reviewed-by: Sunny Sachanandani <sunnyps@chromium.org>
Cr-Commit-Position: refs/heads/master@{#819069}

TBR=bling-team@google.com

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

Fixed: 1139523
Test: browser_tests --gtest_Filter=DiagnosticsApp*
Change-Id: I346a8e58d96cc10691ba1aea3eef6789844d5a56
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2485696Reviewed-by: Zentaro Kavanagh <zentaro@chromium.org>
Commit-Queue: Joon Ahn <joonbug@chromium.org>
Cr-Commit-Position: refs/heads/master@{#819067}

This CL plumbs creation time and reading list read status to Java.

Also add an API in reading_list_manager.h to query the read status.

Bug: 1139133
Change-Id: Ia6bad05c16136b453fc8db198448c5a38be24132
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2485342
Commit-Queue: Xing Liu <xingliu@chromium.org>
Reviewed-by: Brandon Wylie <wylieb@chromium.org>
Reviewed-by: Theresa  <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#819066}

Move the sink ID to its own argument in the logger call so that it gets
truncated properly.

Bug: 1117673, b/170651374
Change-Id: I72d040078104d5f4ce15f15c26f34f542b3f5ca9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2469438Reviewed-by: John Williams <jrw@chromium.org>
Commit-Queue: Takumi Fujimoto <takumif@chromium.org>
Cr-Commit-Position: refs/heads/master@{#819065}

Calls to FirstRunFragment#setInitialA11yFocus can be triggered when
view is not initialized yet for the fragment and cause NPE with current
implementations. This CL simply ignores the calls if it is made too
early.

More context on why #setInitialA11yFocus is introduced and why this
fix might be sufficient can be found in the crbug.com/1140174#c2.


Bug: 1140174
Change-Id: Ie7771e73a46bd30d1c0e0fa3e2e56c0e886c4d54
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2487580
Commit-Queue: Wenyu Fu <wenyufu@chromium.org>
Reviewed-by: Theresa  <twellington@chromium.org>
Reviewed-by: Sky Malice <skym@chromium.org>
Cr-Commit-Position: refs/heads/master@{#819064}

This test is flaky under tsan.

Tbr: bcwhite@chromium.org
Bug: 1061320
Change-Id: I2a0e47659ca84aadb8a4e139406f7e77ec4a0349
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2487844Reviewed-by: Kevin McNee <mcnee@chromium.org>
Commit-Queue: Kevin McNee <mcnee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#819063}

The DestroyProfileOnBrowserClose experiment
(see go/destroy-profile-on-browser-close) changes profile teardown,
and introduced a new crash. ExtensionRequestObservers should be
destroyed before the Profile is destroyed, not during BrowserProcess
teardown.

Listen to OnProfileWillBeDestroyed() events for _all_ profiles, because
they can get destroyed at any time. Previously, we only did this for
some profiles.

Bug: 88586, 1140492
Change-Id: I8657119ae36c763b6e2e515185f1d2f15586376c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2485176
Commit-Queue: Nicolas Ouellet-Payeur <nicolaso@chromium.org>
Reviewed-by: Owen Min <zmin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#819062}

Does not address subfolders which will be done in separate chunks.

Bug: 1128500
Change-Id: Id3caa97d0d59b4700b888c5bca5f89f69d4c64d1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2485148
Commit-Queue: Peter Boström <pbos@chromium.org>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Auto-Submit: Peter Boström <pbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#819061}

Includes 3 Stability.Internals.* and Suggestions.LocalBlacklistSize.

Bug: 975530, 975251
Change-Id: I1fe13c53993d855c48b0869e2f47ad5037311dd3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2487841
Commit-Queue: Sigurður Ásgeirsson <siggi@chromium.org>
Commit-Queue: Robert Kaplow <rkaplow@chromium.org>
Auto-Submit: Sigurður Ásgeirsson <siggi@chromium.org>
Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Cr-Commit-Position: refs/heads/master@{#819060}

This CL modifies the trace events added in
http://crrev.com/c/2229611 to used typed arguments.

It also fixes a typo in an event name (OnDwmCompositionChanged ->
OnDpiChanged).

Change-Id: I04e5c125f1d68be1be2a19414cd363992b7a7b1a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2472501
Commit-Queue: Salvador Guerrero <salg@google.com>
Reviewed-by: oysteine <oysteine@chromium.org>
Reviewed-by: Eric Seckler <eseckler@chromium.org>
Reviewed-by: Robert Liao <robliao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#819059}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/615063999dd2..4deb1ed9573d

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 reillyg@google.com,mcnee@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:1117663,chromium:1140474
Tbr: reillyg@google.com,mcnee@google.com
Change-Id: Ife957fccb764fb7c184730f6ef686c1e58c6c50c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2487760Reviewed-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@{#819058}

The filter file had these tests parameterized, when the tests themselves
are not.

Bug: 1137434
Change-Id: Ia344915cb70535f8ad6b429c51622d0f264dc85f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2488122
Commit-Queue: Kevin McNee <mcnee@chromium.org>
Commit-Queue: Eric Willigers <ericwilligers@chromium.org>
Auto-Submit: Kevin McNee <mcnee@chromium.org>
Reviewed-by: Eric Willigers <ericwilligers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#819057}

Add NIK to the on-disk reporting and NEL information.

Bug: 993805
Change-Id: I27b1242458e48423b7615effcee3de5afda916e9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2485253Reviewed-by: Lily Chen <chlily@chromium.org>
Commit-Queue: Matt Menke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#819056}