GitLab

V8 roll will include console.timeLog implementation.

TBR=dgozman@chromium.org

Bug: chromium:854474
Change-Id: I3669e7cd82e1c83689f91a297a81c7324fe6db7e
Reviewed-on: https://chromium-review.googlesource.com/1251749
Commit-Queue: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org>
Reviewed-by: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595112}

These gesture enums were missing.  Prevented two finger tap
from silencing the screen reader.

Bug: 888695
Test: Manual
Change-Id: I6e71cf65de19651ea3560fbf825cfe59ca6cdcbb
Reviewed-on: https://chromium-review.googlesource.com/1241274Reviewed-by: Alex Sakhartchouk <alexst@chromium.org>
Commit-Queue: Randy Rossi <rmrossi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595111}

We want to have the same design with the one in the bubble.
The icon is same as unified_menu_managed.icon, but differs by the
padding size. So it's kept as a separate file from that.

Bug: 870409
Change-Id: I9876c12bad7aa99f5fe46cf599866aed2eced70f
Reviewed-on: https://chromium-review.googlesource.com/1250382Reviewed-by: Evan Stade <estade@chromium.org>
Commit-Queue: Tatsuhisa Yamaguchi <yamaguchi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595110}

This change cleans up some of the custom control work, including:
- removing unused function
- updating naming to be consistent to other functions
- rearranges for proximity to relevant functions

There are no functional changes.

Change-Id: I5b86f5dec7b850745e11f3adac16de159bf8ac48
Reviewed-on: https://chromium-review.googlesource.com/1249540Reviewed-by: Hidehiko Abe <hidehiko@chromium.org>
Reviewed-by: Eliot Courtney <edcourtney@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: apacible <apacible@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595109}

Bug: 832676
Change-Id: I08c741b57717e69d434d34b1ad73c132e3125d94
Reviewed-on: https://chromium-review.googlesource.com/1251329Reviewed-by: Erik Chen <erikchen@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595108}

- Modifies Mojo code caching API to specify JS or WASM cache.
- Adds WebAssembly GeneratedCodeCache.

Bug: chromium:719172
Change-Id: Ie7dec8112a8e6cea7c576e2e502683bba0bb3d4a
Reviewed-on: https://chromium-review.googlesource.com/1235283
Commit-Queue: Bill Budge <bbudge@chromium.org>
Reviewed-by: Mythri Alle <mythria@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595107}

The CCT benchmark is a small app with minimal dependencies and no
proguard. If it includes Chromium java pieces, it would not fit into the
method count limits, so it would need to enable proguard. This is overly
heavy for the purposes of this app. So we would like to use
android.util.Log in this app instead.

Bug: None
Change-Id: Ia44c6d60a97721bce827061e022d4c5cb8c2fa81
Reviewed-on: https://chromium-review.googlesource.com/1251624Reviewed-by: agrieve <agrieve@chromium.org>
Commit-Queue: Egor Pasko <pasko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595106}

In r591642 we updated the behavior so layout containment
suppress baseline alignment, while size containment does not.
However, we forgot about the special cases (flexbox and grid)
that have their own code for this, which are fixed in this patch.

Regarding WPT tests, these changes will fix the following issue:
https://github.com/web-platform-tests/wpt/issues/13252

One of the Mozilla tests is failing now, it was mentioned
in the associated bug report (https://bugzilla.mozilla.org/1491235).

BUG=882333
TEST=external/wpt/css/css-contain/contain-layout-button-001.html
TEST=external/wpt/css/css-contain/contain-layout-flexbox-001.html
TEST=external/wpt/css/css-contain/contain-layout-grid-001.html
TEST=external/wpt/css/css-contain/contain-size-button-001.html
TEST=external/wpt/css/css-contain/contain-size-flexbox-001.html
TEST=external/wpt/css/css-contain/contain-size-grid-001.html

Change-Id: I5e437d7f82d07d2f6222416a1eb9a3b89cb44eca
Reviewed-on: https://chromium-review.googlesource.com/1250524
Commit-Queue: Manuel Rego <rego@igalia.com>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595105}

