GitLab

We don't have search available for now.

Change-Id: I7c363ead61f46af56c03d7f73f1f25e436517d09
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339283Reviewed-by: Tommy Steimel <steimel@chromium.org>
Reviewed-by: Esmael Elmoslimany <aee@chromium.org>
Commit-Queue: Becca Hughes <beccahughes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795199}

The CL that previously addressed this problem only allowed pressing
the toggle button to enable/disable reverse scrolling, when the entire
row can be clicked in order to enable/disable reverse scrolling
(except for the learn more link).

Fixed: 1109966
Change-Id: Ica6eb360f2ac22770ff130f57b4cae5e58df2000
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339603Reviewed-by: Regan Hsu <hsuregan@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Commit-Queue: Regan Hsu <hsuregan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795198}

Extend the following histograms:
- Memory.BackgroundTask.Browser.PrivateSwapFootprint.*
- Memory.BackgroundTask.Browser.SharedMemoryFootprint.*
- Memory.BackgroundTask.OfflinePrefetch.Browser.PrivateSwapFootprint.*
- Memory.BackgroundTask.OfflinePrefetch.Browser.ResidentSet.*
- Memory.BackgroundTask.OfflinePrefetch.Browser.SharedMemoryFootprint.*

Bug: 1112399, 1112400, 1112401, 1112402, 1112403
Change-Id: Ifd0c20215f60fe76a092458e28f7cb02f1d71a0d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339758Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Xi Han <hanxi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795197}

https://skia.googlesource.com/skia.git/+log/e7b08e4876fb..4c97814f3adc

2020-08-05 brianosman@google.com Fix SKP serialization when SK_DISABLE_EFFECT_SERIALIZATION is defined
2020-08-05 scroggo@google.com Reland "Add an SkImageGenerator that uses NDK APIs"
2020-08-05 jmbetancourt@google.com get rid of unused include
2020-08-05 robertphillips@google.com Simplify GrSmallPathRenderer::visitProxies
2020-08-05 mtklein@google.com remove overdrawcolorfilter_runtime
2020-08-05 adlai@google.com Remove staging API for SkImage::makeWithFilter
2020-08-05 adlai@google.com Migrate MakeFromAdoptedTexture to GrRecordingContext
2020-08-05 mtklein@google.com add a global may-we-JIT flag
2020-08-05 egdaniel@google.com Don't allow transferring between special queues in vulkan in surface flush.
2020-08-05 johnstiles@google.com Fix out-of-bounds array access discovered by fuzzer.
2020-08-05 nifong@google.com Publish version 0.17.3
2020-08-05 scroggo@google.com Revert "Add an SkImageGenerator that uses NDK APIs"
2020-08-05 bungeman@google.com Use SkUniqueCFRef with CTTypesetterCreateLine
2020-08-05 scroggo@google.com Add an SkImageGenerator that uses NDK APIs

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

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

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

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Cq-Do-Not-Cancel-Tryjobs: true
Bug: chromium:1108040
Tbr: herb@google.com
Change-Id: Iead65fcd7be9143871ca224de4c3207347268cac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339653Reviewed-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@{#795196}

3d8daa2 Fix sym-upload-v2 whitespace in filenames.

BUG=1021742
R=mark@chromium.org, nbilling@google.com

Change-Id: Iafb23a63ee968024c6de7d5b636724384a6664af
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339549
Commit-Queue: Michael Moss <mmoss@chromium.org>
Commit-Queue: Mark Mentovai <mark@chromium.org>
Auto-Submit: Michael Moss <mmoss@chromium.org>
Reviewed-by: Mark Mentovai <mark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795195}

Bug: b/162891584
Test: manual
Change-Id: I912e7942787b0d2994e85a1570eb5bb1a0171578
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2337681Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Commit-Queue: Tao Wu <wutao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795194}

Rename font icon name so it matches go/icons#icon=font_download

Bug: 1112552
Change-Id: I7f3e5d9e70cc67e8fbf7ebfc037a3bea359ac31c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339823Reviewed-by: Evan Stade <estade@chromium.org>
Commit-Queue: Olivier Yiptong <oyiptong@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795193}

This is part of a larger effort, started in Chrome CL
2297920, to separate GPU-backed GrDirectContexts from
DDL-backed GrRecordingContexts and remove the ambiguous
GrContext class.

