GitLab

As part of friendly settings project, we communicate the sWAA in sync
setup page. This CL enables to query the sWAA bit independently from
sync or history sync status. This is needed for the 2 following
scenarios during which the |WebHistoryService| is null:
1- The advanced sync setup flow (click on settings from the turn syn on
confirmation dialog).
2- Switching sync history from 'Off' to 'On'. This change does not take
effect until we close the |syncSetup| settings page.

Bug: 1035421
Change-Id: Id1651bd0d9508643e6218c6cef0c6f310109bef8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2012950Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Mihai Sardarescu <msarda@chromium.org>
Reviewed-by: David Roger <droger@chromium.org>
Commit-Queue: Monica Basta <msalama@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736295}

This CL has WebLayer Shell destroy its Profile at the point in the
shutdown process where Chrome destroys its Profile. This change is
concretely needed to enable the upcoming bringup of KeyedServices in
WebLayer; without this change, the KeyedServiceFactory singletons
DCHECK when they are destroyed at shutdown as they expect the context
shutdown (i.e., BrowserContext destruction) to have already occurred.

As part of this change we change session_service_browsertest.cc to
delete the Tab objects that were created by session restore. These
objects currently leak when not on Android, and a DCHECK deep in
//content goes off with this CL without this part of the change (that
DCHECK effectively expects that WebContents instances associated with
a BrowserContext instance are destroyed before the BrowserContext). I
have filed a bug for considering the long-term ownership model around
BrowserImpl::CreateTabForSessionRestore().

Bug: 1030692
Change-Id: I62bfd73e5e4d9d1099e18fc66cdd51d7380497c6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2025367
Commit-Queue: Colin Blundell <blundell@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736294}

The getDeviceInfo API now properly checks the screen lock and disk
encryption status from the OS at least for Debian or Ubuntu based
distros using the Gnome based desktops.

BUG=1037702
TEST=unit_tests and manually on a system with screen lock and cryptodisk

Change-Id: Ibebf0c74b9f45085d0e55ecb15fcd1cd9cfd9460
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2020949Reviewed-by: Owen Min <zmin@chromium.org>
Reviewed-by: Karan Bhatia <karandeepb@chromium.org>
Commit-Queue: Julian Pastarmov <pastarmovj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736293}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/4d88bb065eda..72e996f23962


Created with:
  gclient setdep -r src-internal@72e996f23962

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 jbudorick@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/+/master/autoroll/README.md

Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome
Bug: None
Tbr: jbudorick@google.com
Change-Id: I8ce645a650594e3533497f60b2c4c7b905744360
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2027196Reviewed-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@{#736292}

Adding a cors-and-webview-api.md to give WebView and chromium
developers detailed knowledge to keep the compatible CORS and
Origin related behaviors.

Bug: 1035366
Change-Id: Ia7695011ef4b04d528af523cd2a4a0a4503eff2e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2024652
Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org>
Auto-Submit: Takashi Toyoshima <toyoshim@chromium.org>
Reviewed-by: Nate Fischer <ntfschr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736291}

Previously an empty shared tab name would indicate that the infobar
being constructed is for the shared tab.
- Layout for the shared tab:
Sharing this tab to |app_name|  [Stop]
- Layout for all other tabs:
Sharing |shared_tab_name| to |app_name| [Stop] [Share this tab instead]

However, sometimes the shared tab name can be empty (see bug), leading
to incorrect infobars layout. Don't rely on the shared tab name for
infobar construction, use a separate parameter. When the shared tab is
untitled, create infobars for non-shared tabs using this layout:
Sharing a tab to |app_name| [Stop] [Share this tab instead]

Bug: 1011379
Change-Id: Iedf288060d20b8a97a4c769d83a83e74ac057bd4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2023828
Commit-Queue: Marina Ciocea <marinaciocea@chromium.org>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736290}

Based on [1], 'beginEvent' and 'endEvent' should only be dispatched for
elements that are active at the seeked-to time and elements that were
active at the previous/old/seeked-from time but are inactive at the
seeked-to time (respectively). 'repeatEvent's should not be disaptched
while seeking.

To handle this, extend the TimingUpdate helper class with a map that
tracks what interval the active elements had before the seek operation,
and whether the timing update operation is a seek operation (called
"fast-forward" since we end up moving in the forward direction
regardless of the actual seek direction).
Apart from that, the dispatching of 'repeatEvent's are also inhibited,
as well as the notifications of repeats in general.