This is needed to support IOv2 occlusion testing via hit test. It also allows
content under foreignObject to receive disambiguation on touch screens.

Bug: 823796

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I80089feb9a30d3f28ce2c68f7276cafc5410adcb
Reviewed-on: https://chromium-review.googlesource.com/1227470
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#595104}

This CL filters the output that explains dealing with size regressions
when no size regression occured.

Also adds normalized_apk_size to the output JSON.

Bug: 702625
Change-Id: I38be87bdd6b4fb74e179043cabd42dfcbc93473f
Reviewed-on: https://chromium-review.googlesource.com/1249883
Commit-Queue: Eric Stevenson <estevenson@chromium.org>
Reviewed-by: agrieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595103}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/bea5a39cb895..ce4c48bb2fa0


Created with:
  gclient setdep -r src-internal@ce4c48bb2fa0

The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=mmoss@chromium.org

Change-Id: I0dce02aea77a56df271dc3a1dd7632efb895fb18
Reviewed-on: https://chromium-review.googlesource.com/1250952Reviewed-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@{#595102}

Fix ICWYU error in chrome_cleaner/os/rebooter_api.h

R=csharp

Bug: 830892
Change-Id: I3f311bdd32e21b2901594a835aead483ae8d823b
Reviewed-on: https://chromium-review.googlesource.com/1227683
Commit-Queue: Joe Mason <joenotcharles@chromium.org>
Reviewed-by: Martin Šrámek <msramek@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Chris Sharp <csharp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595101}

In content/child there were two g_lazy_tls global variables
in two different anonymous namespaces. In jumbo build experiments,
where many files compile together and share anonymous namespace,
those globals collided. This patch gives them more distinct names.

Bug: 746953
Change-Id: Icac936f2092d1c8b1bc5de38d443d71cb8955045
Reviewed-on: https://chromium-review.googlesource.com/1251605Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Daniel Bratell <bratell@opera.com>
Cr-Commit-Position: refs/heads/master@{#595100}

This baselines must have been created back when we had NG block
fragmentation enabled by default, which apparently generates (or
generated) different paint layer sizes for multicol.

Just removed NG-specific baselines, and the tests pass. With one
exception: fast/forms/select/menulist-appearance-rtl.html still needs an
NG-specific baseline, because RTL text run dumps are prefixed with "RTL"
in legacy, while it's not in NG. Like this:
  text run at (26,0) width 52 RTL: [...]
vs.
  text run at (26,0) width 52: [...]
There are similar differences further below in the file. There are also
some LayoutNGBlockFlow -> LayoutBlockFlow changes under LayoutMenuList,
because we've started to force legacy inside form elements since last
rebaseline.

Bug: 890135
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
Change-Id: I0da4e267fc216809c54dea0b3f6c7c4b26225a20
Reviewed-on: https://chromium-review.googlesource.com/1250922
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595099}

TBR=dgozman@chromium.org

Bug: 780025
Change-Id: I36e85988a6402bee5ca8fead28fddb64081c4133
Reviewed-on: https://chromium-review.googlesource.com/1246062
Commit-Queue: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595098}

The CL lands the necessary strings for iOS. A pending task is to add a footer for the Sync users.

Bug: 890336
Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs
Change-Id: I47732fa83287439b40c52ed37ac6850b2986ab41
Reviewed-on: https://chromium-review.googlesource.com/1251547Reviewed-by: Vadym Doroshenko <dvadym@chromium.org>
Commit-Queue: Vasilii Sukhanov <vasilii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595097}

This CL removes the bulk of the legacy reading list UI, including all of the classes and support for the collection view-base list.

Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs
Change-Id: Iaca3bb654761f5d262aba416dc42bf6d89055d12
Reviewed-on: https://chromium-review.googlesource.com/1249072
Commit-Queue: Mark Cogan <marq@chromium.org>
Reviewed-by: Gauthier Ambard <gambard@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595096}