Bug: skia:104662
Change-Id: I02b437b5925a4b6098c9bb720eb891ca3bb1c1fd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2335812Reviewed-by: Robert Phillips <robertphillips@google.com>
Reviewed-by: Khushal <khushalsagar@chromium.org>
Commit-Queue: Adlai Holler <adlai@google.com>
Cr-Commit-Position: refs/heads/master@{#795192}

This is needed in order to enable support for extension-based typed
tracing events. For more information, see
https://perfetto.dev/docs/design-docs/extensions

Change-Id: I43bd82ee1c94cf7ae5be0a1fd7db4104cf8ece6a
Bug: 161696674
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2332180Reviewed-by: Bruce Dawson <brucedawson@chromium.org>
Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Reviewed-by: Eric Seckler <eseckler@chromium.org>
Commit-Queue: Andrew Shulaev <ddrone@google.com>
Cr-Commit-Position: refs/heads/master@{#795191}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/bd6505349012..fb9c1110ef14

2020-08-05 bpastene@chromium.org Revert "ResultDB reporting for bot-triggered builds"
2020-08-05 nguyenmh@google.com Add a newline between commit messages

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

The first intended use-case of this is use in the CompositingAssignments
update step for overlap testing.

Bug: 1100711

Change-Id: I75e69d0633187fdc80eec71a74811453c6875cef
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339384Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795189}

PEImage and PeImageReader are similar classes with slightly different
behaviors. This change updates the comments to clarify how they differ.

Change-Id: Id09868324b93d5a44731f778fb3f7684ca77736f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2336303Reviewed-by: Will Harris <wfh@chromium.org>
Commit-Queue: Bruce Dawson <brucedawson@chromium.org>
Auto-Submit: Bruce Dawson <brucedawson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795188}

Test flakes on TSan.

TBR=rogerta@chromium.org

Bug: 1113376
Change-Id: I6f0b868e85c86c7994ae8e3eedb67869cb165c20
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2340101Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: Roger Tawa <rogerta@chromium.org>
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795187}

Use consistent output dir detection from constants. See
build/android/list_java_targets.py as an example.

Bug: 1092528
Change-Id: I6392293a2b036ae419e1dc062e8c6f573fb7640d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339763
Commit-Queue: Peter Wen <wnwen@chromium.org>
Commit-Queue: Sam Maier <smaier@chromium.org>
Auto-Submit: Peter Wen <wnwen@chromium.org>
Reviewed-by: Sam Maier <smaier@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795186}

Using wpt-import in Chromium 2914c6e6.
With Chromium commits locally applied on WPT:
dfdc7fe9 "[WPT] Errors caught/reported for importScripts()"
27a0731b "Origin isolation: add WPTs for contentDocument/frameElement"


Note to sheriffs: This CL imports external tests and adds
expectations for those tests; if this CL is large and causes
a few new failures, please fix the failures by adding new
lines to TestExpectations rather than reverting. See:
https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md

Directory owners for changes in this CL:
foolip@chromium.org, lpz@chromium.org, robertma@chromium.org:
  external/wpt/tools

NOAUTOREVERT=true
TBR=smcgruer@google.com

No-Export: true
Change-Id: I42b165b6e527a04854b0e257043c76a3c7ab3438
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339222Reviewed-by: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#795185}

As part of UX discussions, the filter list is now a list of nodes that
can be used in the filter. Whether a node is actually in the filter or
not is toggled by its checkbox. "Select all" and "Deselect all" buttons
have been added to make checkbox manipulation easier.

A node enters the filter list through the filter input or the node
details panel. It always enters in the checked state. A node exits the
filter list through the user manually clicking the x beside it. Once in
the filter list, the node's filter visibility can be toggled by a
checkbox beside it or through the node details panel.

Checkbox information is also encoded in the URL.

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

Many times, high data cache miss rates and data TLB miss rates have
root causes far removed from the function where the miss is actually
occurring. Having callstacks, helps us understand data access
and allocation patterns with poor locality.

To set sampling intervals, I followed the pattern used for cycles flat
vs. callgraph, where the latter has a 4x larger sampling interval.

For DTLB miss cycles, we are currently collecting about 2x more samples
per report than for other events, so I increased the sampling interval
by 2 * 4 = 8.