[1] https://www.w3.org/TR/SMIL3/smil-timing.html#q114

Bug: 1039886
Change-Id: I17d91b1355858ee0b916d4fa46b9572e685e40e5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2020947Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#736289}

Bug: b/148450751
Change-Id: I055608c7a063f5772964712a10f726aca9e1145f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2023896Reviewed-by: Boris Sazonov <bsazonov@chromium.org>
Commit-Queue: Luca Hunkeler <hluca@google.com>
Cr-Commit-Position: refs/heads/master@{#736288}

The ChromeBrowserState has been moved from the "ios" namespace
to the global namespace by http://crrev.com/c/2014913. Fix the
uses from ios::ChromeBrowserState to ChromeBrowserState.

Also remove includes of chrome_browser_state_forward.h and use
a simple forward declaration instead (since the old name is no
longer necessary).

This CL was uploaded by git cl split.

R=eugenebut@chromium.org

Bug: 1042208
Change-Id: I0662606ee05132aaa3e9da65a25745f6e3b93e3b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2017344Reviewed-by: Eugene But <eugenebut@chromium.org>
Commit-Queue: Sylvain Defresne <sdefresne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736287}

Bug: 1028407
Change-Id: I11e8768ebb87f783be4bc1f419335f0ce1ad3da3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2023890Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Commit-Queue: Vasilii Sukhanov <vasilii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736286}

Using wpt-import in Chromium d2478a08.
With Chromium commits locally applied on WPT:
1029b7e9 "SharedWorker: Add WPT for upgrade-insecure-requests"


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

NOAUTOREVERT=true
TBR=robertma

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

This CL deletes the default copy constructor and introduce
a move constructor and CopyFrom method instead.

That's because we are planning to add a non-copiable member for
streaming body to ResourceRequest
 ("fetch() upload streaming" design doc/ http://bit.ly/2RlBw6x),
which is a instance member of WebURLRequest.

Bug: 787704
Change-Id: I86f1b094df4df56e98172b46e63982f80fb510f8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2000402
Commit-Queue: Yoichi Osato <yoichio@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736284}

Bug: 839389
Change-Id: I55b0dc09f7de94760e7690e2b4943846446eb901
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2026918Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Commit-Queue: Hitoshi Yoshida <peria@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736283}

ServiceWorkerTerminationOnNoControllee is originally implemented as stopping a
service worker with a delay. However, it may causes abortion of inflight evetns
dispatched to the service worker.
This CL is to make the termination respect the idleness of the service worker.
When all controllees are gone, the service worker's idle delay is made shorter
and the worker will be terminated soon by using the logic of idle timeouts.

Bug: 1043845
Change-Id: I420f174beb198177888625d4f33baafee55bc3bc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2022446Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Kenichi Ishibashi <bashi@chromium.org>
Commit-Queue: Makoto Shimazu <shimazu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736282}

R=etiennep@chromium.org

Bug: 1026641
Change-Id: I68c6e40f080ac5808cd9c67e227695ca921e1691
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2026714
Auto-Submit: Gabriel Charette <gab@chromium.org>
Commit-Queue: Etienne Pierre-Doray <etiennep@chromium.org>
Reviewed-by: Etienne Pierre-Doray <etiennep@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736281}

Two identical FontDescriptions with identical font-variation-settings
axis + value pairs should produce the same FontCacheKey hash. Fix an issue
in FontCacheKey computation that only performs pointer comparisons on
the FontVariationSettings.

This fixes a smaller percentage of FontCache misses during variable font
animations.

Bug: 1046257
Change-Id: I05ae3ac64b289dc7e1c41b03ab15d7e651195d9b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2023650Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Dominik Röttsches <drott@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736280}

If we're in a nested fragmentation context (multicol in multicol, for
instance), we may end up in a situation where we have no outer
fragmentainer space left to lay out inner columns. In such cases, if we
cannot fit anything at all, we'll now abort the column layout algorithm,
produce no fragment, and break before the multicol container (or even
earlier), and try again in the next outer fragmentainer.

This introduces another non-successful status for NGLayoutResult, which
all Layout() invokers need to handle as part of block fragmentation.
This doesn't really add much complexity, though: To participate in block
fragmentation, one needs to invoke MovePastBreakpoint() somehow
(possibly via BreakBeforeChildIfNeeded()) anyway, which will refuse to
move past if layout aborted. Apart from that, the only thing callers
need to take care of, is check if layout was successful before trying to
access the physical fragment of the result (since there'll be none if
layout was unsuccessful).

