GitLab

Clean up some stragglers that called DeleteFile() without the base::
prefix, but still got the right function with argument-dependent lookup.

Bug: 1009837
Change-Id: I6a11c92cc9f928830ea772f7a998b4c23bf939fd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2313043Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#790998}

The builder should use latest version of Xcode 12.

Also carried a luci-scheduler.cfg format change in this CL, from a
recent generator update.

Bug: 1108147
Change-Id: Ibd0ceb9966c7974fe8d01e96be2e8f8a5a9d8b95
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2311722
Commit-Queue: Zhaoyang Li <zhaoyangli@chromium.org>
Reviewed-by: Garrett Beaty <gbeaty@chromium.org>
Cr-Commit-Position: refs/heads/master@{#790997}

Provide test coverage for the following scenarios in the
chrome.certificateProvider extensions API:
* empty certificate chain;
* empty algorithm list;
* an extension subscribing to both legacy and non-legacy
  events simultaneously.

Bug: 1067683
Change-Id: I074967716aba5c91b6b6e946345f84a4767bd722
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2252187
Commit-Queue: Maksim Ivanov <emaxx@chromium.org>
Reviewed-by: Fabian Sommer <fabiansommer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#790996}

If the calls to MatchResult::Finish are not correct, we can end up
rules that appear to exist in the wrong origin.

In CollectPseudoRulesForElement, there is an option _not_ match
UA/User rules, but it didn't call the Finish* functions for
skipped origins.

In PseudoStyleForElementInternal, there is a call to
FinishAddingAuthorRulesForTreeScope with _may_ take place without the
other finishers being called first. Since no further rules are added
anyway, we can simply remove this call.

Change-Id: I81e54b267eba6098d9037d2d403047bc3da25dfa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2310338Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org>
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/master@{#790995}

Remove //components* from allowlist.

Bug: 1082904
Change-Id: Icf4100c9e9e2a4ea7c843ea6d8cfa148b1fa7b6a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2314298
Commit-Queue: Peter Wen <wnwen@chromium.org>
Auto-Submit: Peter Wen <wnwen@chromium.org>
Reviewed-by: Calder Kitagawa <ckitagawa@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/master@{#790994}

Updates the HARMFUL_ACCESS() macro to use EXPECT_DEATH_IF_SUPPORTED,
which is a no-op on platforms where EXPECT_DEATH is unsupported. This
effectively disables death tests when run on iOS, allowing
base_unittests to pass when run under ASAN.

BUG=None

Change-Id: I700210e3a96e3cf8b10c786184146c4269bc3f21
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2313117Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Rohit Rao <rohitrao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#790993}

TBR=thibaudm@chromium.org

Bug: 1107923
Change-Id: I73a80f3986a8b4ee7e655c42057a6d47c014a737
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2313960Reviewed-by: James MacLean <wjmaclean@chromium.org>
Commit-Queue: James MacLean <wjmaclean@chromium.org>
Cr-Commit-Position: refs/heads/master@{#790992}

This shows a snackbar when the user interacts with the paint preview
player on startup.

It also implements the 'frustration detector'. It triggers when the user
taps in areas that are not links, or longpresses. This will lead to
showing the snackbar again.

Bug: 1106430
Change-Id: I3aa94f055a730630058bd204d0810e81668b7a36
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2302938
Commit-Queue: Mehran Mahmoudi <mahmoudi@chromium.org>
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Reviewed-by: Calder Kitagawa <ckitagawa@chromium.org>
Reviewed-by: Fred Mello <fredmello@chromium.org>
Cr-Commit-Position: refs/heads/master@{#790991}

https://dawn.googlesource.com/tint.git/+log/747e80a9b369..433670b576c5

$ git log 747e80a9b..433670b57 --date=short --no-merges --format='%ad %ae %s'
2020-07-22 rharrison Add usage of main from chromium when part of a chromium build
2020-07-22 dsinclair Add return to simple test
2020-07-22 sarahmashay [validation] Add a disabled test for assignment statement.
2020-07-22 dneto [spirv-reader] Support OpAny, OpAll, OpIsInf, OpIsNan
2020-07-21 dsinclair [spirv-writer] Emit select intrinsic.
2020-07-21 dsinclair Add type determination for the select intrinsic.
2020-07-21 dneto [spirv-reader] Add README.md
2020-07-21 dneto [spirv-reader] Support function call returning void
2020-07-21 dj2 [hlsl-writer] Add assignment statement.
2020-07-21 dj2 [hlsl-writer] Add switch statement support
2020-07-21 dj2 [hlsl-writer] Emit case statements.
2020-07-21 dj2 [hlsl-writer] Emit unary operators.
2020-07-21 dj2 [hlsl-writer] Emit break, return and continue.
2020-07-21 dsinclair [hlsl-writer] Add binary operator emission.
2020-07-21 dsinclair Parse void function call.
2020-07-21 dsinclair [hlsl-writer] Add emission of identifiers
2020-07-21 dj2 Emit call statements from the various backends.
2020-07-21 dj2 Type determine the call statement.
2020-07-21 dj2 Add a call ast statement.
2020-07-21 dneto [spirv-reader] Support select over scalars and vectors
2020-07-20 dneto Add missing Doxygen comments on two methods.
2020-07-20 dneto [spirv-reader] Support function calls, except returning void
2020-07-20 dsinclair [hlsl-writer] Scaffold the HLSL backend.
2020-07-20 dsinclair [msl-writer] Emit storage buffers.
2020-07-20 dsinclair [msl-writer] Add import emission.

Created with:
  roll-dep src/third_party/tint/src

Bug=tint:123

Change-Id: I5ba160dfbd1fabd4390a55b833bcfd6b255f7530
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2314116
Commit-Queue: Ryan Harrison <rharrison@chromium.org>
Commit-Queue: Kai Ninomiya <kainino@chromium.org>
Auto-Submit: Ryan Harrison <rharrison@chromium.org>
Reviewed-by: Kai Ninomiya <kainino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#790990}

Change-Id: I4595a84b9fbf5421e43311005d1a7aa634f66ec9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2309006
Auto-Submit: Takumi Fujimoto <takumif@chromium.org>
Reviewed-by: Brandon Tolsch <btolsch@chromium.org>
Commit-Queue: Brandon Tolsch <btolsch@chromium.org>
Cr-Commit-Position: refs/heads/master@{#790989}

Using wpt-import in Chromium 85f04135.
With Chromium commits locally applied on WPT:
a02f2df5 "Implement Storage Access commands for TestDriver"
9c2ef271 "[COOP report] Add support for report-only"
e0092d05 "Reland "[COOP] access reporting [5/N] Plumb report type.""


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=robertma@google.com

No-Export: true
Change-Id: I34cd10a9c6ea32fec940c57e94327d96525a1c9a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2314136Reviewed-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@{#790988}

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

1000 contexts were causing time out in Linux and Mac OS bots. Lowering
the count to 500.

Bug: 1092145
Change-Id: Iaee7b4b408e551236252b3b2f163240249c5697b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2309805Reviewed-by: Raymond Toy <rtoy@chromium.org>
Commit-Queue: Hongchan Choi <hongchan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#790986}

This CL defines WebContentsDelegate::ShouldPinTopControlsToContentTop(),
which embedders can use to tell BrowserControlsOffsetManager to only
show the top browser controls if the page is scrolled to the top.

WebLayer's Browser#setTopView pinToContentTop parameter is hooked up to
this new method.

Bug: 1069498
Change-Id: I7a19656c0ee3219936c3279bfb89591b1f3abb56
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2284138
Commit-Queue: Robbie McElrath <rmcelrath@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Bo <boliu@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#790985}

Makes use of the clipping api for ink drop highlights/ripples.

ToggleButton: Ink-drop layers were always forwarded to the thumb view,
so the InkDropMask was unnecessary before.

FrameButton: InkDropMask relies a bit on the frame button internals, so
create a custom highlight path generator.

MediaButton: Used CircularMask which can be converted to a CircularPath.

Test: manual
Bug: 1056490
Change-Id: I16e4b853158136eee2ffba1a2de2b495437896f1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2310875Reviewed-by: Peter Boström <pbos@chromium.org>
Commit-Queue: Sammie Quon <sammiequon@chromium.org>
Cr-Commit-Position: refs/heads/master@{#790984}

This CL removes GLRendererCopier for SkiaRenderer, as we use skia for
readback on all platforms.

Bug: 1044594
Change-Id: I51ee6f36c87a0598a5aa7dd9d9dc1c9ca1417d73
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2307651Reviewed-by: Jonathan Backer <backer@chromium.org>
Commit-Queue: Vasiliy Telezhnikov <vasilyt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#790983}

Converts ModelAddedCallback and ModelRemovedCallback to base::Repeating
Callbacks to match their usage. Removes the corresponding entry from
PRESUBMIT.py

Bug: 1007635
Change-Id: I10393eea74ff16ba86f5e7118765557fca770028
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2303877
Commit-Queue: Alexander Cooper <alcooper@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#790982}

ChromeOS devices are usually lower powered where
making use of the hardware based video decoders
helps a lot with battery life.  ChromeOS SOC's
are closer to those of Android, so choose the
same cutoff point.

Bug: 684792
Change-Id: I426e0dedaf210b0d7b7c387ddacebdaa78eb363b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2303605Reviewed-by: Will Cassella <cassew@google.com>
Reviewed-by: Miguel Casas <mcasas@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Commit-Queue: Fritz Koenig <frkoenig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#790981}

The node.fidl interface is expected to change over the next year, so add
a default case to prevent against future SDK roll breakages.

Test: AccessibilityBridgeTest and AXTreeConverterTest
Bug: 1108467
Change-Id: I63612fcdd88f169279a2cad464be97b17a8e0369
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2314040Reviewed-by: Kevin Marshall <kmarshall@chromium.org>
Commit-Queue: Sharon Yang <yangsharon@chromium.org>
Cr-Commit-Position: refs/heads/master@{#790980}

I forgot to handle CascadeOrigin::kNone, which means the subsequent
call to priority.GetPosition() would always return zero, and we would
access the wrong value (and possibly crash).

Handle that case, and add a more detailed test which verifies each
origin.

Fixed: 1108019
Change-Id: I298c12ed56231b27f3ce505911db5e3fe0c2a16e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2310535Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org>
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/master@{#790979}

This reverts commit 539778cf.

Reason for revert: not enough HW capacity for more tests

Original change's description:
> Explicitly name webgl/2 conformance tests on Windows
> 
> These tests should be explicit about using ANGLE's d3d11 backend.
> 
> Bug: chromium:850252
> Change-Id: I0f3d348edf38f845efeb5ba9d2a70f38b662efbf
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2302413
> Reviewed-by: Jonah Ryan-Davis <jonahr@google.com>
> Reviewed-by: Kenneth Russell <kbr@chromium.org>
> Reviewed-by: Brian Sheedy <bsheedy@chromium.org>
> Commit-Queue: Jonah Ryan-Davis <jonahr@google.com>
> Cr-Commit-Position: refs/heads/master@{#790942}

TBR=ynovikov@chromium.org,kbr@chromium.org,bsheedy@chromium.org,jonahr@google.com

Change-Id: I0af5192a835a0094c468d000786ba6b5b3aec7f5
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: chromium:850252
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2314135Reviewed-by: Yuly Novikov <ynovikov@chromium.org>
Commit-Queue: Yuly Novikov <ynovikov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#790978}

Adding tests for zoom, fit, and rotate buttons.

Also fixing a small bug, where forceFit() was setting the icon to the
opposite of the desired type in the new toolbar (reproduce by opening
a PDF with #view=fit appended to the URL, with the new and old UI).

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

Add an EventHandler class to wrap calls to addEventListener and
removeEventListener. This makes the code more readable, by describing
semantically what is happening, and less complex, by automatically
removing old event listeners when the nodes in question change. In
addition, it eliminates the need to save bound pointers to functions to
eventually remove a listener.

AX-Relnotes: n/a.
Bug: None
Change-Id: I3994abbdd2f0da1ce06f0b51fbcf0634fa7eb2f7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2303458
Commit-Queue: Anastasia Helfinstein <anastasi@google.com>
Reviewed-by: Katie Dektar <katie@chromium.org>
Cr-Commit-Position: refs/heads/master@{#790976}

UpdateEngineAttemptResult does not match the AttemptResult enum in
update_engine. Add two missing values.

BUG=chromium:1108110
TEST=None

Change-Id: I756358dcfb1e167359e8e350c6a75155fd6f9937
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2311076Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Commit-Queue: Andrew Lassalle <andrewlassalle@chromium.org>
Cr-Commit-Position: refs/heads/master@{#790975}

Bug: 973650
Change-Id: I60375e858ac017b2b1ae96ad7bff8ce8aa6ffc97
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2310830
Commit-Queue: Matt Mueller <mattm@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#790974}

This CL implements function to run tests with ash-chrome

Bug: 1104318
Change-Id: Ic53d72c5f6152ed114ca360405e7b459d6b71f0c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2309804
Commit-Queue: Yuke Liao <liaoyuke@chromium.org>
Reviewed-by: Erik Chen <erikchen@chromium.org>
Reviewed-by: Sven Zheng <svenzheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#790973}

Previously, ClientControlledShellSurface always assumed that the client
uses default_device_scale_factor, and that the client converts x/y values
to DP before sending bounds information to the server. This means that
each pixel in the client buffer corresponds to one pixel on the display
only when the scale factor is set to the default_dsf.

This CL allows a client using the remote_shell protocol to disable using
default_dsf for scale cancellation. When it is disabled, remote_surfaces
for that client will use the display_scale_factor of the display on which
the surface is placed for scale cancellation.

In this CL, if use_default_scale_cancellation is disabled:
- ClientControlledShellSurface expects that clients will send all bounds
and buffers in display pixels instead of DP;
- When the device_scale_factor changes, the client will update the UI
accordingly to account for the new scale factor;
- When the device_scale_factor changes, the client will resize each of
its windows that are not fullscreen or maximized so that the bounds
change proportionally to the scale factor;
- When the client sends the first buffer of a different size (after
resizing the window), the newly added OnContentSizeChanged callback of
the SurfaceObserver interface is called, and the server will commit the
scale cancellation to use the new device_scale_factor.

BUG=b:141715728
TEST=manual with client-side changes; change the scale using
Ctrl-shift-(+/-) and expect scale cancellation to updated visually.

Change-Id: I06b2c47828af4d1d1923fdc4b6a82e5c41cd9766
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2255141
Commit-Queue: Prabir Pradhan <prabirmsp@chromium.org>
Auto-Submit: Prabir Pradhan <prabirmsp@chromium.org>
Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Cr-Commit-Position: refs/heads/master@{#790972}

This CL hooks UrlLoaderFactory into FtlSignalStrategy, as it will be
needed by multiple components inside FtlSignalStrategy.

This is split off from crrev.com/c/2293230, as that CL is blocked by
server rollout.

Bug: 1103416
Change-Id: I0efeb4468c066a8f7f2eb1dd35d1e20b2cca3366
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2310775
Commit-Queue: Yuwei Huang <yuweih@chromium.org>
Commit-Queue: Clark DuVall <cduvall@chromium.org>
Auto-Submit: Yuwei Huang <yuweih@chromium.org>
Reviewed-by: Clark DuVall <cduvall@chromium.org>
Reviewed-by: Joe Downing <joedow@chromium.org>
Cr-Commit-Position: refs/heads/master@{#790971}

This CL changes minimum version policy to work with Chrome OS version
(platform version) instead of Chrome version.
The policy updates Chrome OS and Chrome gets updated along with it,
hence it makes sense to use Chrome OS version here.
Also there are other policies that already work with Chrome OS version,
like Device​Target​Version​Prefix.

Bug: 1106736
Change-Id: I84c19254d800638f412df99c0bed67457a33e888
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2302009Reviewed-by: Roman Sorokin [CET] <rsorokin@chromium.org>
Reviewed-by: Pavol Marko <pmarko@chromium.org>
Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Commit-Queue: Saurabh Nijhara <snijhara@google.com>
Cr-Commit-Position: refs/heads/master@{#790970}

Roll ChromeOS Airmont AFDO profile from 86-4183.25-1595237914-benchmark-86.0.4207.0-r1 to 86-4183.25-1595237914-benchmark-86.0.4208.0-r1

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/cros-afdo-airmont-chromium
Please CC c-compiler-chrome@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: c-compiler-chrome@google.com
Change-Id: Id92efd3a917fec2bd609068b28c70d0585d15c3d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2314130Reviewed-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@{#790969}

Use AudioManagerAndroid, instead of CastAudioManagerAndroid on ATV.

The flag should only be used for dev and testing.

Bug: internal b/160753974
Test: Turn on the flag and verify in the log
Change-Id: Ie205d3f48d40d85b67272eeb143dbbc99d22bfe8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2311677Reviewed-by: Kenneth MacKay <kmackay@chromium.org>
Reviewed-by: Simeon Anfinrud <sanfin@chromium.org>
Commit-Queue: Yuchen Liu <yucliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#790968}

Bug: 1104858
Change-Id: I40e12d5922f33036953fcedad3a19faf42557c30
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2313296
Commit-Queue: Che-yu Wu <cheyuw@google.com>
Reviewed-by: Owen Min <zmin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#790967}

TBR=yosin@chromium.org

Bug: 982194
Change-Id: Ibf53acb6ce258419128fe809bda63539eac42a01
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2313057Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#790966}

Roll ChromeOS Broadwell AFDO profile from 86-4181.3-1595240638-benchmark-86.0.4207.0-r1 to 86-4181.3-1595240638-benchmark-86.0.4208.0-r1

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/cros-afdo-broadwell-chromium
Please CC c-compiler-chrome@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: c-compiler-chrome@google.com
Change-Id: Ia092f2b2daaaa53bb4176ef38515cf783142de26
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2314439Reviewed-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@{#790965}

Surfacing the composite failure reasons in the inspector
trace will allow Lighthouse to identify animations which
can cause jank during page load.

Bug: 230229
Change-Id: I40031189b3bb47f7bfa48ab2a7c06e40cd8c36c3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2283289
Commit-Queue: Adam Raine <asraine@google.com>
Reviewed-by: Robert Flack <flackr@chromium.org>
Reviewed-by: Paul Irish <paulirish@chromium.org>
Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#790964}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/76e4baebf3bd..deded62426ed

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

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

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

Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome
Bug: chromium:1085419,chromium:1107843,chromium:1107847,chromium:937821
Tbr: kelvinjiang@google.com,wjmaclean@google.com
Change-Id: Ic6222e0f92673d920ebcda1ed4be339687a80c75
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2313776Reviewed-by: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#790963}

This change adds CookieAccessSemantics to CookieAccessResult and
CookieAccessResult to CookieChangeInfo so change events will have
CookieAccessResult data. This change is part of a larger effort [1]
so CookieStore will eventually be able to consistently return
EffectiveSameSite for SameSite across all its endpoints.

[1]https://crbug.com/1092695

Bug: 1092695
Change-Id: I498bd79c1bfa6d92e92414173a219fe4f3d2482e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2288508
Commit-Queue: Ayu Ishii <ayui@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Maksim Orlovich <morlovich@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Lily Chen <chlily@chromium.org>
Cr-Commit-Position: refs/heads/master@{#790962}

Roll ChromeOS Silvermont AFDO profile from 86-4183.25-1595242326-benchmark-86.0.4207.0-r1 to 86-4183.25-1595242326-benchmark-86.0.4208.0-r1

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/cros-afdo-silvermont-chromium
Please CC c-compiler-chrome@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: c-compiler-chrome@google.com
Change-Id: I8cb9f0d6579616da5c537ba4eed40ec544cab373
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2314126Reviewed-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@{#790961}

Test expectation of conformance/misc/shader-precision-format.html
on ChromeOS FYI Release (kevin) is set to Failure on Nexus 5.

TBR=kbr@chromium.org

Bug: 1108368
Change-Id: I59aa049b373fd38fa759d0f3246de33ee95fde9f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2313302Reviewed-by: Kramer Ge <fangzhoug@chromium.org>
Commit-Queue: Kramer Ge <fangzhoug@chromium.org>
Cr-Commit-Position: refs/heads/master@{#790960}

Per-project coding style: ref counted types must be thread-safe and
sequence affinity declared with sequence checkers in destructors
if needed.

The motivation for such change is that our types get aggregated in
different ways, and mixing thread-safe and non thread-safe may
result into puzzling asserts in ref-counting code when objects
get shared between sequences.

Bug: 1105922
Change-Id: I31c5f3c118b633d3a3eb5bf072d3872fba2d2054
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2314418Reviewed-by: Joshua Pawlicki <waffles@chromium.org>
Commit-Queue: Sorin Jianu <sorin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#790959}