For LLC misses, we are collecting about 2x less samples per report than
for other events, so I increased the sampling interval by 2.5x, more
than 4 / 2, to be a bit conservative.

Also increased samping interval for iTLB misses by 1.5x, as they are
at the upper end of acceptable samples / report.

BUG=b:162350244

Change-Id: Idd7d29d2e7535f3ddf99470d1980da14fccdcff9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339827Reviewed-by: George Burgess <gbiv@chromium.org>
Reviewed-by: Gabriel Marin <gmx@chromium.org>
Commit-Queue: Gabriel Marin <gmx@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795183}

This defines a handful of MultiToken<> variants (and their mojom traits)
that will be used in renderer code, as well as in renderer to browser IPC.

BUG=1085129, 1096617

Change-Id: I548ecfe2824d2a8e78c0af8a197abebf2ab6fc41
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2337104
Commit-Queue: Chris Hamilton <chrisha@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795182}

Fix a couple instances of "master". As of this CL, the following terms
no longer appear in //ash -- master, slave, white_?list, black_?list.

Bug: 1097644
Change-Id: I02f59e12cf587c97c7c12f88f00fac2a468e3cbd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339926
Commit-Queue: James Cook <jamescook@chromium.org>
Commit-Queue: Xiyuan Xia <xiyuan@chromium.org>
Auto-Submit: James Cook <jamescook@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795181}

Suspecting that the test was flaking because of
https://crbug.com/1111525, which is now fixed.

Bug: 1111530
Change-Id: I5e68c2fc23155ad3eac608fa5d1b167720b665c3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339814
Commit-Queue: Lei Zhang <thestig@chromium.org>
Auto-Submit: dpapad <dpapad@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795180}

Original patch: crrev.com/c/2319538
First reland: crrev.com/c/2333648

Changes in this patch (https://chromium-review.googlesource.com/c/chromium/src/+/2336301/1..10)
1. Fixed use-after-free of ContainingBlockScope. Similar to the first
   revert, the issue was because it was allocated in
   PaintInvalidatorContext which is in a vector replacing the real stack.
   ContainingBlockScope::outer_ might point to an invalid address if the
   vector was reallocated. Now use std::unique_ptr<ContainingBlockScope>
   in PaintInvalidatorContext. This increases the cost a bit but not much
   because ContainingBlockScope is created for LayoutBlockFlow with
   inline children only.
2. Rebased on crrev.com/c/2335647 which avoids memory regression caused
   by the original CL, and enables LayoutShiftTracker to use more
   accurate previous rects for shifted boxes.
3. Simplify LayoutShiftTracker::ReattachHook[::Scope].

Bug: 1108622
Change-Id: I7b4a85675483f7006ade8925c159a7882f08ec27
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2336301Reviewed-by: Steve Kobes <skobes@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795179}

* The C++ side of the Chrome cleaner child immediately condenses the
  received states to the ones that are relevant for the child. This
  reduces complexity on the JS side and simplifies recording metrics.

Bug: 1087263
Change-Id: I4e2f8400be863c7a7c0c83e35ce2ba4856372c62
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2328665Reviewed-by: Esmael Elmoslimany <aee@chromium.org>
Commit-Queue: Rainhard Findling <rainhard@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795178}

Bug: 1113367
Change-Id: If85efce44c5b84c41949c80534dc6a40d418016d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339548Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Commit-Queue: Roger Tawa <rogerta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795177}

Roll Chrome Win32 PGO profile from chrome-win32-master-1596635955-2b1d31dacdbaf52cf854414e21cd977f1d32db43.profdata to chrome-win32-master-1596643173-1c5e3b62f80a4dd3f16924cb334ea677bc923f5e.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 sebmarchand+pgo_roller@google.com,jeffyoon@google.com,liaoyuke@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: chrome/try:win-chrome
Tbr: sebmarchand+pgo_roller@google.com,jeffyoon@google.com,liaoyuke@google.com
Change-Id: I13d20081550abb91d26374dded504b023ff97b8b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339541Reviewed-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@{#795176}

In order for the global media controls dialog to display the currently
used audio device in the UI the renderer needs to report what device is
in use. Currently, MediaWebContentsObserver will receive messages when
the output device is switched. However, the device id reported by the
renderer is hashed so that it may be only used on one origin.

This change has the MediaWebContentsObserver translate the device ID
before passing it off to the MediaSessionControllersManager.

Bug: 1111432
Change-Id: I11d161ff5f89525b4c465f01a779bdd30e31c823
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2331330
Commit-Queue: Noah Rose Ledesma <noahrose@google.com>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Reviewed-by: Tommy Steimel <steimel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795175}