Disable the warning until we clean it up.

Bug: 890307
Change-Id: I6fe7dc36bef54f5fec63d71efe6e300b95b6c362
Reviewed-on: https://chromium-review.googlesource.com/1251622
Commit-Queue: Hans Wennborg <hans@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595095}

Also added enum for "tab switch offered". This allows UMA to treat
the data (0,1) as entities, not quantities.

Bug: 854714
Change-Id: I891aa38603c741070013a6cb06cc52df2bce14cb
Reviewed-on: https://chromium-review.googlesource.com/1247028
Commit-Queue: Kevin Bailey <krb@chromium.org>
Reviewed-by: Mark Pearson <mpearson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595094}

By mistake SequenceManagerImpl is crashing on exit if
CreateUnboundSequenceManager(null) is called but BindToMessageLoop
is not.  This patch fixes that.

Bug: 863341, 872372
Change-Id: I2827ab40c1e32553f1c42229762732b5cd42801d
Reviewed-on: https://chromium-review.googlesource.com/1251448Reviewed-by: Alexander Timin <altimin@chromium.org>
Commit-Queue: Alex Clarke <alexclarke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595093}

Neither signin_manager.h nor profile_oauth2_token_service.h are being
used from this implementation file, we can clean these includes up.

Bug: 890236
Change-Id: I3d6e55bc63e5c6e43115de1e46022fdee404d83e
Reviewed-on: https://chromium-review.googlesource.com/1251623Reviewed-by: Justin Cohen <justincohen@chromium.org>
Commit-Queue: Mario Sanchez Prada <mario@igalia.com>
Cr-Commit-Position: refs/heads/master@{#595092}

This CL adds the getResourcePriority method to the WorkerInternals
interface via the partial interface defined in core/fetch. This will
help testing resource priorities fetched from worker contexts
(i.e., Service Workers). Before this CL, getResourcePriority was only
exposed on Internals, and thus all ResourceFetchers associated with
WorkerGlobalScopes could not be queried.

R=kinuko@chromium.org, yhirano@chromium.org, yoav@yoav.ws

Bug: 872776
Change-Id: I010b95441c191cf90dfda7b0d5f58c7e7d6c7c21
Reviewed-on: https://chromium-review.googlesource.com/1249882Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: Dominic Farolino <domfarolino@gmail.com>
Cr-Commit-Position: refs/heads/master@{#595091}

next_token_request_time is always supposed to be equal to the scheduled
run time of request_access_token_retry_timer_. Instead of keeping this
redundant state (and risk it getting out of sync), let's just compute
next_token_request_time when we need it.

Bug: 889859
Change-Id: I2b47d5dd78ef55bbfe1c0b43657cf9125e3f4586
Reviewed-on: https://chromium-review.googlesource.com/1250927
Commit-Queue: Marc Treib <treib@chromium.org>
Reviewed-by: Mikel Astiz <mastiz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595090}

Changing the type of the parameter from GURL to
url::Origin is desirable because:

1) The only user of the parameter
   (ProxyingURLLoaderFactory::MaybeProxyRequest) was looking at the origin,
   rather than at the URL.

2) Current users of the WillCreateURLLoaderFactory's parameter
   (ProxyingURLLoaderFactory::MaybeProxyRequest) and future callees of
   RenderFrameHostImpl::CreateNetworkServiceDefaultFactoryInternal
   (extensions::URLLoaderFactoryManager - see
   https://crrev.com/c/1228478) should make decisions based on the
   origin rather than URL (URLs with blob:, data: and about: schemes
   are tricky here).

Bug: 846346
Change-Id: Ia1acc3735664c2f6f6290bd23b5431b633381644
Reviewed-on: https://chromium-review.googlesource.com/1234361Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: Mihai Sardarescu <msarda@chromium.org>
Reviewed-by: Nasko Oskov <nasko@chromium.org>
Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595089}