This CL only aborts multicol layout - we still lay out regular blocks
even in cases where we could have told up front that we're past the
fragmentainer boundary. Actually, even if there's a forced break before
a child, we'll lay it out, and let the container break before it
afterwards (and thus discard the fragment that we wasted time on
producing). We might want to change that as well in the future, if it
gives any benefits apart from minuscule performance improvements.

Bug: 829028
Change-Id: I473e7106fcc62921d71567d9496ca4c8a9729b05
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2023833Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736279}

This reverts commit 12bbfb47.

Reason for revert: this breaks video_decode_accelerator_unittest (and probably others) when built in Debug mode:

hardware_display_plane_manager.cc(368)] Check failed: state.properties.active.id.

Original change's description:
> Replace drmModeSetCrtc by Atomic APIs
> 
> If the device supports atomic APIs, use drmModeAtomicCommit to modeset
> and disable instead of drmModeSetCrtc.
> Abstracted Modeset and Disabled code to HDPM to handle both atomic and
> legacy call.
> Updated tests to support Connector and CRTC props.
> 
> BUG=987274
> TEST=HardwareDisplayControllerTest.CheckModesettingSetsProps,
> HardwareDisplayPlaneManagerLegacyTest.Modeset,
> HardwareDisplayPlaneManagerLegacyTest.DisableModeset,
> HardwareDisplayPlaneManagerAtomicTest.DisableModeset, Tested on
> Nautilus(Intel), Grunt(AMD) and Cave(Legacy).
> 
> Change-Id: Ic6d3873c94cb657fbe8de6dcd0faf97aeea05bd5
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2020809
> Reviewed-by: Daniel Nicoara <dnicoara@chromium.org>
> Commit-Queue: Mark Yacoub <markyacoub@google.com>
> Auto-Submit: Mark Yacoub <markyacoub@google.com>
> Cr-Commit-Position: refs/heads/master@{#736021}

TBR=dnicoara@chromium.org,dcastagna@chromium.org,markyacoub@google.com

Change-Id: Ic116c75d0eb1d81dfe45b6bcd76bcc2e27aaa4e6
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 987274
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2026779Reviewed-by: Alexandre Courbot <acourbot@chromium.org>
Commit-Queue: Alexandre Courbot <acourbot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736278}

Bug: 839389
Change-Id: I282656edadc4c309878b7cd8e3b8695e2689d87f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2027012
Commit-Queue: Hitoshi Yoshida <peria@chromium.org>
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736277}

Change-Id: I74fee102764e9313f510f2b825df992c3771defd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2027013Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org>
Commit-Queue: Hayato Ito <hayato@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736276}

This makes InitializeChildData() easier to understand, allows a tiny bit
of code reuse, and will make future changes to both these functions and
their callers simpler.

Bug: none
Change-Id: If19e736dbdc00d252c6043d6cf499cffd5d33386
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2026352
Commit-Queue: Dana Fried <dfried@chromium.org>
Reviewed-by: Dana Fried <dfried@chromium.org>
Auto-Submit: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736275}

GL or EGL image creation happens on the child thread, which should not
access any of the members that belong to the decoder thread. Yet this is
precisely what we were doing by reading the visible size of the buffer
to be imported, without any guarantee that the decoder thread will not
have changed it following a resolution change event.

Fix this by making the visible size a parameter of the bound method run
on the child thread. That way, it is read from the decoder thread and is
guaranteed to be consistent.

BUG=b:148421581
TEST=video.Seek.switch_vp8 passing on Kevin.
TEST=video.Seek.switch_vp8 passing on Hana.
TEST=video.Seek.switch_h264 passing on Krane.

Change-Id: Id8bc87ac50d6ebd2d74b2f6c25d42da83c933605
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2026852Reviewed-by: Andres Calderon Jaramillo <andrescj@chromium.org>
Commit-Queue: Alexandre Courbot <acourbot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736274}

This CL should have no visible effect. (maybe metrics, see below)

Currently, the same popup suggestions are built in two different places
and a third one reuses one of the methods. For updating, there will be
at least two more code paths building suggestions which cannot reuse the
current code.
To prevent code duplication, this CL moves building the suggestions into
helper methods.