https://pdfium.googlesource.com/pdfium.git/+log/fa9a15cb008b..fe8e758b920c

2020-08-05 thestig@chromium.org Rewrite OS_LINUX define.
2020-08-05 thestig@chromium.org Rewrite is_linux GN flag.
2020-08-05 tsepez@chromium.org Rename CXFA_NodeHelper to CFXJSE_NodeHelper and move to fxjs/
2020-08-05 thestig@chromium.org Roll tools/clang/ 6cbea33c9..1078c4141 (10 commits)
2020-08-04 thestig@chromium.org Use |kAA| instead of "AA" string.
2020-08-04 thestig@chromium.org Remove some dead CPDF_FormControl code.
2020-08-04 thestig@chromium.org Roll third_party/zlib/ f87c8e288..7492de9a5 (3 commits)

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: chromium:1110266
Tbr: pdfium-deps-rolls@chromium.org
Change-Id: I857a1b9d415c8bd425194f933c82e65081afe49e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2338923Reviewed-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@{#795174}

This change makes Trusted Type policy enforcement to Perfect types
(i.e. `require-trusted-types-for 'script'; trusted-types;`) by
default for WebUI (while still keeping report-only).

This means WebUI will not be able to use unsafe APIs by default (e.g.
innerHTML, document.write, etc). However, I have removed Trusted
Types CSP from a pages where it does not support Trusted Types yet
(e.g. Polymer 3).

This change will not make any observable changes, as report-only CSP
would only log console error when it detects Trusted Types violation.

Bug: 41905
Change-Id: Ib9d6eae53b600123c1837d2cdc56269c14a8d00f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2234238
Commit-Queue: Jun Kokatsu <Jun.Kokatsu@microsoft.com>
Reviewed-by: Nasko Oskov <nasko@chromium.org>
Reviewed-by: dpapad <dpapad@chromium.org>
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Reviewed-by: Tommy Steimel <steimel@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: enne <enne@chromium.org>
Reviewed-by: oysteine <oysteine@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Reviewed-by: Charlie Harrison <csharrison@chromium.org>
Reviewed-by: Tommy Li <tommycli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795173}

The current implemnetation of GetMediaDeviceIDFroHMAC accepts a
blink::mojom::MediaStreamType to distinguish between audio and video
devices. However, it is not able to distinguish between audio input and
output. Currently, this method will assume input.

In order to allow this method to work with audio output devices this
change introduces an overload that accepts a blink::MediaDeviceType
instead of a stream type.

Bug: 1111585
Change-Id: Ie7111665f8cd3d24a360bff28d2da56c7ddfaacb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2330741
Commit-Queue: Noah Rose Ledesma <noahrose@google.com>
Reviewed-by: John Rummell <jrummell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795172}

Bug: 1113284
Change-Id: I63092930726af55e45b1878850de540a09d9ad69
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339700
Commit-Queue: Dan H <harringtond@chromium.org>
Auto-Submit: Dan H <harringtond@chromium.org>
Reviewed-by: Justin DeWitt <dewittj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795171}

See attached bug for rationale and example screenshots.

We went from only making the change on Windows to making it on all
platforms because the difference isn't jarring but makes a positive
change in readability in almost all cases while maintaining the correct
font height for the badge.

Bug: 1111648
Change-Id: Ife6f126238489f11ead564ddf8f123de100a9d59
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2331296Reviewed-by: Peter Boström <pbos@chromium.org>
Commit-Queue: Dana Fried <dfried@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795170}

This CL introduces a new Finch flag, SafeBrowsingRemoveCookies, which
controls whether certain communications with Safe Browsing to attach
cookies. This was previously being shared with the
SafeBrowsingSeparateNetworkContexts Finch flag, which was misleading.