Bug: 854101
Change-Id: Ibd9375295ea26ff0533dadcc8153cabfe71ba786
Reviewed-on: https://chromium-review.googlesource.com/1251443
Commit-Queue: Denis Kuznetsov <antrim@chromium.org>
Reviewed-by: Sergey Poromov <poromov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595088}

The alert dialog property should be set to nil in the dialog callback
before doing anything else.
DCHECK is failing since the first alert dialog still exist in
_alertCoordinator, when creating the second alert dialog:
https://cs.chromium.org/chromium/src/ios/chrome/browser/ui/authentication/authentication_flow_performer.mm?l=321

There is no consequence since when cleaning up _alertCoordinator for the
first dialog (while the second dialog is already set into _alertCoordinator).
_alertCoordinator is not set to nil because of that test [1] when the
cleanup is done [2].

[1]: https://cs.chromium.org/chromium/src/ios/chrome/browser/ui/authentication/authentication_flow_performer.mm?l=387
[2]: https://cs.chromium.org/chromium/src/ios/chrome/browser/ui/authentication/authentication_flow_performer.mm?l=218


Bug: 890332
Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs
Change-Id: I012baa44c3a129a54bc8a3d4c0f442b06e04b68a
Reviewed-on: https://chromium-review.googlesource.com/1251601
Commit-Queue: Jérôme Lebel <jlebel@chromium.org>
Reviewed-by: Mihai Sardarescu <msarda@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595087}

This CL uses ScopedBlockingCall to mark blocking calls in /device/bluetooth/bluez.

This CL was created by replacing calls to AssertBlockingAllowed()
with instantiations of ScopedBlockingCall(MAY_BLOCK).
I kindly ask the reviewer to make sure of the following:
  - ScopedBlockingCall is instantiated in a scope with minimal CPU usage.
    If this is not the case, ScopedBlockingCall should be instantiated
    closer to the blocking call. See scoped_blocking_call.h for more
    info. Please let me know when/where the blocking call happens if this needs
    to be changed.
  - Parameter |blocking_type| matches expectation (MAY_BLOCK/WILL_BLOCK). See
    BlockingType for more info. While I assumed MAY_BLOCK by default, that might
    not be the best fit if we know that this callsite is guaranteed to block.
  - The ScopedBlockingCall's scope covers the entirety of the blocking operation
    previously asserted against by the AssertBlockingAllowed().

This CL was uploaded by git cl split.

R=rkc@chromium.org

Bug: 874080
Change-Id: I4ab9d5ae6b94c448f3e30e6e9c607fb88a1078bf
Reviewed-on: https://chromium-review.googlesource.com/1191183Reviewed-by: Rahul Chaturvedi <rkc@chromium.org>
Commit-Queue: Etienne Pierre-Doray <etiennep@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595086}

Change-Id: Iff2fac58c58042d4ddf55ef962df61954414a1fd
Reviewed-on: https://chromium-review.googlesource.com/1230025
Commit-Queue: Mugdha Lakhani <nator@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Reviewed-by: Rayan Kanso <rayankans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595085}

The tests were previously flaky because of crbug.com/884589.  Now that it's fixed, renable these tests.

The EncryptedMediaTest's used to fail for the same reason, but are now failing because of a memory leak (crbug.com/889993), so keep these disabled for now.

Bug: 884589
Change-Id: Ia394e710d47f995f64ce858a51439ad11bdc2518
Reviewed-on: https://chromium-review.googlesource.com/1249913Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Ryan Cui <rcui@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595084}

This solves the issue of auto-resuming notifications. OnItemUpdated was
being called after the notification was paused with an offline item
containing an out-of-sync status.

There is also a race condition between pausing the job (OIC) and the
download completing (DS), so new downlaods need to be throttled in case
the job is paused.

Bug: 855856
Change-Id: I537789e7b1607fc4ce69b9cc7593a6499152475c
Reviewed-on: https://chromium-review.googlesource.com/1241157
Commit-Queue: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Reviewed-by: Mugdha Lakhani <nator@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595083}

