GitLab

The browsertests of statistics collector policy are moved from
policy_browsertests to a separate file.

Bug: 1128322
Change-Id: Ie35643f650c86d710ae470ec51745f8d227a07c0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2410063
Commit-Queue: Swapnil Gupta <swapnilgupta@google.com>
Reviewed-by: Sergey Poromov <poromov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807853}

This reverts commit 91b2c272.

Reason for reland: Don't use `thread_local`

Original change's description:
> base/allocator: Add a thread cache to PartitionAlloc.
>
> This CL adds a thread cache to PartitionAlloc. It is optional, only
> applies to thread-safe partitions, and uses the same freelist encoding
> and bucketing as the main allocator.
>
> The thread cache is added "in the middle" of the main allocator, that is:
> - After all the cookie/tag management
> - Before the "raw" allocator.
>
> That is, the general allocation flow is:
> 1. Adjustment of requested size to make room for tags / cookies
> 2. Allocation:
>   a. Call to the thread cache, if it succeeds, return.
>   b. Otherwise, call the "raw" allocator <-- Locking
> 3. Handle cookies/tags, zero allocation if required
>
> On the deallocation side, the process is reversed:
> 1. Check cookies / tags, adjust the pointer
> 2. Deallocation
>   a. Return to the thread cache of possible. If it succeeds, return.
>   b. Otherwise, call the "raw" allocator <-- Locking
>
> The thread cache maintains an array of buckets, the same as the parent
> allocator. A single thread cache instance is only used by a single
> partition. Each bucket is a linked list of allocations, capped to a set
> maximum size. Elements in this "freelist" are encoded the same way they
> are for the main allocator.
> Only the smallest buckets are eligible for caching, to reduce the
> memory impact.
>
> There are several limitations:
> - Only a single partition is allowed to have a thread cache
> - No periodic purging of thread caches is done
> - No statistics are collected
>
> The last two limitations will be addressed in subsequent CLs. Regarding
> the first one, it is not possible to use Chrome's native thread local
> storage support, as it allocates. It is also desirable to use
> thread_local to improve performance.
>
> Bug: 998048
> Change-Id: Ia771f507d9dd1c2c26a4668c76da220fb0c65dd4
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2375206
> Commit-Queue: Benoit L <lizeb@chromium.org>
> Reviewed-by: Kentaro Hara <haraken@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#805697}

Bug: 998048
Change-Id: If7fa5c2e1e10bc7dd1d41cdb188840668aad888f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2410126Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Benoit L <lizeb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807852}

Update the value on the session start.

Fixed: 893938
Change-Id: I949ecfcaba81c6d53d78853d0d4576ac5ae003c3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414209
Commit-Queue: Roman Sorokin [CET] <rsorokin@chromium.org>
Reviewed-by: Renato Silva <rrsilva@google.com>
Cr-Commit-Position: refs/heads/master@{#807851}

as buildbots missing H264 comes up frequently.

BUG=chromium:840659

Change-Id: I8db4bee8bbbc04d1227d957dcd6a73ee658ec829
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414315Reviewed-by: Harald Alvestrand <hta@chromium.org>
Commit-Queue: Philipp Hancke <philipp.hancke@googlemail.com>
Cr-Commit-Position: refs/heads/master@{#807850}

Fixed: 1125731
Change-Id: Icba338d52cce5a05de22e180a046157e22b7726b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2410871Reviewed-by: Brian White <bcwhite@chromium.org>
Commit-Queue: Vasilii Sukhanov <vasilii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807849}

I reviewed many of the changes in core dark mode module and recently
have been adding many changes. Going forward to assess correctness and
completeness, I would like to get involved in reviewing changes related
to this module.

Bug: None
Change-Id: I2bb51c6cbcff3bfb2b18be1a160c70952e1f8839
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2416188Reviewed-by: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Prashant Nevase <prashant.n@samsung.com>
Cr-Commit-Position: refs/heads/master@{#807848}

TBR=leese@chromium.org

Bug: 1129347
Change-Id: I576ab5489586e495cda867befa800b375d0add66
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414305Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807847}

This is a follow up CL of https://crrev.com/c/2377630 and moves
|never_composited| variable into WidetBase from RenderWidget.

Bug: 1102446
Change-Id: I7821c5890831cf4ccc17fc10f88b1d628f87114c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2407680
Commit-Queue: Miyoung Shin <myid.shin@igalia.com>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807846}