Bug: 1049833
Change-Id: If5f375fb146a1afe5669fc22f5b863bcfdd096c3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2337253Reviewed-by: Xinghui Lu <xinghuilu@chromium.org>
Commit-Queue: Daniel Rubery <drubery@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795169}

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/fuchsia-aemu-chromium-autoroll
Please CC chonggu@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

Tbr: chonggu@google.com
Change-Id: I8cac684b50d2ed3d2ba61cbc75ca2e67c0f3ea2a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339938Reviewed-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@{#795168}

This is so WebLayer can use it to support NoStatePrefetch.

Bug: 1096088
Change-Id: If0986e4e2eb43960bd19c4d43b1272c1803dfd1a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2336082Reviewed-by: Kevin McNee <mcnee@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Commit-Queue: Mugdha Lakhani <nator@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795167}

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

Bug: 1112872
Change-Id: I387fb3f0f7d96b0dc92cd5494668b29735d870e0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339925
Auto-Submit: Fred Mello <fredmello@chromium.org>
Reviewed-by: Ian Vollick <vollick@chromium.org>
Commit-Queue: Ian Vollick <vollick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795166}

These will not actually be executed, but should be isolated, which is
useful for the testing team.

Bug: 1106083
Change-Id: Ie9094bf7eaa70dd0a130ccb747c7f64d8f5bdffd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339921
Auto-Submit: Stephen Martinis <martiniss@chromium.org>
Reviewed-by: Erik Staab <estaab@chromium.org>
Commit-Queue: Erik Staab <estaab@chromium.org>
Commit-Queue: Stephen Martinis <martiniss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795165}

There should be no behaviour change.

Change-Id: I972509c2ce8e28dcd6542b0b9531d1c0a961dd1f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2244971
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Auto-Submit: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795164}

This reverts commit 77cd5d73.

Reason for revert: pinpoint shows only regressions.

Original change's description:
> heap: Minor marking tweaks
> 
> 1) Traces show that it can take a relatively long time before Oilpan
>    starts flushing v8 references (e.g. ~10 steps spent just on the
>    bailout worklist). This CL moves v8 references flushing before
>    processing of the bailout worklist.
> 2) Traces also show that a shorter duration for the first marking step
>    can suffice.
> 
> Bug: 986235
> Change-Id: If7bad026e91f1fdf1899035bda049834e7bffab5
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339356
> Commit-Queue: Omer Katz <omerkatz@chromium.org>
> Commit-Queue: Anton Bikineev <bikineev@chromium.org>
> Auto-Submit: Omer Katz <omerkatz@chromium.org>
> Reviewed-by: Anton Bikineev <bikineev@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#795059}

TBR=bikineev@chromium.org,omerkatz@chromium.org

Change-Id: I36bbadafcfe91a4f725537975ec06b1a9ac10e0a
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 986235
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2340040Reviewed-by: Omer Katz <omerkatz@chromium.org>
Commit-Queue: Omer Katz <omerkatz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795163}

Currently, the identity internals debugging page does not display the
account ID that the token belongs to. This information may be useful to
list for debugging cases where multiple accounts are involved.

This CL adds the account ID for each cached token to the Identity
Internals page.

Bug: None
Change-Id: I704748f2521cb34c96ed7ccade0fdac6e99d01dd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2333545
Commit-Queue: William Lin <williamlin@google.com>
Reviewed-by: Alex Ilin <alexilin@chromium.org>
Reviewed-by: David Roger <droger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795162}

Targets the new driver and Windows versions for the GPU Windows 10
Quadro P400 machines in preparation for an upcoming upgrade.

Bug: 1085489
Change-Id: I4dffa9fe085fa96dc3ad3e73bb981314195f98e4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2340000
Commit-Queue: Brian Sheedy <bsheedy@chromium.org>
Commit-Queue: Yuly Novikov <ynovikov@chromium.org>
Auto-Submit: Brian Sheedy <bsheedy@chromium.org>
Reviewed-by: Yuly Novikov <ynovikov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795161}

Design doc go/chrome-sync-merchant-offers.

Start with implementing only the protobuf changes since they are in
kind of a finalized state and this CL can unblock impl on GMSCore.

Bug: 1112095
Change-Id: I27705f467424d614c80b4dd03ae5207e112e4c32
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2333870
Commit-Queue: Siyu An <siyua@chromium.org>
Reviewed-by: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#795160}