One notable change: previously, we would record the metric
"PasswordManager.ShowAllSavedPasswordsShownContext" when the suggestion
entry was added to the list of suggestions. This might have recorded the
metric prematurely since there is another check that occasionally
prevents showing the popup (and with it, the "Show all" button).

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

This also adds a move constructor (since there's no obvious reason not
to, and Optional has them) and copy and move assignment (since
constructors and assignments should be defined together per style guide).

This also makes the comparison operators non-members since this is
preferred when feasible (e.g. makes implicit conversion for comparisons
apply equally to both sides).

Bug: none
Change-Id: I5b593f078063b8f9502dae232ed28e01ae41cd5e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2026688
Commit-Queue: Dana Fried <dfried@chromium.org>
Reviewed-by: Dana Fried <dfried@chromium.org>
Auto-Submit: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736272}

Macros are more efficient than functions, but increase the binary size
by a non-trivial amount. Given that the histogram calls in the folder
are emitted infrequently (less than about ten calls per hour),
functions are preferred.

Histogram emissions to PrintPreview.UserAction and
PrintPreview.PrintSettings will still be done using macros, given the
greater volume of emissions.

Change-Id: I19321a3648b1b361931369e47d41817250711f9b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2026601Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Daniel Hosseinian <dhoss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736271}

https://skia.googlesource.com/skia.git/+log/1b5b51de558d..3d23fc123c37

git log 1b5b51de558d..3d23fc123c37 --date=short --first-parent --format='%ad %ae %s'
2020-01-29 skia-recreate-skps@skia-swarming-bots.iam.gserviceaccount.com Update Go Deps

Created with:
  gclient setdep -r src/third_party/skia@3d23fc123c37

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 reed@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/+/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
Bug: None
Tbr: reed@google.com
Change-Id: Idd5720985687ac8b0243d3deb5ba229b30211dd4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2027193Reviewed-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@{#736270}

Bug: 1046066
Change-Id: Ifdf8b55ad7f2bcbb556483445eee0fb3d7c13e8e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2023353
Commit-Queue: Yusuf Sengul <yusufsn@google.com>
Reviewed-by: Tien Mai <tienmai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736269}

https://chromium.googlesource.com/angle/angle.git/+log/44c75073811b..5ca050d1fdbb

git log 44c75073811b..5ca050d1fdbb --date=short --first-parent --format='%ad %ae %s'
2020-01-29 syoussefi@chromium.org Vulkan: Set fragment output locations in SPIR-V
2020-01-29 syoussefi@chromium.org Vulkan: Set vertex attribute locations in SPIR-V
2020-01-29 syoussefi@chromium.org Vulkan: Set set/binding in SPIR-V
2020-01-29 spang@chromium.org Fuchsia: Blacklist swiftshader on Fuchsia

Created with:
  gclient setdep -r src/third_party/angle@5ca050d1fdbb

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 tobine@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/+/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
Bug: None
Tbr: tobine@google.com
Change-Id: I88598b98ea817c2d414376456f9e9027c83d3a74
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2027192Reviewed-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@{#736268}

This follows crbug.com/955013, but added -swarming suffix due to builder
name in test_suite_exceptions.pyl.

test_suite_exceptions.pyl does not distinguish
android-marshmallow-arm64-rel under chromium.android or chromium.swarm

Bug: 955013
Change-Id: I5be20bbf312bda9353071f9d11540492d7f57a76
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2026917
Auto-Submit: Takuto Ikuta <tikuta@chromium.org>
Reviewed-by: Yoshisato Yanagisawa <yyanagisawa@google.com>
Commit-Queue: Takuto Ikuta <tikuta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736267}

We, in team, agreed not to break include header file paths written in
code generator.  Breaking them makes it difficult to find or sort lines.

Bug: 839389
Change-Id: I882d9bd37fa85bd1359933757e491c4db65a7971
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2026560Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Commit-Queue: Hitoshi Yoshida <peria@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736266}

|NGPaintFragment| has two offsets; one relative to its parent
and the other relative to the container block.
|NGFragmentItem| has only one, so it was named as |Offset()|,
but r736251 <crrev.com/c/2024133> revealed that this can be
confusing and mis-used, even by myself.

This patch adds |InContaininerBlock| suffixes to all functions
that return the offset relative to the container block.

This patch has no behavior changes.

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

enums.xml numbers come from the suggested values given by the unit test.
See https://chromium.googlesource.com/chromium/src/tools/+/refs/heads/master/metrics/histograms/README.md#flag-histograms
for more information.