As a part of the effort to understand the current behavior of the
resource timing, I changed the tests to use async/await for readability
with adding a few comments.

Bug: 1128786
Change-Id: I45daee67e52a13c98ad3f2010131d858a58781d3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2413927
Commit-Queue: Makoto Shimazu <shimazu@chromium.org>
Auto-Submit: Makoto Shimazu <shimazu@chromium.org>
Reviewed-by: Kenichi Ishibashi <bashi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807845}

Bug: 1105381
Change-Id: I4f63f8d7de3bf9bd530dbe842fe47d736e2b04d6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2413567Reviewed-by: Sam McNally <sammc@chromium.org>
Reviewed-by: Austin Tankiang <austinct@chromium.org>
Commit-Queue: Sergei Datsenko <dats@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807844}

Logic is partly carried over from manage_input_methods.js

The original CL that added this logic doesn't explain much
https://crrev.com/1908483003.

This CL https://crrev.com/c/1109441 suggests component IMEs are
pre-installed system IMEs, which makes sense to ensure at least one is
enabled in case the third-party one get removed and users can no longer
type.

Button disabled view: http://screen/3qQgdYTc6UQBn8Y

Bug: 1113439
Change-Id: I4d07687a8ac0a2c705d8e83bfb938909149a2723
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2413677
Commit-Queue: My Nguyen <myy@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: Regan Hsu <hsuregan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807843}

Screenshot before: https://screenshot.googleplex.com/BARaxjkyDLmdPR5.png
Screenshot after: https://screenshot.googleplex.com/92GvmjRmJsErz2q.png

Bug: 1091563
Change-Id: Icfaccb7888cafe18a22c8897737bef458e20f3d4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2412341
Commit-Queue: Michael van Ouwerkerk <mvanouwerkerk@chromium.org>
Reviewed-by: Peter Conn <peconn@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807842}

The hiding/showing is normally done via
ReadingListListViewControllerAudience but the initial
setup is done before the navigationController was create.
It is necessary to create the navigationController in the
correct state.

Bug: 1128059
Change-Id: I2303356c71bf70f178a5f9a5c65f023750ecf05d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414273Reviewed-by: Olivier Robin <olivierrobin@chromium.org>
Reviewed-by: Gauthier Ambard <gambard@chromium.org>
Commit-Queue: Olivier Robin <olivierrobin@chromium.org>
Auto-Submit: Olivier Robin <olivierrobin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807841}

https://chromium.googlesource.com/catapult.git/+log/d03abd8af735..1d8e2d5acaf5

2020-09-17 vovoy@chromium.org Include the first valid tab switch latency

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/catapult-autoroll
Please CC oysteine@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:chromeos-kevin-rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Bug: chromium:899174
Tbr: oysteine@google.com
Change-Id: I64ebdd5ff5b43f89e01480a9e9729af477a7d701
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2415889Reviewed-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@{#807840}

Currently WaylandKeyboardDelegate internally tracks the
state of XKB. To fix the zwp_text_input behavior,
XKB state needs to be shared. So this CL extracts it.

Bug: 1123705
Test: Ran locally.
Change-Id: I72806731f778aadca07ff73ba2cc0a08abb59141
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2413612
Commit-Queue: Hidehiko Abe <hidehiko@chromium.org>
Reviewed-by: Jun Mukai <mukai@chromium.org>
Reviewed-by: Yuichiro Hanada <yhanada@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807839}

Add content::RunAllTasksUntilIdle() to resolve the test case
ChromeLauncherControllerWithArcTest.ArcAppPinCrossPlatformWorkflow
flaky issue.

BUG=1083331

