GitLab

Fix build error with libstdc++:
In file included from ../../ui/gfx/x/xlib_support.cc:5:
../../ui/gfx/x/xlib_support.h:41:8: error: ‘unique_ptr’ in namespace ‘std’ does not name a template type
   41 |   std::unique_ptr<XlibLoader> xlib_loader_;
      |        ^~~~~~~~~~

Bug: 957519
Change-Id: Ibd752625f76d24749d8958c5e4d9082ecf24630a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2534874Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
Commit-Queue: José Dapena Paz <jdapena@igalia.com>
Cr-Commit-Position: refs/heads/master@{#828155}

Roll Chrome Win64 PGO profile from chrome-win64-master-1605560272-77c0d8d0117a28bac6ffdb0ad2fa6b677cbad6f9.profdata to chrome-win64-master-1605581968-699188875fbc74b98026cce85d5b16d698948c9f.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-win64-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:win64-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I38e72fe2ecbe3bd7c93cf996c644078af18dbed3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2543829
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#828154}

This change adds the protos required for the mini
actions.

These mini actions will be added to |action_info| of
the |ActionProto| in a later patch.

Bug: b/172542134
Change-Id: I5f7d5112e5e2e0be0d776b9e431fa1bf04c6983d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2519455Reviewed-by: Clemens Arbesser <arbesser@google.com>
Reviewed-by: Stephane Zermatten <szermatt@chromium.org>
Commit-Queue: Sandro Maggi <sandromaggi@google.com>
Cr-Commit-Position: refs/heads/master@{#828153}

https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/67c1571570a0..1d0105053a41

2020-11-17 alexrudenko@chromium.org Use APCA for text contrast in Color Picker
2020-11-17 szuend@chromium.org [issues] Throw an error for unused replacements
2020-11-17 kimanh@chromium.org [e2e] Disable flaky wasm performance test
2020-11-17 the.derekli@gmail.com Improve _searchHighlighting performance
2020-11-17 szuend@chromium.org [ts] Replace DOMExtensions with platform features in UIUtils.js
2020-11-17 szuend@chromium.org TypeScript-ify ui/ViewManager.js
2020-11-17 petermarshall@chromium.org [typescript] TypeScript-ify profiler/ChildrenProvider.js
2020-11-17 szuend@chromium.org TypeScript-ify ui/Toolbar.js
2020-11-17 szuend@chromium.org [ts] Fix event types in ui/UIUtils.js
2020-11-17 kimanh@chromium.org Show linear memory inspector as drawer
2020-11-17 szuend@chromium.org [cleanup] Replace symbols with WeakMaps in ui/ViewManager.js
2020-11-17 aerotwist@chromium.org TypeScriptify measured-scrollbar-width.js
2020-11-17 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update DevTools Chromium DEPS.

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:1011811,chromium:1110202,chromium:1121900,chromium:1125465,chromium:1149827
Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com
Change-Id: I0920410053d5eb7c60fa41291bf02c11c22edad5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2544105Reviewed-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@{#828152}

This CL removes the unused dependency of KeyPermissionsService on the
underlying profile policies.

Bug: 1137344
Change-Id: I700356ce7b39cc58e1c4aec08ce14abafec166cd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2541862
Commit-Queue: Omar Morsi <omorsi@google.com>
Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Cr-Commit-Position: refs/heads/master@{#828151}

This comment should have been updated here
https://chromium-review.googlesource.com/c/chromium/src/+/2476637/9/chrome/browser/ui/webui/settings/people_handler.cc#b558

TBR=rushans@google.com

Bug: None
Change-Id: I8d83c0ba64a0af9ad61bb4795d1ac8efc349b84c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2541783
Commit-Queue: Victor Vianna <victorvianna@google.com>
Reviewed-by: Rushan Suleymanov <rushans@google.com>
Reviewed-by: Victor Vianna <victorvianna@google.com>
Cr-Commit-Position: refs/heads/master@{#828150}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/d4e6fb6573e0..9abde8c3f3a2

2020-11-17 sigurds@chromium.org Reland "Add option to git cl st to sort by committer date"

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 ajp@google.com,apolito@google.com,ehmaldonado@google.com,sokcevic@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: ajp@google.com,apolito@google.com,ehmaldonado@google.com,sokcevic@google.com
Change-Id: Ib8ccae3e750621a3e00d8ff02315046c43fce667
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2544082Reviewed-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@{#828149}

Stop ARC once all required by ArcPolicy apps are installed and take a
snapshot.
When MGS is successfully started in blocked UI mode, wait for all
required by policy apps are installed, stop ARC instance and requirest
to take a snapshot from arc-data-snapshotd daemon.

BUG=b:161221001
TEST=components_unittests
TEST=unit_tests

Change-Id: I176f7aefea11847e80f0a9a3ae4ce0ac44d0edb3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2461382Reviewed-by: Roman Sorokin [CET] <rsorokin@chromium.org>
Reviewed-by: Achuith Bhandarkar <achuith@chromium.org>
Reviewed-by: Hidehiko Abe <hidehiko@chromium.org>
Reviewed-by: Yusuke Sato <yusukes@chromium.org>
Commit-Queue: Polina Bondarenko <pbond@chromium.org>
Auto-Submit: Polina Bondarenko <pbond@chromium.org>
Cr-Commit-Position: refs/heads/master@{#828148}

Extend it to milestone 92.

Bug: 980846
Test: None
Change-Id: I379a9bcafbc8b4e4c1e09287ea577a96d0beb10d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2543539
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@{#828147}

Move validation logic into ValidateSpeculativeFrameHostForBug1146573.

Also fixes the problem of dumping too often by not dumping when
replacing a crashed RFH.

Bug: 1146573
Change-Id: Ifcae2662ca7fa071440a5e1d069936683f763269
Cq-Do-Not-Cancel-Tryjobs: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2538863
Commit-Queue: Fergal Daly <fergal@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Auto-Submit: Fergal Daly <fergal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#828146}

These metrics used the legacy Blink helpers to record enumeration
histograms; rather than migrating them to the preferred helpers in
//base/metrics, just remove them.

Bug: 1047547
Fixed: 975724, 975724, 1037132
Change-Id: I8f428f02d06b53aeaa31c5623ea776d630fa8732
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2524930Reviewed-by: Patrick Noland <pnoland@chromium.org>
Reviewed-by: Weilun Shi <sweilun@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Steve Kobes <skobes@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: vmpstr <vmpstr@chromium.org>
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#828145}

I am removing myself from watchlist, and as I am the only one to use it,
I'm removing the rule too.

Bug: none
Change-Id: I3b83556d0d03de88113142ccd4166d2522d88f98
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2540627
Auto-Submit: Stepan Khapugin <stkhapugin@chromium.org>
Commit-Queue: Sylvain Defresne <sdefresne@chromium.org>
Reviewed-by: Sylvain Defresne <sdefresne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#828144}

This CL adds the add-new-tab-button, which is not tappable and which is
not moving the position according to the number of tabs.

Bug: 1134132,1128249
Change-Id: Ia72835684f8d65879c863041a503835dad2a67d3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2536469
Commit-Queue: Nazerke Kalidolda <nazerke@google.com>
Reviewed-by: Gauthier Ambard <gambard@chromium.org>
Cr-Commit-Position: refs/heads/master@{#828143}

Quarantined objects do not need to be scanned at all. For larger
objects with size >= kLargeScanAreaThreshold, it's beneficial to check
the quarantine bit before performing a scan.

Locally reduces Speedometer2 regression from ~6% to around ~2.5% with
the current partition configuration (renderer + browser).

Bug: 11297512
Change-Id: I97627898733f6cdb1fa7b0dc18a39b1b4566f48e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2540594
Commit-Queue: Michael Lippautz <mlippautz@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Bartek Nowierski <bartekn@chromium.org>
Reviewed-by: Anton Bikineev <bikineev@chromium.org>
Cr-Commit-Position: refs/heads/master@{#828142}

Change the names of the string placeholders from ENROLLMENT_DOMAIN or
DOMAIN to MANAGER in order to make it clearer for the translators that
the placeholder can be replaced either by a domain or by an individual
managing the users and devices. Additionally adjust several messages
that explicitly mention the domain.

Bug: b:172676091, b:172676651, b:172676763, b:172676861, b:172678391, b:172678434, b:172678602, b:172678610, b:172679002, b:172680043, b:172680296, b:172682943, b:172683064
Test: None
Skip-Translation-Screenshots-Check: True
Change-Id: I938f7dc563733e6cdd3c5cbee8c1692c4444cc5d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2537534
Commit-Queue: Jana Grill <janagrill@chromium.org>
Reviewed-by: Greg Levin <glevin@chromium.org>
Reviewed-by: Brian Malcolm <bmalcolm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#828141}

The expectation of PartitionAllocMemoryReclaimer::Reclaim() is that
all unused memory gets reclaimed, which requires a scan to be run.

In general: Purging memory may only be effective when running PCScan
before doing so, as otherwise quarantined memory keeps buckets and
their PartitionRoot used.

Bug: 11297512
Change-Id: I82b39dd8662df3a32dbf21a795de86b160684f18
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2539200
Commit-Queue: Michael Lippautz <mlippautz@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Bartek Nowierski <bartekn@chromium.org>
Reviewed-by: Anton Bikineev <bikineev@chromium.org>
Cr-Commit-Position: refs/heads/master@{#828140}

No behavior is changed, only test code.
- Sign-in before creating the sync service.
- Use MANUAL_START, which is more common than AUTO_START these days.

Bug: None
Change-Id: I739b950b97e01321008b72c984b909ec09bde6ee
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2540595
Commit-Queue: Victor Vianna <victorvianna@google.com>
Reviewed-by: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#828139}

This will become even more useful once we roll in
https://reviews.llvm.org/rGf2710d4b576053d405af7a0e2a62ea06d5a978e3

Bug: 1149587
Change-Id: Ia6953f31fcbf3dc0e1041112d437fb20e1f6e9eb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2542122Reviewed-by: Hans Wennborg <hans@chromium.org>
Commit-Queue: Hans Wennborg <hans@chromium.org>
Auto-Submit: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#828138}

https://pdfium.googlesource.com/pdfium.git/+log/b8a27ae001c2..6823afb28ceb

2020-11-17 nigi@chromium.org Enable some Windows-only embedder tests for Skia/SkiaPaths.
2020-11-17 nigi@chromium.org Enable FPDFEditEmbedderTest.RemoveMarkedObjectsPrime for Skia/SkiaPaths.
2020-11-17 nigi@chromium.org Roll third_party/skia/ ae4bb98f1..1ce8964db (756 commits)
2020-11-17 nigi@chromium.org Roll tools/clang/ c5290b5af..c72342ce9 (39 commits)
2020-11-17 nigi@chromium.org Roll third_party/freetype/src/ 007c109b4..32b14552d (13 commits)
2020-11-17 nigi@chromium.org Roll buildtools/ 4be464e05..6302c1175 (8 commits)
2020-11-17 nigi@chromium.org Roll build/ 50f81f245..182e4cef2 (336 commits)
2020-11-17 nigi@chromium.org Roll third_party/skia/ 4c3486e6f..ae4bb98f1 (1 commit)
2020-11-17 nigi@chromium.org Roll third_party/zlib/ 26211a5a8..e84c9a3fd (2 commits)
2020-11-17 nigi@chromium.org Roll tools/memory/ ee1e24481..f685c086b (1 commit)
2020-11-17 nigi@chromium.org Roll third_party/icu/ aba3f0dfe..7db579a73 (12 commits)
2020-11-17 nigi@chromium.org Roll third_party/depot_tools/ 422c039e8..da73999f7 (72 commits; 20 trivial rolls)
2020-11-16 tsepez@chromium.org Remove CFXJSE_Values from CFXJSE_FormCalcContext::Mod() and Round()
2020-11-16 tsepez@chromium.org Remove CFXJSE_Value from CFXJSE_FormCalcContext::ApplyToExpansion().
2020-11-16 pdfium-autoroll@skia-public.iam.gserviceaccount.com Roll Catapult from 89eeef5150cb to ed4fb99735f4 (55 revisions)

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pdfium-autoroll
Please CC pdfium-deps-rolls@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: None
Tbr: pdfium-deps-rolls@chromium.org
Change-Id: Ib777eacf8c0091b101060c318bcef58d79cfd29c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2543475Reviewed-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@{#828137}

When a dynamic resolution change occurs and a new picture is imported
under the same ID as a previously existing one, we need to release the
reference to the old frame in picture_at_client_, otherwise the
reference counter will never to back to 0 and the picture will never be
released.

BUG=b:161759267
BUG=b:165035340
BUG=b:172881995
TEST=DRC with Youtube Android app on Trogdor now takes place smoothly.
TEST=CTS H264 AdaptivePlaybackTests now pass.

Change-Id: I82350fbc9355d22365b7f6432243b3ecb39a22b3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2540206
Commit-Queue: Alexandre Courbot <acourbot@chromium.org>
Reviewed-by: Chih-Yu Huang <akahuang@chromium.org>
Auto-Submit: Alexandre Courbot <acourbot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#828136}

This was reset once per navigations, which includes same-document
navigations (in-page scroll toward #fragment). This doesn't look right.
This has been moved toward DidCommitNewDocument().

Bug: 1113294.
Change-Id: Ib8a62f29ab53b11828475b83f2fe7c0df7e360e9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2536468
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Jonathan Ross <jonross@chromium.org>
Cr-Commit-Position: refs/heads/master@{#828135}

Adds setShowFlexOverlays methods according to:

https://docs.google.com/document/d/1MmJtT_KaNYq3iTiDQJHuEVOI0vHaJRVnPdVMAaG6tAE

Bug: 1145997
Change-Id: I945252bf625c98ff98043d8feaf620f77075393d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2527133
Commit-Queue: Alex Rudenko <alexrudenko@chromium.org>
Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#828134}

TBR=bling-team@google.com

Change-Id: I693ddd491b5d0a96b75b1cf1b78aee767b9c241c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2542858Reviewed-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@{#828133}

This reverts commit 108797c3.

Reason for revert: Underlaying problem fixed in webrtc. https://webrtc-review.googlesource.com/c/src/+/193063

Original change's description:
> Disable flaky */ConnectionTest.VideoWithSlowSignaling/*
>
> Bug: 1143311
> Change-Id: I131bb5b58f8f403d2752288c6e2c4a8ec11e15a7
> NoTry: True
> Tbr: joedow@chromium.org
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2523302
> Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org>
> Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#825119}

TBR=xiaochengh@chromium.org

# Not skipping CQ checks because original CL landed > 1 day ago.

Bug: 1143311
Change-Id: I0aa89b44e48335b08b0615c6ba9edc6c405218fb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2544122Reviewed-by: Per Kjellander <perkj@chromium.org>
Commit-Queue: Per Kjellander <perkj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#828132}

...similar to what we do for Windows.

This is to pick up:
- include/c++/v1 to pick up libc++ headers for the very few targets
  that use system libc++ (which on macOS assumes that library headers
  are bundled with the compiler), like gcapi
- libclang_rt.osx.a for __isPlatformVersionAtLeast (needed everywhere)

Bug: 1147069
Change-Id: I9da25218686466c29b171ca959bbe5a529cccfdc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2542183
Auto-Submit: Nico Weber <thakis@chromium.org>
Commit-Queue: Hans Wennborg <hans@chromium.org>
Reviewed-by: Hans Wennborg <hans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#828131}

Bug: 1132403
Change-Id: Ie44b69c074794cbd10a08289e389e502e8e94ccc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2539892Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Commit-Queue: dpapad <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#828130}

This was a well-known flag so it wasn't removed immediately but instead
printed a deprecation messages when it was used. This was more than
three months ago which is enough time for deprecation so this CL removes
the flag.

Also uses more inclusive language in a comment found with `git grep`.

Bug: chromium:1101491
Change-Id: I6dd147ca0e5a7b55175995be4f46dcc11bb7d138
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2540668
Auto-Submit: Corentin Wallez <cwallez@chromium.org>
Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Reviewed-by: Colin Blundell <blundell@chromium.org>
Commit-Queue: Colin Blundell <blundell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#828129}

BUG=webrtc:7061

Change-Id: I4bf6df92f64635880cd3aae35bf4f61881199868
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2543145
Commit-Queue: Philipp Hancke <philipp.hancke@googlemail.com>
Reviewed-by: Henrik Boström <hbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#828128}

This reverts commit e256a45e.

Reason for revert:
Seems that this header is used by Drive and Doc offline.

Original change's description:
> Stop sending X-Chrome-Connected header when Mirror is disabled
>
> The header X-Chrome-Connected header was sent to Gaia and Drive even
> when Mirror is disabled. However it seems that this header is ignored
> server-side, so it is better from privacy perspective to stop sending
> it.
>
> Bug: 1149163
>
> Change-Id: I361754ed4d74b10a4347975d614efbd29be41d1c
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2537838
> Reviewed-by: David Roger <droger@chromium.org>
> Commit-Queue: Mihai Sardarescu <msarda@chromium.org>
> Auto-Submit: Mihai Sardarescu <msarda@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#827813}

TBR=droger@chromium.org,msarda@chromium.org

Change-Id: Icc095489c0c6762b2eb7dba76c4d7ccfda1ecce6
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 1149163
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2543023Reviewed-by: Mihai Sardarescu <msarda@chromium.org>
Commit-Queue: Mihai Sardarescu <msarda@chromium.org>
Cr-Commit-Position: refs/heads/master@{#828127}

This reverts commit 93cc91b2.

Reason for revert:

Findit (https://goo.gl/kROfz5) identified CL at revision 828123 as the
culprit for failures in the build cycles as shown on:
https://analysis.chromium.org/waterfall/culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyRAsSDVdmU3VzcGVjdGVkQ0wiMWNocm9taXVtLzkzY2M5MWIyZTRlZGU0MTYwNTRlNTVkNGMyNmEzMjAyNjZkZTA3NjYM

Sample Failed Build: https://ci.chromium.org/b/8863396302867752096

Sample Failed Step: compile

Original change's description:
> Mojoify DidCommitProvisionalLoadParams
> 
> Turn the IPC struct:
> FrameHostMsg_DidCommitProvisionalLoad_Params
> 
> Into a mojo struct
> mojom::DidCommitProvisionalLoadParams
> 
> This is mostly straigforward, except:
> 
> 1. The functions have been updated to correctly specify whether
>    ownership over this struct is passed or not. Use one of "const T&" /
>    "T*", "TPtr*".
> 
> 2. Mojo checks the required params are populated. This forced me to
>    update several unittests to construct the required params. Like the
>    referrer or the navigation_token.
> 
> 3. blink::mojom::Referrer is used instead of the old content::Referrer
>    This required adding (temporarily) the conversion between both when
>    needed.
> 
> Fixed: 1145888
> Bug: 1145888
> Change-Id: Ib94cff3921d0212d8c1556062326d6cb6d0dcba4
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2529096
> Reviewed-by: Nasko Oskov <nasko@chromium.org>
> Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#828123}


Change-Id: If87cc3dce40bc743138b7225818db9073f4ca474
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 1145888
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2542857
Cr-Commit-Position: refs/heads/master@{#828126}

Because of differences in precision when using timestamps from
performance.now() and timestamps from RTCStats.timestamp it was
possible for the test "RTCStats.timestamp increases with time passing"
to fail, e.g:

  assert_less_than_equal: expected a number less than or equal to
  505.65500000084285 but got 506

By flooring t0 and ceiling t1 we get a more broader view of the
maximumTimeElapsedBetweenGetStatsCallsMs.

This should fix the flake. If it doesn't, the issue may be related to
using different clocks or somehting, in which case we'll have to
revisit what this test can assert. For now, let's land and see if the
flake goes away.

TBR=philipp.hancke@googlemail.com

Bug: chromium:1093020
Change-Id: Ie8c8e379a244ca53ed207d20c5f4de68606d29d7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2543923Reviewed-by: Henrik Boström <hbos@chromium.org>
Reviewed-by: Philipp Hancke <philipp.hancke@googlemail.com>
Commit-Queue: Henrik Boström <hbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#828125}

This CL injects and removes the objects into all frames in
RemoteObjectInjector#addInterface and set an allow of inspection
to all frames.

Bug: 1105935
Change-Id: Ica6bba74e7f5c5f5eada272979bd15b690d6a254
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2532141
Commit-Queue: Miyoung Shin <myid.shin@igalia.com>
Reviewed-by: Bo <boliu@chromium.org>
Reviewed-by: Oksana Zhuravlova <oksamyt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#828124}

Turn the IPC struct:
FrameHostMsg_DidCommitProvisionalLoad_Params

Into a mojo struct
mojom::DidCommitProvisionalLoadParams

This is mostly straigforward, except:

1. The functions have been updated to correctly specify whether
   ownership over this struct is passed or not. Use one of "const T&" /
   "T*", "TPtr*".

2. Mojo checks the required params are populated. This forced me to
   update several unittests to construct the required params. Like the
   referrer or the navigation_token.

3. blink::mojom::Referrer is used instead of the old content::Referrer
   This required adding (temporarily) the conversion between both when
   needed.

Fixed: 1145888
Bug: 1145888
Change-Id: Ib94cff3921d0212d8c1556062326d6cb6d0dcba4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2529096Reviewed-by: Nasko Oskov <nasko@chromium.org>
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#828123}

Send a `Page.DocumentOpened` event via CDP when an iframe's content is
edited via JS. Writing to an iframe's document via JS is not considered
a navigation, therefore no `Page.Navigated` CDP event is emitted. But
since writing to an iframe's document can change attributes which
DevTools needs to be informed about, the `Page.DocumentOpened` event is
emitted instead. Previously only a refresh of DevTools would let
DevTools know about changes to an iframe caused by JS manipulation of
said iframe.

Example (see http://doc/1gczarAME7AATGHwqm_IDqcGFlOM6DLAoX9rqetv4Rx0):
There is a 'frameNavigated' event for the initial load of an iframe.
If there is a 'document.write' for this iframe right away, there is no
'frameNavigated' event for this iframe at all.

Frontend CL: https://crrev.com/c/2507793
(needs to be merged first, this will fix the failing tests, which fail
because the frontend cannot handle unknown CDP events)

Bug: chromium:1140540, chromium:1140481


Change-Id: I92a659b7ab8b1cb7ae50e28df40b8ca9b0bf8c86
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2498482
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Auto-Submit: Wolfgang Beyer <wolfi@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Sigurd Schneider <sigurds@chromium.org>
Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#828122}

In order to send different detached notifications,
we need to make sure that WebContents is associated with will_delete.

This becomes essential with the new ClosedTabCache feature, which
changes the assumption that the WebContents will be deleted after
detaching.

We do the following in this CL to fix this scenario:
 - Removes ‘will_delete’ from TabStripModel::DetachNotifications
   struct and Move it to TabStripModel::DetachedWebContents.
 - Move TabStripModelChange::Remove ‘will_be_deleted’ member to
   TabStripModelChange::Removed contents with addition of
   will_be_deleted to ContentsWithIndex.

ContentsWithIndexAndWillBeDeleted is added to TabStripModelChange to
associate WebContents with will_be_deleted used inside Remove struct.

BUG=1146370

Change-Id: Ifa2d1378449e057e8ce297ce6f8f6e31bed90d5f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2522585Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Sreeja Kamishetty <sreejakshetty@chromium.org>
Cr-Commit-Position: refs/heads/master@{#828121}

CSPEE (Content-Security-Policy: Embedded Enforcement)
is a mechanism for a parent frame to enforce some Content
Security Policies on a child frame. This was originally
implemented in Blink, and later moved to the Browser.
The Blink implementation has been put behind a feature flag
and deactivated.

Since it seems that the new implementation in the Browser
is working correctly, the old Blink code and the feature
flag are now safe to remove.

Bug: 1094909
Change-Id: If299c5561b9f55330234c6fdf85d3faf2c4462d5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2410408Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: Antonio Sartori <antoniosartori@chromium.org>
Cr-Commit-Position: refs/heads/master@{#828120}

GPU.SupportsDX12
GPU.D3D12FeatureLevel
Viz.DisplayCompositor.RootDamageRect.Underlay
Viz.DisplayCompositor.RootDamageRect.Overlay

Bug: 1149513, 1140045
Change-Id: If7abff2968708f2f4c234d87f55d6bb26b25c2ed
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2543184
Auto-Submit: Maggie Chen <magchen@chromium.org>
Reviewed-by: Weilun Shi <sweilun@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Commit-Queue: Ilya Sherman <isherman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#828119}

EULA screen doesn't fetch the password anymore and the removed class
doesn't have any other consumers.

BUG=b:172748724
BUG=b:168852740
TEST=browser_tests.

Change-Id: Ic72312280fd7768b36ebba6aff476eb7aec50f07
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2536658
Commit-Queue: Leo Lai <cylai@google.com>
Reviewed-by: Achuith Bhandarkar <achuith@chromium.org>
Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Cr-Commit-Position: refs/heads/master@{#828118}

Remove v8::ScriptCompiler::CompileOptions option that is no longer
supported from ScriptStreamer.

The V8-side changes have landed in 8.8: https://crrev.com/c/2498698

Bug: 1061857, v8:11165
Change-Id: I06b8c23cfb1ed3b397c0df024366848f8b7c1636
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2540453Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Camillo Bruni <cbruni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#828117}

This CL contains a few changes to make working with
poilcy-recommended (marked as "Recommended" in ONC) IP and
Namserver settings possible in the Chrome OS network settings UI.

(1) ui/webui/resources/cr_components/chromeos/network/
    network_nameservers.js
(1.1) When selecting 'custom' in the UI, introduce explicit priority
      among the nameservers to display:
      policy-enforced > previously user-entered > recommended > active
      (getCustomNameServers)
(1.2) |savedCustomNameservers_|: Keep track of the most recent
      manually selected nameservers type, to be able to handle the case
      of 'google' nameservers coming in from the backend by selecting
      'custom' (if the user last selected 'custom') or 'google' if the
      user never selected anything or something else than 'custom'.
(1.3) setNameservers_():
      Get rid of async hack.

(2) ui/webui/resources/cr_components/chromeos/network/
    network_ip_config.js
    Correctly merge saved/backend-provided IPv4 settings with defaults
    on changing to "automatic".

Bug: 1108922, 1109660, 1109670
Change-Id: I18c2ab5ae69a4922f3d63584975f6f3424dee9e4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2449449
Commit-Queue: Pavol Marko <pmarko@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#828116}