Bug: 1012578
Change-Id: Idf5aacf0aae6b6c2e5f4bdad621d028710e26052
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2026916
Commit-Queue: Rachel Carpenter <carpenterr@google.com>
Reviewed-by: dstockwell <dstockwell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736264}

Currently when the |get-info| command is caught by an element, the event
continues to propagate, which causes |display_| to be called twice in
some cases.

Fix this: stop propagation of the event when handled.  No change in
behavior, no new tests.

Bug: 1044448
Change-Id: I670bb872b414f18265cb68688d704ab4c0088976
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2026532Reviewed-by: Noel Gordon <noel@chromium.org>
Commit-Queue: Noel Gordon <noel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736263}

https://chromium.googlesource.com/catapult.git/+log/1fbc1b7f92be..c768c76138f9

git log 1fbc1b7f92be..c768c76138f9 --date=short --first-parent --format='%ad %ae %s'
2020-01-29 abennetts@google.com Fix 'git_hash' KeyError when posting bug updates about patches.

Created with:
  gclient setdep -r src/third_party/catapult@c768c76138f9

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 skyostil@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/+/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_optional_gpu_tests_rel
Bug: chromium:1046618
Tbr: skyostil@google.com
Change-Id: Ie3f513cfa5fba0d06b5737676b5e034b9d30d7ed
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2027190Reviewed-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@{#736262}

A user defined type is defined with a non-partial and non-mixin
definition of an IDL definition.
Following it, this CL defines a Union's component as a set of components
where its member types are defined.


Bug: 839389
Change-Id: I8632364d72cc33680ed30086f42777bb42f0ce43
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2026554
Commit-Queue: Hitoshi Yoshida <peria@chromium.org>
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736261}

Bug: 839389
Change-Id: I4b86d896e527caa15a2150e2a1544cc080e227df
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2026835Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736260}

https://skia.googlesource.com/skia.git/+log/dcc8c5431bcb..1b5b51de558d

git log dcc8c5431bcb..1b5b51de558d --date=short --first-parent --format='%ad %ae %s'
2020-01-29 skia-autoroll@skia-public.iam.gserviceaccount.com Roll ../src 77c4d4c4..243744c2 (487 commits)
2020-01-29 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/swiftshader 34e16df059f8..6c3dc3581eaf (2 commits)
2020-01-29 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/angle2 086aded3cb74..2bc9cc12f0b0 (19 commits)
2020-01-29 mtklein@google.com remove more vtune references
2020-01-29 mtklein@google.com start on 2pt conical gradients

Created with:
  gclient setdep -r src/third_party/skia@1b5b51de558d

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 reed@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/+/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
Bug: None
Tbr: reed@google.com
Change-Id: Ib5adec88e352db347bb4f6c86cc9591f74b3b57a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2027002Reviewed-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@{#736259}

https://chromium.googlesource.com/external/github.com/KhronosGroup/glslang/+log/07a55839eed5..9a80305c0897

git log 07a55839eed5..9a80305c0897 --date=short --first-parent --format='%ad %ae %s'
2020-01-29 johnkslang@users.noreply.github.com Merge pull request #2068 from jljusten/standalone-fix-long-help

Created with:
  gclient setdep -r src/third_party/glslang/src@9a80305c0897

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/glslang-chromium-autoroll
Please CC radial-bots+chrome-roll@google.com,tobine@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/+/master/autoroll/README.md

Bug: None
Tbr: radial-bots+chrome-roll@google.com,tobine@google.com
Change-Id: I9a4d1e7af760ffe779a482e7f4ac4bc1c3b93f6d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2027189Reviewed-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@{#736258}

Right now we're not loading saved files ranking models from disk on
dev channel, for debugging reasons. We don't need this any more, so
this CL removes the logic.

Bug: 955893
Change-Id: I4159ca99c020f422861480a4c24b39db362ce242
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010596Reviewed-by: Jia Meng <jiameng@chromium.org>
Commit-Queue: Tony Yeoman <tby@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736257}

Before renaming swarming builders for crbug.com/955013, let me fix build
config so that each builder uses the same build config with typical
builders.

Bug: 943176
Change-Id: Ie203ee1ccd05491fe8332e1206d75ad6235b022c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2026556
Auto-Submit: Takuto Ikuta <tikuta@chromium.org>
Reviewed-by: Yoshisato Yanagisawa <yyanagisawa@google.com>
Commit-Queue: Takuto Ikuta <tikuta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736256}