An entire URLRequestContext was created for extensions when it was only
used to hold a CookieStore for the chrome-extension:// origin. This
patch simplifies this situation by removing this concept and replacing
it with just an extensions-specific CookieStore. This should reduce
further confusion that this URLRequestContext is used for actual URL
requests.

Bug: 158386
Change-Id: Iaab7b19c578eae75c79a1fb93434e0b04db95c7c
Reviewed-on: https://chromium-review.googlesource.com/1250098Reviewed-by: Jochen Eisinger <jochen@chromium.org>
Commit-Queue: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595082}

This reverts commit 7c58d162.

Reason for revert:
This broke win-asan, see 2nd bug.

Original change's description:
> Roll clang 342523:343189.
> 
> Bug: 888476
> Change-Id: Iccb39603a10261d1bdf3fcb26b008bb02fc371e6
> Reviewed-on: https://chromium-review.googlesource.com/1245465
> Commit-Queue: Nico Weber <thakis@chromium.org>
> Reviewed-by: Nico Weber <thakis@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#594765}

TBR=thakis@chromium.org,hans@chromium.org

Change-Id: I003bbfca7a542fe18c31a679ea58cf1da2c3fdb3
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 888476, 890310
Reviewed-on: https://chromium-review.googlesource.com/1251606Reviewed-by: Hans Wennborg <hans@chromium.org>
Commit-Queue: Hans Wennborg <hans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595081}

Bug: 854101
Change-Id: Iea1248fd7d8bcb8c5eb0443c713fbf8717b1255a
Reviewed-on: https://chromium-review.googlesource.com/1251542
Commit-Queue: Denis Kuznetsov <antrim@chromium.org>
Reviewed-by: Sergey Poromov <poromov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595080}

This reverts commit 7c77c254.

Reason for revert: Probably breaks some chromium.webrtc

Original change's description:
> Roll src/third_party/webrtc 89f64d305eff..cbcbc225687f (3 commits)
> 
> https://webrtc.googlesource.com/src.git/+log/89f64d305eff..cbcbc225687f
> 
> 
> git log 89f64d305eff..cbcbc225687f --date=short --no-merges --format='%ad %ae %s'
> 2018-09-28 nisse@webrtc.org Reland "Replace VideoDecoder with VideoDecoderFactory in VideoReceiveStream config."
> 2018-09-28 kron@webrtc.org Parse two-byte header extensions.
> 2018-09-28 henrika@webrtc.org Improves threading model in AudioDeviceTest.
> 
> 
> Created with:
>   gclient setdep -r src/third_party/webrtc@cbcbc225687f
> 
> The AutoRoll server is located here: https://autoroll.skia.org/r/webrtc-chromium-autoroll
> 
> Documentation for the AutoRoller is here:
> https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
> 
> If the roll is causing failures, please contact the current sheriff, who should
> be CC'd on the roll, and stop the roller if necessary.
> 
> CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_chromium_archive_rel_ng;luci.chromium.try:mac_chromium_archive_rel_ng
> TBR=webrtc-chromium-sheriffs-robots@google.com
> 
> Change-Id: I047923cf7501cf353a3b50b6c560e0ab42a550da
> Reviewed-on: https://chromium-review.googlesource.com/1250948
> Reviewed-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@{#595070}

TBR=chromium-autoroll@skia-public.iam.gserviceaccount.com,webrtc-chromium-sheriffs-robots@google.com

Change-Id: Icb55c9c65ef78633440b412a6b7ecddac7437e75
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Cq-Include-Trybots: luci.chromium.try:linux_chromium_archive_rel_ng;luci.chromium.try:mac_chromium_archive_rel_ng
Reviewed-on: https://chromium-review.googlesource.com/1251450Reviewed-by: Mirko Bonadei <mbonadei@chromium.org>
Commit-Queue: Mirko Bonadei <mbonadei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595079}

