GitLab

https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/89cf59f82a6b..9bed95f88a26

2020-11-03 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update DevTools 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: None
Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com
Change-Id: I363f2307528226b42d5c305940e5f56df34b552f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2516900Reviewed-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@{#823543}

Only significant change is to ignore any params received with alias
records.

Bug: 1138620
Change-Id: I5d30127b07a5347c6215077ebfb49d0dc8f19b1e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2515560
Auto-Submit: Eric Orth <ericorth@chromium.org>
Commit-Queue: Dan McArdle <dmcardle@chromium.org>
Reviewed-by: Dan McArdle <dmcardle@chromium.org>
Cr-Commit-Position: refs/heads/master@{#823542}

Prior to this CL, the kWebRtcThermalResource feature was enabled by
default on all platform, after having been successfully rolled out with
.gcl. However, only on macOS did the thermal resource actually receive
any signal from the OS about thermal states, so on non-mac injecting a
thermal resource into webrtc did not have any observable affects on
adaptation.

In order to support platform-specific rollout of this feature, this CL
changes the default to DISABLED on all platforms except the one we are
confident in: macOS.

We want to do this because in M88, thermal states was implemented on
ChromeOS, and we want to begin a rollout where the default values of
the feature is off.

TBR=guidou@chromium.org

Bug: chromium:1144734
Change-Id: Id1f746013f8a279f5cc4f6b9cd7e48d9a069f70d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2516940Reviewed-by: Henrik Boström <hbos@chromium.org>
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Commit-Queue: Henrik Boström <hbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#823541}

https://chromium.googlesource.com/angle/angle.git/+log/ed916ddf61cc..6a4c9bbd5185

2020-11-03 angle-autoroll@skia-public.iam.gserviceaccount.com Roll SPIRV-Tools from f7da52775714 to 5735576f87be (1 revision)
2020-11-03 angle-autoroll@skia-public.iam.gserviceaccount.com Roll Vulkan-Tools from 3f747ee91e3b to 51c1c5ab56d5 (1 revision)
2020-11-03 angle-autoroll@skia-public.iam.gserviceaccount.com Roll Vulkan-ValidationLayers from e46399ddd2c7 to 1b2f8307f21d (7 revisions)
2020-11-03 angle-autoroll@skia-public.iam.gserviceaccount.com Roll SwiftShader from 7751fe38f474 to b5bf82693f85 (7 revisions)
2020-11-03 angle-autoroll@skia-public.iam.gserviceaccount.com Roll Chromium from a64ace71 to ce54b897 (254 revisions)
2020-11-03 syoussefi@chromium.org Vulkan: Use dst access masks to determine if barrier is needed
2020-11-03 xiaoxuan.liu@arm.com Reland "Add support for Linux vulkan backend with VK_KHR_display"
2020-11-03 courtneygo@google.com Allow single threaded CommandProcessor
2020-11-03 jmadill@chromium.org Test Runner: Robustly handle unexpected crashes.
2020-11-03 m.maiya@samsung.com Vulkan: Bug fix in sRGBDecode logic
2020-11-02 jmadill@chromium.org Test Runner: Add ability to retry flaky tests.
2020-11-02 angle-autoroll@skia-public.iam.gserviceaccount.com Roll VK-GL-CTS from e69b9b7294af to 9e07e4424cd4 (5 revisions)
2020-11-02 thomasanderson@chromium.org Remove dependency on //build/config/linux:x11
2020-11-02 angle-autoroll@skia-public.iam.gserviceaccount.com Roll Chromium from f2fabcd1 to a64ace71 (130 revisions)
2020-11-02 jmadill@chromium.org Expand suppression of new EGL test.
2020-11-02 syoussefi@chromium.org Noop clear of non-existing attachments.
2020-11-02 syoussefi@chromium.org Noop empty-scissor clears
2020-11-02 jmadill@chromium.org Revert "Add support for Linux vulkan backend with VK_KHR_display"
2020-11-02 jmadill@chromium.org Tests: Print warning when we hit display reuse limit.
2020-11-02 syoussefi@chromium.org Vulkan: Fix prerotation bug with glInvalidateSubFramebuffer
2020-11-02 amy.liu@arm.com Fix maxShaderAtomicCounters value.
2020-11-02 xiaoxuan.liu@arm.com Add support for Linux vulkan backend with VK_KHR_display
2020-11-02 angle-autoroll@skia-public.iam.gserviceaccount.com Roll SPIRV-Tools from 34ae8a475754 to f7da52775714 (8 revisions)
2020-11-02 angle-autoroll@skia-public.iam.gserviceaccount.com Roll Vulkan-ValidationLayers from f673b4e6ebf3 to e46399ddd2c7 (11 revisions)
2020-11-02 angle-autoroll@skia-public.iam.gserviceaccount.com Roll glslang from 740ae9f60b00 to 142cb87f803d (1 revision)
2020-11-02 angle-autoroll@skia-public.iam.gserviceaccount.com Roll SwiftShader from e6c9497255c6 to 7751fe38f474 (3 revisions)
2020-11-02 angle-autoroll@skia-public.iam.gserviceaccount.com Roll Vulkan-Headers from 320af06cbdd2 to 87451c55aa8b (1 revision)

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/angle-chromium-autoroll
Please CC courtneygo@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_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win-asan;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86
Bug: chromium:1066670
Tbr: courtneygo@google.com
Test: Test: dEQP-GLES31.functional.shaders.opaque_type_indexing.atomic_counter.*vertex
Change-Id: Iab4601f31e54eb61b24d15c309855d3f64896002
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2516903Reviewed-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@{#823540}

Changed the flag which controls whether a HaTS v1 or HaTS Next survey is
launched to default to launching HaTS Next surveys, instead of HaTS v1.

This flag by itself does not change any behavior, and must be combined
with a survey feature to deliver a survey. No HaTS v1 surveys are
currently running in Chrome, and the service has been deprecated.

Bug: 1110888
Change-Id: I49a97cda08e5cd7a79195b4da9ad9f5cca645bfa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2514209
Commit-Queue: Theodore Olsauskas-Warren <sauski@google.com>
Reviewed-by: Sean Harrison <harrisonsean@chromium.org>
Cr-Commit-Position: refs/heads/master@{#823539}

The screen recording part of the new screen capture feature
should be connected to the same SCREENSHOT restriction in DLP policy.

Tests: New browsertest
Bug: 1133324
Change-Id: If43440522edde5b1d4cc51400ec7f501c9d63074
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2510330
Commit-Queue: Sergey Poromov <poromov@chromium.org>
Reviewed-by: Nikita Podguzov <nikitapodguzov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#823538}

The inspector fuzzer was added to v8 in https://crrev.com/c/2505722.

R=mmoroz@chromium.org
CC=ahaas@chromium.org

Bug: chromium:1142437
Change-Id: I5d2271f222ce91327eed1c03a548054a190e9c2b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2510132Reviewed-by: Andreas Haas <ahaas@chromium.org>
Reviewed-by: Max Moroz <mmoroz@chromium.org>
Commit-Queue: Clemens Backes <clemensb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#823537}

FrameConnectorDelegate was created to provide a delegation interface
for RenderWidgetHostViews in content/browser/renderer_host to interact
with embedding frames in content/browser/frame_host without breaking
layering rules.

Since http://crrev.com/805452 and its follow up CLs, frame_host has
been merged into renderer_host, making the delegation unnecessary.

Change-Id: I2450938c8d48aba8fd35451d9a6dca030a8e8d71
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2515120Reviewed-by: Avi Drissman <avi@chromium.org>
Commit-Queue: Ken Buchanan <kenrb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#823536}

This change enables the WellKnownChangePassword feature by default.

Bug: 927473
Change-Id: I05f4fdae2fd4364fc5b184c25339244ec0fcaece
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2513216
Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org>
Reviewed-by: Friedrich [CET] <fhorschig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#823535}

cros_healthd had removed two paramters from two battery routines:
- |low_mah| and |high_mah| from 'BatteryCapacityRoutine'.
- |maximum_cycle_count| and |percent_battery_wear_allowed| from
'BatteryHealthRoutine'.

This CL removes the corresponding parameters from the corresponding
routines found in TelemetryExtension in both:
- Mojo interface exposed to Telemetry SWXs.
- WebIDL interface exposed to third-party code.
Also removes the dependency on the removed parameters from
browser_tests.

Bug: b:171327161
Change-Id: Idaa57d0a05986883c26337a151f0c0adfb5f5272
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2507698Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Oleh Lamzin <lamzin@google.com>
Commit-Queue: Mahmoud Gawad <mgawad@google.com>
Cr-Commit-Position: refs/heads/master@{#823534}

This just changes the wording for the deprecation message for
the :unresolved pseudo selector. Instead of "will be removed",
it now just says "removed".

Bug: 937746
Change-Id: I694bcefabf34f9399000206d30da50b62fbf01b9
Cq-Do-Not-Cancel-Tryjobs: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2514081Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Mason Freed <masonfreed@chromium.org>
Auto-Submit: Mason Freed <masonfreed@chromium.org>
Cr-Commit-Position: refs/heads/master@{#823533}

Roll Chrome Linux PGO profile from chrome-linux-master-1604382852-89adcc94b5376db481c405a47786acd9d71a0a15.profdata to chrome-linux-master-1604404061-a0e49f41ece3a518deb5950cf222a12f66659bab.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: Ia62dbdfaf5cd6dc97a01279f8bfcbf940b5b2fbd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2516906Reviewed-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@{#823532}

https://webrtc.googlesource.com/src.git/+log/ee24eb66d23f..42cafa5696f5

2020-11-03 nisse@webrtc.org Delete legacy stats minWaitingTimeMs and medianWaitingTimeMs from ACM.
2020-11-03 nisse@webrtc.org Replace RWLockWrapper --> Mutex in ScreenCapturerHelper
2020-11-03 natim@webrtc.org Adding total duration and more test cases to VoipStatistics.
2020-11-02 terelius@webrtc.org Fix incorrect ToUnsigned in RTC event log.
2020-11-02 hta@webrtc.org Check for oversized TURN usernames
2020-11-02 nisse@webrtc.org Delete master_timing argument to VCMTiming.
2020-11-02 jakobi@webrtc.org Reland "Reland "Default enable WebRTC-SendSideBwe-WithOverhead.""
2020-11-02 gustaf@webrtc.org Increased high frequency transparency
2020-11-02 jakobi@webrtc.org Use non-null transport for RTCP in AV sync test.
2020-10-30 philipp.hancke@googlemail.com doc: mention video_replay tool for reporting video bugs
2020-10-30 mbonadei@webrtc.org Reformat python files checked by pylint (part 1/2).
2020-10-30 nisse@webrtc.org Delete internal locking in TimestampExtrapolator class.
2020-10-30 hta@webrtc.org Remove obsolete GetRemoteAudioSSL* functions.
2020-10-30 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 2abf60f7..2357c735 (822386:822514)
2020-10-29 deadbeef@webrtc.org Free data if SCTP packet is delivered after transport destruction.
2020-10-29 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 0cbb40a9..2abf60f7 (822259:822386)
2020-10-29 alessiob@webrtc.org AGC2 RNN VAD size_t -> int
2020-10-29 deadbeef@webrtc.org Update set of known root certificates.
2020-10-29 auorion@microsoft.com Add and refactor functionality into rtc_base/win
2020-10-29 alessiob@webrtc.org RNN VAD: Pitch periods as integers and for-if-break optimization
2020-10-29 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision c8ecd260..0cbb40a9 (822116:822259)
2020-10-29 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 28455e96..c8ecd260 (821997:822116)
2020-10-29 ssilkin@webrtc.org Analyze quality of dropped frames in VideoProcessor.
2020-10-29 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision a9d053b9..28455e96 (821860:821997)
2020-10-28 natim@webrtc.org VoipStatistics subAPI and implementation.
2020-10-28 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 3201204f..a9d053b9 (821703:821860)
2020-10-28 ivoc@webrtc.org Reset NetEq simulation step time if a large gap is detected.
2020-10-28 philipel@webrtc.org Removed _completeFrame since we never allow incomplete frames.
2020-10-28 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 5c9a5207..3201204f (821334:821703)
2020-10-28 nisse@webrtc.org Fix locking in RTPFile class
2020-10-27 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 473d43b3..5c9a5207 (821175:821334)
2020-10-27 sprang@webrtc.org Updates how min bitrate is set for VP9 SVC in perf tests.
2020-10-27 ivoc@webrtc.org Remove deprecated PacketArrived method from NetEqController interface.

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: chromium:1127774,chromium:1144646
Tbr: webrtc-chromium-sheriffs-robots@google.com
Change-Id: If0271b1a073b8bab73994f09e702f2bdfecbb071
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2516902Reviewed-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@{#823531}

This reverts commit 3dcbf868.

Reason for revert: Msan failure
Bug: 1145157

Original change's description:
> [CrOS PhoneHub] Add notification metrics.
>
> We add metrics for PhoneHub notification actions by introducing' a new
> PHONE_HUB notification type. This way, metrics will be logged into
> existing histograms.
>
> Additionally, this CL also adds a new Ash.PhoneHub.NotificationCount
> histogram counting the number of active PhoneHub notifications.
>
> BUG=1138137,1106937
>
> Change-Id: I4529eb6cc0d861ec9eb720e4eeac5c6d2d6257ce
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2505728
> Commit-Queue: Tim Song <tengs@chromium.org>
> Reviewed-by: Ilya Sherman <isherman@chromium.org>
> Reviewed-by: Yoshiki Iguchi <yoshiki@chromium.org>
> Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
> Reviewed-by: Andre Le <leandre@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#823474}

TBR=yoshiki@chromium.org,khorimoto@chromium.org,isherman@chromium.org,tengs@chromium.org,leandre@chromium.org

Change-Id: I523202c3a64f58d267dff229baf69dad1cfe8377
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 1138137
Bug: 1106937
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2517241Reviewed-by: Gayane Petrosyan <gayane@chromium.org>
Commit-Queue: Gayane Petrosyan <gayane@chromium.org>
Cr-Commit-Position: refs/heads/master@{#823530}

For reasons not yet understood, building it on the tot bots makes
the tot bots fail. It works fine on the upload bot, so only build
it there.

This change doesn't affect the clang package we distribute since it's
a no-op on the upload bots, and the tot bots don't use the arm64
iossim slice. We still should understand what's going on, since having
the tot bots and the upload bots do different things is suboptimal.

Bug: 1145151,1138425
Change-Id: Ib8d7a31289ec2caf6ccf2fe6e6ddadb4f908b4c4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2517240Reviewed-by: Hans Wennborg <hans@chromium.org>
Reviewed-by: Sylvain Defresne <sdefresne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#823529}

https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2503953
has landed

R=aerotwist@chromium.org

Bug: 1143170
Change-Id: I94cee3838e9ba305449b9ce0356f597e13074b7a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2503698
Commit-Queue: Tim van der Lippe <tvanderlippe@chromium.org>
Reviewed-by: Paul Lewis <aerotwist@chromium.org>
Reviewed-by: Simon Zünd <szuend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#823528}

Roll Chrome Mac PGO profile from chrome-mac-master-1604382852-9483a9470fa3ce55e504618f01ab71cbbe527541.profdata to chrome-mac-master-1604404061-6e4b1d6492901c864984b20d97dc0cd527cfcccf.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: Idfa89acd73a3f90ba269a7332e7ce95293055060
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2516905Reviewed-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@{#823527}

When fullscreen widget code was removed in crrev.com/406647a3 an
additional code path was accidentally removed. Add that code
path back in because it broken a callback that was necessary for
cast. It used it in the non-optimized fullscrene video for cast.

BUG=1144255

Change-Id: I6b3bdd2b20614a5995120434bd7d429119c0526d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2514076Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#823526}

Differently from other platforms, under Wayland, unmaximizing the
dragged window before starting the drag loop is not needed as it is
assumed to be handled at compositor side, in extended-drag sessions
[1][2]. Just like in xdg_toplevel_surface's move request.

Thus, this CL patches WaylandToplevelWindow::Restore() function such
that it is no-op if there is a window drag session running.

Bug: 896640
Test: ozone_unittests --gtest_filter='*WaylandWindowDragControllerTest.RestoreDuringWindowDragSession*'

[1] https://docs.google.com/document/d/1s6OwTi_WC-pS21WLGQYI39yw2m42ZlVolUXBclljXB4/edit#heading=h.gjdgxs
[2] https://source.chromium.org/chromium/chromium/src/+/master:third_party/wayland-protocols/unstable/extended-drag/extended-drag-unstable-v1.xml

Change-Id: Ifd07958604554686ca3bd7f7964b2dab80442316
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2508235
Commit-Queue: Nick Yamane <nickdiego@igalia.com>
Auto-Submit: Nick Yamane <nickdiego@igalia.com>
Reviewed-by: Maksim Sisov (GMT+2) <msisov@igalia.com>
Cr-Commit-Position: refs/heads/master@{#823525}

Roll Chrome Win32 PGO profile from chrome-win32-master-1604284542-523a5c2cc242e551c8b0becc0134f849b2e7b9d5.profdata to chrome-win32-master-1604361545-95869d864c8b2bd48e03f9a16b21429d633a6ea4.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-win32-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:win-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I0646620d4b383c02cb2ead822bcd77350bca6806
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2516380Reviewed-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@{#823524}

This CL adds the basic file structure for trigger scripts. Most classes
are only stubs, but the TriggerScript condition checking is already in
place. Subsequent CLs will replace the stubs to make this fully
functional.

Bug: b/171776026
Change-Id: Ic6b687242048c3f6ebf665d7611ff115a9a91ccd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2513595
Commit-Queue: Clemens Arbesser <arbesser@google.com>
Reviewed-by: Marian Fechete <marianfe@google.com>
Cr-Commit-Position: refs/heads/master@{#823523}

CookieSettingsFactory unittest is updated to cover ephemeral Guest
profiles.

Please see go/ephemeral-guest-profiles for more context.

Bug: 1125474
Change-Id: I71fa7a2027df6abf70a15bcde20ca0a3f749af0e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2516939Reviewed-by: Christian Dullweber <dullweber@chromium.org>
Commit-Queue: Ramin Halavati <rhalavati@chromium.org>
Cr-Commit-Position: refs/heads/master@{#823522}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/e0ff8ffa..33fdba02

Please follow these instructions for assigning/CC'ing issues:
https://v8.dev/docs/triage-issues

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,vahl@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com

Change-Id: Ia4168755ae2514f12e6fc18c31daa6062b500f6e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2516002Reviewed-by: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#823521}

Prior to this CL, video decoding used the main thread whenever gpu
acceleration is unavailable/disabled, and audio decoding always used the
main thread. Now both cases use a SequencedTaskRunner from the worker
(no relation to web workers) pool.

Also

Bug: 1095786
Change-Id: I1c6265cdb63bcd4dadf48fdbe9bd27622218b948
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2500526
Auto-Submit: Chrome Cunningham <chcunningham@chromium.org>
Commit-Queue: Alexander Timin <altimin@chromium.org>
Reviewed-by: Alexander Timin <altimin@chromium.org>
Reviewed-by: Dan Sanders <sandersd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#823520}

This test checks that the configured DLP policy is correctly
converted into the corresponding Content Restriction.

Bug: 1109783
Change-Id: I17bba26c6d0eb791cbcd7483b94e1537f64609d4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2515683
Commit-Queue: Sergey Poromov <poromov@chromium.org>
Reviewed-by: Nikita Podguzov <nikitapodguzov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#823519}

This CL establishes a way to provide shared OOBE components via
individual URLs, using oobe_i18n_behavior as an example.

Bug: 1144159
Change-Id: I918c9f5c80ddc581813cdad65e68af032c9d34a2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2509515Reviewed-by: Renato Silva <rrsilva@google.com>
Commit-Queue: Denis Kuznetsov [CET] <antrim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#823518}

|ChromeWebContentsHandler::AddNewContents| assumed that a browser object
can be created in all situations but this is not true, at least if the
request comes during browser shutdown.

|ChromeWebContentsHandler::AddNewContents| is updated to consider the
case that browser cannot be created and gracefully exit.

Bug: 1141608, 1121894
Change-Id: Iaf0b2b4c1359ccf9b3b07ed606521a62c98ea4e3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2513209
Commit-Queue: Ramin Halavati <rhalavati@chromium.org>
Reviewed-by: Denis Kuznetsov [CET] <antrim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#823517}

This CL makes sure "camera" in page info UI is hidden when camera PTZ is
granted or blocked, regardless the state of the "Experimental Web
Platform features" switch. This is needed anymore as the
MediaCapturePanTilt feature is now enabled by default.

Bug: 1144253
Change-Id: If212a72c00e4bede8ad1a0ebacb9a306a7d38409
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2516223Reviewed-by: Balazs Engedy <engedy@chromium.org>
Commit-Queue: Balazs Engedy <engedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#823516}

* Recorded the Safety check start in the Interactions histogram
* Added missing non-error PasswordsResult values
* Fixed UpdatesResult to use UPDATED instead of UPDATING

Bug: 1145123, 1070620
Change-Id: I5c00fc8a9f34d6f802ce47263a3a6d5ec39d98f3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2516224Reviewed-by: Martin Šrámek <msramek@chromium.org>
Auto-Submit: Andrey Zaytsev <andzaytsev@google.com>
Commit-Queue: Andrey Zaytsev <andzaytsev@google.com>
Cr-Commit-Position: refs/heads/master@{#823515}

Bug: b/171025821
Change-Id: I45cb6e3af454c7790fb8ad4ee6494ece06b847e0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2516500
Commit-Queue: Rahul Goyal <goyalrahul@google.com>
Reviewed-by: Luca Hunkeler <hluca@google.com>
Cr-Commit-Position: refs/heads/master@{#823514}

Add a function to wait for EMCert to be uploaded and call it in
TpmChallengeKey* objects before replying to Verified Access challenges.

Bug: 1092653
Test: *TpmChallenge*, *MachineCertificateUploader*
Change-Id: Ied402214b9bda7783b1d3c5b6856b5c908807ad4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2452730
Commit-Queue: Michael Ershov <miersh@google.com>
Reviewed-by: Denis Kuznetsov [CET] <antrim@chromium.org>
Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Reviewed-by: Pavol Marko <pmarko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#823513}

No change to production logic. This unbatches AwSettingsTest. This is to
work around a bug with the @Batch annotation: if a test fails or
crashes, then all subsequent tests have status "unknown" and appear as
failures. We've received several "flaky test" bugs for tests which are
themselves perfectly fine but are failing due to a previous test's
failure.

It seems more effective to unbatch this test suite until
https://crbug.com/1127935 is resolved.

Bug: 1144352
Test: run_webview_instrumentation_test_apk -f AwSettingsTest.*
Change-Id: I8d42330909782d071ee2ffcec028a0171a4ad788
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2515785
Auto-Submit: Nate Fischer <ntfschr@chromium.org>
Commit-Queue: Bo <boliu@chromium.org>
Reviewed-by: Bo <boliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#823512}

https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/30ad9ea33821..89cf59f82a6b

2020-11-03 alexrudenko@chromium.org Add baseline icons for flexbox properties in the Styles panel
2020-11-03 jacktfranklin@chromium.org Migrate emulation/DeviceModeModel to TS.
2020-11-03 yangguo@chromium.org [ts] Typecheck RenderingOptions.js
2020-11-03 aerotwist@chromium.org TypeScriptify EventListenersView.js
2020-11-03 kimanh@chromium.org Add value interpreter to linear memory inspector
2020-11-03 yangguo@chromium.org [ts] Typecheck DefaultCodeMirrorMimeMode.js
2020-11-03 janscheffler@chromium.org Fix keyboard accessibility in security panel
2020-11-03 yangguo@chromium.org [ts] Typecheck LayerPaintProfilerView.js

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

This change performs remaining TODOs in the context of moving
PasswordForm to components/password_manager. These include removing the
password_form_forward.h header, as well as deleting the
autofill.mojom.PasswordFormFieldPredictionType enum.

TBR=dcheng,vasilii,sdefresne

Fixed: 1067347
Change-Id: I88bf0d074a4920bb3b371aefad1864917ee6550d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2515684Reviewed-by: Mohamed Amir Yosef <mamir@chromium.org>
Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org>
Cr-Commit-Position: refs/heads/master@{#823510}

Reland modularization of banners/ code.
Necessary dependencies on external repo have been added.
This reverts commit 9c0ee959.

This CL moves AppBanner* code from:
  chrome/android/banners
... to ...
  chrome/browser/banners/android
... and modularizes it in the process.

Bug: 1135551
Change-Id: I80d52038bff391239f7cbc43bdcb1f1f14767916
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2509571
Commit-Queue: Finnur Thorarinsson <finnur@chromium.org>
Auto-Submit: Finnur Thorarinsson <finnur@chromium.org>
Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Cr-Commit-Position: refs/heads/master@{#823509}

And rename it to CanUseUpdateService for the consistency.

The UpdateService::CanUpdate method doesn't use much from its class
(only a browser context to access one keyed service). From other side,
in the future we want this method to depend on extension management,
which is available for chrome/, but not for extensions/ layers. And the
only usage of CanUpdate is inside ExtensionUpdaters (which is already in
chrome/ layer).

Therefore, it makes sense to move this method in chrome/ layer,
specifically into ExtensionUpdater class. As a bonus, now this method is
private.

Bug: b:171782200
Change-Id: I6afd7e784e8cd95f8927aab8f818f307352f58a2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2503690
Commit-Queue: Oleg Davydov <burunduk@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#823508}

https://swiftshader.googlesource.com/SwiftShader.git/+log/959f41988a18..b5bf82693f85

2020-11-03 jari.komppa@siru.fi Add script to verify proper Memset template use

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

https://dawn.googlesource.com/dawn.git/+log/71d2e1d23d49..43ef0a365b84

2020-11-03 cwallez@chromium.org ValidationTest: Make custom device creation go through a virtual method

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

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

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

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

This CL replaces all uses of blink::MediaDeviceType with
blink::mojom::MediaDeviceType in order to reduce type
conversion between them.

Bug: 919392
Change-Id: I37bc2effefa790a2c0a1874738e94e41dada12ed
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2505347
Commit-Queue: Gyuyoung Kim <gyuyoung@igalia.com>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#823505}

Bug: b/171901437
Change-Id: Id0785abc0161a1f4f23e85050ab7f3c4f6007408
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2515682Reviewed-by: Rayan Kanso <rayankans@chromium.org>
Commit-Queue: Richard Knoll <knollr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#823504}