Change-Id: Ib142e74c194625f8a180a34bc4f755b01b3c4e2b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2409428
Commit-Queue: Nancy Wang <nancylingwang@chromium.org>
Reviewed-by: Nancy Wang <nancylingwang@chromium.org>
Reviewed-by: Long Cheng <lgcheng@google.com>
Cr-Commit-Position: refs/heads/master@{#807838}

set_sources_assignment_filter() is considered as a mis-feature
of gn (as it makes it difficult to reason about the BUILD.gn
files individually).

Change code in //components/variations to check the platform before
adding plaform-specific source files to "sources" variable and clear
the filter to prevent regressions.

Bug: 1018739
Change-Id: Ib4c82f8dd2ede72ab9fcdb4ec193d7efa8c2bd3e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414232
Commit-Queue: Sylvain Defresne <sdefresne@chromium.org>
Auto-Submit: Sylvain Defresne <sdefresne@chromium.org>
Reviewed-by: Mark Pearson <mpearson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807837}

ComputedStyle::AccessAnimations() (and AccessTransitions) are used
to modify corresponding properties. But
ComputedStyle::AccessAnimations() uses inside
ComputedStyleBase::AnimationsInternal() which meant to be used for
constant access only. Due to copy-on-write semantics of
ComputedStyle it causes modifications to cloned ComputedStyle
affect source ComputedStyle instance.
Replacing call to AnimationsInternal() with copy-on-write-aware
MutableAnimationsInternal() eliminate this problem.

Change-Id: I67a0342151bbd4e0aee1fd8fbf16aa2a02a6310a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2410018
Commit-Queue: Alexander Semashko <ahest@yandex-team.ru>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807836}

Several fields are optional. Use the ? Mojo type specifier to
explicitly mark them as such.

Bug: 1039255
Change-Id: Ib5aa530059b90d0c41fe3288d8b9964c333e3cca
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2351831
Commit-Queue: Henrique Ferreiro <hferreiro@igalia.com>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807835}

This CL adds PhoneHubNotificationController, which creates and manages a
ChromeOS notification for each corresponding PhoneHub notification.

This basic implementation only creates a simple notification and
additional details will be added in following CLs:
  * Images and icons
  * Buttons and inline reply
  * Settings

BUG=1128091,1106937

Change-Id: Ifd57011c68e480f5956b628823ca461bb7ee39fb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2413531
Commit-Queue: Tim Song <tengs@chromium.org>
Reviewed-by: Tetsui Ohkubo <tetsui@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807834}

Now flaky on MacOS. Already disabled for most other platforms. Disable
for all.

TBR=skyostil@chromium.org

Bug: 1078405
Change-Id: Ib0212de28302de1581a63db55c2e6227856bed3f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414303Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807833}

The MIDIDispatcher ctor recently gained access to execution_context. Use
it to generate a TaskRunner when it is needed.

Since it is only needed in the ctor, remove task_runner_.

Change-Id: I7873fddd1ae815fd7ac909b3a5f9a49e257ef0c3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2409561Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org>
Commit-Queue: Johann Koenig <johannkoenig@google.com>
Cr-Commit-Position: refs/heads/master@{#807832}

The browsertests of google requests are moved from
policy_browsertests to a separate file.

Bug: 1128321
Change-Id: Ia64c8e4cefea56cedff9bd29c3baa390cc160867
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2410388
Commit-Queue: Swapnil Gupta <swapnilgupta@google.com>
Reviewed-by: Sergey Poromov <poromov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807831}

MojoLPM should add handles (DataPipeProducer/Consumers etc) directly to
its context, instead of attempting to ToProto convert these. As this is
consistent with HandleDataPipeRead/Write.

Bug: 1076336
Change-Id: Ia509064339724db82548ba24eebeb0bdfac39a2b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2351991Reviewed-by: Oksana Zhuravlova <oksamyt@chromium.org>
Commit-Queue: Clovis PJ <clovispj@google.com>
Cr-Commit-Position: refs/heads/master@{#807830}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/2ff41ff5..26d327a7

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

This change prolongs several Password Manager histograms.

Fixed: 1125827, 1125734, 1125733, 1125732, 1125730, 1125724, 1117137
Change-Id: Ib14848f0db5dd5f437e1b0dd9bd447990bbba8e8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414215Reviewed-by: Jesse Doherty <jwd@chromium.org>
Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org>
Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807828}

https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools.git/+log/e8ce4355ae1c..34ef0c3fdc8e