This change is supposed to delete obsolete HTTP data from the password
store 60 seconds after start up.
This CL will delete HTTP credentials with HSTS enabled for that host and
for which an equivalent (i.e. same signon_realm, PasswordForm::Scheme,username
and password) HTTPS credential exists. Also it replaces HTTP credentials by an HTTPS
version of that form if site has HSTS enabled and no HTTPS credential
with same signon_realm, same PasswordForm::Scheme and username exists.

Bug: 871140, 879244
Change-Id: I605e39f25ce1052aa67d95cf84601a9db94c33a6
Reviewed-on: https://chromium-review.googlesource.com/1178282Reviewed-by: Vaclav Brozek <vabr@chromium.org>
Reviewed-by: Jan Wilken Dörrie <jdoerrie@chromium.org>
Commit-Queue: Narcis Gemene <gemene@google.com>
Cr-Commit-Position: refs/heads/master@{#595078}

Using wpt-import in Chromium dfabb6a5.

Build: https://ci.chromium.org/buildbot/chromium.infra.cron/wpt-importer/25461

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=raphael.kubo.da.costa@intel.com

No-Export: true
Change-Id: Ia29fac6b63b6fb1cf3d7d038570100033399d4d4
Reviewed-on: https://chromium-review.googlesource.com/1251227
Commit-Queue: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org>
Reviewed-by: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595077}

When loading the primary account, the SigninManager may decide to
force sign-out (e.g if the user disallowed signed in). In this case,
the GAIAInfoUpdateService is not notified (as it is created only after
the SigninManager), so it fails to clear the GAIA name, given name and
picture from the profile entry cache.

This CL clears the GAIA name, given name and picture from the profile
entry cache when the GAIAInfoUpdateService is created if the profile
does not have any primary account.

Bug: 890309

Change-Id: I21211cc355672e4ecdc4e911a56187c63b97b8f1
Reviewed-on: https://chromium-review.googlesource.com/1251442Reviewed-by: Thomas Tangl <tangltom@chromium.org>
Commit-Queue: Mihai Sardarescu <msarda@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595076}

- Updates _currentPage properly in response to 3-finger accessibility swipe. This will now properly read out the currently visible page if a user swipes to a different page.
- Ensures that only the currently visible page's elements can be selected in the scroll view. This resolves an issue VoiceOver was having with what page to readout and to focus on. Oftentimes the visible page was not readout or selectable.

Video: https://drive.google.com/open?id=1Q62MUlrVcNlqnFIQOfw_YiGHinTKb_45

Bug: 880079
Change-Id: Ic9a91762e9a5f04b267ac588c83a675d61bd53cf
Reviewed-on: https://chromium-review.googlesource.com/1221474
Commit-Queue: Chris Lu <thegreenfrog@chromium.org>
Reviewed-by: Mark Cogan <marq@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#592818}
Reviewed-on: https://chromium-review.googlesource.com/1238995
Cr-Commit-Position: refs/heads/master@{#595075}

https://android.googlesource.com/platform/external/perfetto.git/+log/40a2e1ea2449..5cfa93810a40


git log 40a2e1ea2449..5cfa93810a40 --date=short --no-merges --format='%ad %ae %s'
2018-09-28 hjd@google.com Merge "perfetto-ui: Factor checkerboard out"


Created with:
  gclient setdep -r src/third_party/perfetto@5cfa93810a40

The AutoRoll server is located here: https://autoroll.skia.org/r/perfetto-chromium-autoroll

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=perfetto-bugs@google.com

Change-Id: I4638054db03af150d38ea83923ccdc147e88e23e
Reviewed-on: https://chromium-review.googlesource.com/1250951Reviewed-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@{#595074}

This adds new policy that allows admin to restrict duplex mode
to either one-sided only or two-sided only.

Bug: 853877, 885265
Change-Id: I3698ca4d248415693590b895d0f3c28ad95755c2
Reviewed-on: https://chromium-review.googlesource.com/1224310
Commit-Queue: Vladislav Kuzkokov <vkuzkokov@chromium.org>
Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#595073}