2020-09-16 rharrison@google.com Fix missed modification flagging (#3814)
2020-09-16 andreperezmaselco.developer@gmail.com spirv-fuzz: Use an irrelevant id for the unused components (#3810)
2020-09-16 stefanomil@google.com spirv-fuzz: Improvements to random number generation (#3809)
2020-09-16 greg@lunarg.com Add buffer oob check to bindless instrumentation (#3800)
2020-09-16 vasniktel@gmail.com spirv-fuzz: Remove CanFindOrCreateZeroConstant (#3807)

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/spirv-tools-chromium-autoroll
Please CC radial-bots+chrome-roll@google.com,jmadill@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_angle_vk32_deqp_rel_ng;luci.chromium.try:android_angle_vk32_rel_ng;luci.chromium.try:android_angle_vk64_deqp_rel_ng;luci.chromium.try:android_angle_vk64_rel_ng;luci.chromium.try:linux_angle_deqp_rel_ng;luci.chromium.try:linux-angle-rel;luci.chromium.try:win-angle-rel-32;luci.chromium.try:win-angle-rel-64;luci.chromium.try:win-angle-deqp-rel-32;luci.chromium.try:win-angle-deqp-rel-64
Tbr: radial-bots+chrome-roll@google.com,jmadill@google.com
Change-Id: If070d9f97ec26f5bc06f6d4428d7642555e6cb90
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2415891Reviewed-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@{#807827}

https://chromium.googlesource.com/angle/angle.git/+log/3018d5e57091..0a8a3ea25b36

2020-09-17 courtneygo@google.com Vulkan: Skip nested pow test on NVIDIA, Windows
2020-09-17 timvp@google.com Vulkan: Use linkedShaderStages in GlslangGetShaderSpirvCode()
2020-09-17 jmadill@chromium.org GN: Fix CrOS build due to buggy "defines".
2020-09-17 timvp@google.com Vulkan: Match descriptor pool sizes to descriptor set layouts
2020-09-17 jmadill@chromium.org Test Runner: Fix dirty thread teardown.
2020-09-17 jmadill@chromium.org Run trace tests against Vulkan Mock ICD.
2020-09-16 jmadill@chromium.org GN: Fix missing pkg_config import in GL back-end.
2020-09-16 capn@google.com Validate GLSL attribute location range
2020-09-16 jmadill@chromium.org Test Runner: Handle GTest sharding args.
2020-09-16 syoussefi@chromium.org Vulkan: Change VK suffix to Vk
2020-09-16 cclao@google.com Vulkan: Move mAttachedColorBufferMask to FramebufferState
2020-09-16 syoussefi@chromium.org Change renderbuffer width/height/sample types to GLsizei
2020-09-16 jmadill@chromium.org Show file in internal errors.
2020-09-16 cnorthrop@google.com EGL: Add another config for Mali
2020-09-16 ianelliott@google.com Vulkan: Disable BlitStencilWithFlip test on Win
2020-09-16 jmadill@chromium.org GN: Componentize GL back-end.
2020-09-16 lexa.knyazev@gmail.com Vulkan: Fix blendEnable-02023 VU

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 jmadill@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:1110800,chromium:1127866,chromium:1128064,chromium:1129075
Tbr: jmadill@google.com
Test: Test:Test: Test: VulkanDescriptorSetTestTest: Test: angle_end2end_testsTest: Test: local GN CrOS build
Change-Id: Idb0889596d09481056523072965daf21db685c77
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414659Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Reviewed-by: Jamie Madill <jmadill@chromium.org>
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#807826}

Bug: 984693
Test: video_decode_accelerator_tests
Change-Id: Idee4e53a555168433e7e138ba2fafd1cff649cbd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2409726
Auto-Submit: Hirokazu Honda <hiroh@chromium.org>
Reviewed-by: Miguel Casas <mcasas@chromium.org>
Commit-Queue: Hirokazu Honda <hiroh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807825}

These tests were created with expectations for the normal bots, not the
disable-layout-ng bot. FlexNG differs from legacy flex in at least one
test in each file, so disable-layout-ng needs an expected.txt for each
test.

Change-Id: Ide3a709fb1e262ce0b072018a6c8b1a4d8d647d9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414676
Commit-Queue: Christian Biesinger <cbiesinger@chromium.org>
Auto-Submit: David Grogan <dgrogan@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807824}

After going through the sync consent flow from SyncPromoPreference, this
preference should be hidden. Keeping the SyncPromoPreference when
SigninPromoController was not null was preventing that from happening.

Bug: 1126074
Change-Id: Ibad0838ec2594b1c6825561df4d6392359fe7c9c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2400418Reviewed-by: Tanmoy Mollik <triploblastic@chromium.org>
Reviewed-by: Alice Wang <aliceywang@chromium.org>
Reviewed-by: Marc Treib <treib@chromium.org>
Commit-Queue: Tanmoy Mollik <triploblastic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807823}

rotates the screen.

Update the ViewRevealingVerticalPanHandler's base view height when the
BVC transitions to a different size. Keep track of whether the BVC is
positioned at the bottom of the screen and reposition it on rotation if
needed.

Bug: 1123729, 1127604
Change-Id: I8fb2ee0f531204ff3788845af8f32b515f101931
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414393Reviewed-by: Gauthier Ambard <gambard@chromium.org>
Commit-Queue: Roberto Moura <mouraroberto@google.com>
Cr-Commit-Position: refs/heads/master@{#807822}

Timeout on multiple builders. Not able to identify culprit. Disabling.

TBR=ellyjones@chromium.org

Bug: 1129313
Change-Id: I9f9bb6f3c3e55499b4d8709d790886b8bfa8d5fb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414195Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807821}

https://pdfium.googlesource.com/pdfium.git/+log/5b4eaf71f78b..837fe726e639

2020-09-16 tsepez@chromium.org Rewrite some loops in CFXA_FMParser.
2020-09-16 tsepez@chromium.org Introduce PDFFuzzerPublic::MaybeForceGCAndPump().

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

Roll Chrome Mac PGO profile from chrome-mac-master-1600310646-24416ad728deecf44e4a88c788126e2edffee2b4.profdata to chrome-mac-master-1600322062-3a48015e01b1446b1d53601d43c9f7d995fa4dd3.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-mac-chromium
Please CC jeffyoon@google.com,liaoyuke@google.com,sebmarchand+pgo_roller@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: jeffyoon@google.com,liaoyuke@google.com,sebmarchand+pgo_roller@google.com
Change-Id: I12b0574462366330741b5a92e84bae61fd9de06e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2415892Reviewed-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@{#807819}

This reverts commit 7cfe51d0.

Reason for revert: Suspected as the reason for Canary build failures.

Original change's description:
> [WebLayer] Enable WebLayer in split on canary
> 
> This enables WebLayer in a split in WebView bundles in canary. I tested
> on L-Q and ran all instrumentation tests on P with this setup.
> 
> Bug: 1105096
> Change-Id: I517bce4109531108a4fb3af64a87aa1f5d2a91bb
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2412705
> Reviewed-by: Scott Violet <sky@chromium.org>
> Commit-Queue: Clark DuVall <cduvall@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#807252}

TBR=sky@chromium.org,cduvall@chromium.org

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

Bug: 1105096, 1129288
Change-Id: I040fa6a2cd4dcfbfd006a49b32ec952625557132
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414258Reviewed-by: Benoit L <lizeb@chromium.org>
Commit-Queue: Benoit L <lizeb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807818}

Describe lossy prefs and how to remove individual settings from
HostContentSettingsMap.

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

To reflect actual implementation

Bug: none
Change-Id: I7cdb669ffaa6aacf0b1442db49026aa8d8e26ff4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414034Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Commit-Queue: Roman Sorokin [CET] <rsorokin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807816}

Change-Id: I340d719227315722953ef8f73409c0ec61ac0624
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414069Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Reviewed-by: Pavol Marko <pmarko@chromium.org>
Commit-Queue: Omar Morsi <omorsi@google.com>
Cr-Commit-Position: refs/heads/master@{#807815}

This CL adds grid node highlight configs to the regular inspect tool
to make sure persistent grid overlays can be shown while inspecting.

Frontend CL: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2400498

Bug: 1109224
Change-Id: If0828bb67577136ceb01c7bee92480bee1f53be8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2400478Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Reviewed-by: Sigurd Schneider <sigurds@chromium.org>
Commit-Queue: Alex Rudenko <alexrudenko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807814}