GitLab

MessageLoop will go away, eventually.

BUG=891670

Change-Id: Icd3016627e9c59f8e16e7f8031131b17b3d44eaa
Reviewed-on: https://chromium-review.googlesource.com/c/1352765Reviewed-by: Marc Treib <treib@chromium.org>
Commit-Queue: Carlos Caballero <carlscab@google.com>
Cr-Commit-Position: refs/heads/master@{#611707}

Sometimes BrowsingDataTest.testCookiesDeleted fails because it gets a
result that doesn't contain number.
This can happen if the BrowsingDataCounter result isn't calculated
within 140ms and the counter responds with "Calculating...".
To fix test flakiness, we have to ignore these messages.

Bug: 909690
Change-Id: I087280bd98b8e5604a352692e3f0740e30eb4f02
Reviewed-on: https://chromium-review.googlesource.com/c/1353923
Commit-Queue: Christian Dullweber <dullweber@chromium.org>
Reviewed-by: Boris Sazonov <bsazonov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611706}

Allow overriding document.lastModified for standalone Documents.

Behavior matches Firefox.

Bug: 765116

Change-Id: I10006622f8866b5aa785e91cc17d2147f884950b
Reviewed-on: https://chromium-review.googlesource.com/c/1344137Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Commit-Queue: Rob Buis <rbuis@igalia.com>
Cr-Commit-Position: refs/heads/master@{#611705}

Use identity::IsUsernameAllowedByPattern() instead so that we can migrate
those consumers entirely to the IdentityManager in follow-up patches.

Also, in order to make it explicit that this API should not be used any
more, make SigninManager::IsAllowedUsername() a private method and friend
it with the relevant test cases from SigninManagerTest, so that it can
only be used from there. And while at it, also remove some stale lines
"friending" SigninManager with test cases that no longer exist.

Bug: 890794, 890815, 906085
Change-Id: Id8a72b0efd89818e02c6d1e73aac1451207b9625
Reviewed-on: https://chromium-review.googlesource.com/c/1346409Reviewed-by: Mihai Sardarescu <msarda@chromium.org>
Reviewed-by: Sylvain Defresne <sdefresne@chromium.org>
Commit-Queue: Mario Sanchez Prada <mario@igalia.com>
Cr-Commit-Position: refs/heads/master@{#611704}

The test PersistProgressMarkerOnRestart used to fail for USS Bookmarks
because the metadata weren't persisted properly.

This CL makes sure that the processor would outlive the bookmark model
such that the metadata is available at the time when the model is
getting destructed and persisted on disk.

Bug: 816866
Change-Id: Ief259bd75ee66a6f9bb1dd70fc2ef6a446ebbd7a
Reviewed-on: https://chromium-review.googlesource.com/c/1349314
Commit-Queue: Mohamed Amir Yosef <mamir@chromium.org>
Reviewed-by: Mikel Astiz <mastiz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611703}

Parallelize processing of each entry in the zip (jar) file. This also
preserves build determinism since we wait on each future in sequence.

Estimated total savings on an incremental build: 1.6 seconds.

Bug: 906803
Change-Id: Iec0cfcc4511bf090a6f50a3d64eea3f8b3459778
Reviewed-on: https://chromium-review.googlesource.com/c/1351458
Commit-Queue: Peter Wen <wnwen@chromium.org>
Reviewed-by: Eric Stevenson <estevenson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611702}

https://android.googlesource.com/platform/external/perfetto.git/+log/f16618125056..5403e4fde106


git log f16618125056..5403e4fde106 --date=short --no-merges --format='%ad %ae %s'
2018-11-28 primiano@google.com Roll clang and libcxx to match chromium revisions


Created with:
  gclient setdep -r src/third_party/perfetto@5403e4fde106

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: Ie75875424109a4f955c1bd5f8cf9ac8fcd7b62a9
Reviewed-on: https://chromium-review.googlesource.com/c/1352861Reviewed-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@{#611701}

https://chromium.googlesource.com/chromium/src/third_party/freetype2.git/+log/fb0d66d04c4d..3dd4e76b19f3

$ git log fb0d66d04..3dd4e76b1 --date=short --no-merges --format='%ad %ae %s'
2018-11-27 apodtele * builds/windows/vc2010/freetype.vcxproj: Simplify.
2018-11-27 chris.liddell [type1,cff] Add FT_{Set,Get}_MM_WeightVector API calls.
2018-11-27 bungeman [cff] Fix compiler warning (#55105).
2018-11-27 bungeman [truetype] Fix numeric overflow (#55103).
2018-11-25 apodtele [builds] Belated DLL support with vc2002-vc2008.
2018-11-22 prince.cherusker * src/cff/cffparse.c: Please the compiler.
2018-11-22 prince.cherusker [cff] Fix memory overflow.
2018-11-18 apodtele * builds/windows/{visualc,vc2005,vc2008}/freetype.vcproj: Fix it.
2018-11-10 apodtele Clarification.
2018-11-10 apodtele [smooth] Placeholder only for library-enabled LCD filtering.
2018-11-09 wl [psaux] Add safety guard (#54985).
2018-11-08 apodtele * builds/unix/configure.raw: Require `windows.h' for windres.
2018-11-08 apodtele [ftstroke] Fix unpredictable failures (#54986).
2018-11-08 apodtele [ftstroke] Fix unpredictable failures (#54976).

Created with:
  roll-dep src/third_party/freetype/src
R=bungeman@chromium.org,drott@chromium.org

CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_chromium_msan_rel_ng

PDFium-Issue: pdfium:1196
Bug: 907670
Change-Id: Ic23ebcc22837b6d4b85d19b4b84159faffedd66d
Reviewed-on: https://chromium-review.googlesource.com/c/1353890
Commit-Queue: Ben Wagner <bungeman@chromium.org>
Reviewed-by: Ben Wagner <bungeman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611700}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/62103075707c..c0d86a6b9d74


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

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: Ie36cd95b09f1980e280780ee7b497a9617dfcd96
Reviewed-on: https://chromium-review.googlesource.com/c/1351488Reviewed-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@{#611699}

No need to zip up the generated source just to unzip it again :P

This reverts commit 61c12ee7.

Reason for reland: Fix missing deps for realz

TBR=pauljensen@chromium.org,agrieve@chromium.org

Bug: 908479
Change-Id: Ib3108f01ad49a68aa1a2d6de303aaa79d899ec8f
Reviewed-on: https://chromium-review.googlesource.com/c/1352520
Commit-Queue: agrieve <agrieve@chromium.org>
Reviewed-by: agrieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611698}

Bug: 909722
TBR=rogerta@chromium.org

Change-Id: I09108bc16d2f2e470b90fa8a1ff602eaea36087d
Reviewed-on: https://chromium-review.googlesource.com/c/1353959Reviewed-by: Tim Schumann <tschumann@chromium.org>
Commit-Queue: Tim Schumann <tschumann@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611697}

Channels are uint32_t in the javascript API there is no need for them
to be index as 64 bit integers.

BUG=879657

Change-Id: I21d2d0568a7cffe3cb275df11f642b9222f29c1d
Reviewed-on: https://chromium-review.googlesource.com/c/1349463Reviewed-by: Chrome Cunningham <chcunningham@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611696}

base::AssertBlockingAllowedDeprecated is deprecated in favor of
ScopedBlockingCall, which serves as a precise annotation of
the scope that may/will block.

Please 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: The call might block (e.g. file I/O that might hit in memory cache).
      WILL_BLOCK: The call will definitely block (e.g. cache already checked and now pinging
        server synchronously).
    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().
  - Calls to blocking //base APIs don't need to be annotated
    with ScopedBlockingCall. All blocking //base APIs (e.g. base::ReadFileToString, base::File::Read,
    base::SysInfo::AmountOfFreeDiskSpace, base::WaitableEvent::Wait, etc.) have their
    own internal annotations.

Refer to the top-level CL if necessary :
https://chromium-review.googlesource.com/c/chromium/src/+/1338391

Please CQ if LGTY!

This CL was uploaded by git cl split.

R=davidben@chromium.org

Bug: 903957
Change-Id: I7264546a54917ab0f7be6931219aad84091582aa
Reviewed-on: https://chromium-review.googlesource.com/c/1338486Reviewed-by: David Benjamin <davidben@chromium.org>
Commit-Queue: Etienne Pierre-Doray <etiennep@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611695}

Type was a char but should be a char[]

BUG=909692

Change-Id: I2151ab95a0ec0bbefd913f32de1b3e4d51cce6f8
Reviewed-on: https://chromium-review.googlesource.com/c/1354058Reviewed-by: Ryan Sleevi <rsleevi@chromium.org>
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611694}

Note that the CL is able to use gaia IDs from AccountInfo, rather than hardcode them.

BUG=903878

Change-Id: I03dd2f0bd271e969be00aa23005a6bd8960062e0
Reviewed-on: https://chromium-review.googlesource.com/c/1351157
Commit-Queue: Antonio Gomes <tonikitoo@igalia.com>
Reviewed-by: Colin Blundell <blundell@chromium.org>
Reviewed-by: Varun Khaneja <vakh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611693}

Change OnDisplayMetricsChanged to create new ManagedDisplayInfo for
display if OnDisplayAdded was never called for the display.
This is needed for the initial display on cast.

Bug: 896710
Test: None
Change-Id: I3b7d4829874b61b2115d25071a0de7bb74dba246
Reviewed-on: https://chromium-review.googlesource.com/c/1329859
Commit-Queue: Daniel Nicoara <dnicoara@chromium.org>
Reviewed-by: Daniel Nicoara <dnicoara@chromium.org>
Reviewed-by: Luke Halliwell <halliwell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611692}

Merge internal change: 223015666
Merge internal change: 223024889
Merge internal change: 223044144

R=rch@chromium.org

Change-Id: I83e3a5662499e716bd02698fd95488edc14593b3
Reviewed-on: https://chromium-review.googlesource.com/c/1351102
Commit-Queue: Victor Vasiliev <vasilvv@chromium.org>
Reviewed-by: Ryan Hamilton <rch@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611691}

This is in preparation for supporting manual interactions on testdriver.
By setting this field to true, unimplemented APIs will fail early rather
than waiting for user input (and timing out).

https://github.com/web-platform-tests/wpt/pull/11173

Change-Id: Ie409b683755358fb7978989bf3894e7b45b05239
Reviewed-on: https://chromium-review.googlesource.com/c/1352571
Commit-Queue: Philip Jägenstedt <foolip@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611690}

MessageLoop will go away, eventually.

BUG=891670

Change-Id: I6d254d90004514c867f66f3f49465a25c717a212
Reviewed-on: https://chromium-review.googlesource.com/c/1352754Reviewed-by: Martin Šrámek <msramek@chromium.org>
Commit-Queue: Carlos Caballero <carlscab@google.com>
Cr-Commit-Position: refs/heads/master@{#611689}

Bug: 903276
Change-Id: Id679d9ae73535fa4f5f168c2745cdd65991c66cc
Reviewed-on: https://chromium-review.googlesource.com/c/1352311
Commit-Queue: Tatiana Gornak <melandory@chromium.org>
Reviewed-by: Mohamed Amir Yosef <mamir@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611688}

Reland "[TaskScheduler]: Migrate off of ScopedAllowWait in /base/profiler/stack_sampling_profiler.cc"

This is a reland of 50b50793

This CL changes ScopedAllowBaseSyncPrimitives to ScopedAllowBaseSyncPrimitivesOutsideBlockingScope
in StackSamplingProfiler.

Original change's description:
> [TaskScheduler]: Migrate off of ScopedAllowWait in /base/profiler/stack_sampling_profiler.cc
>
> base::ThreadRestrictions::ScopedAllowWait is deprecated in favor of its more
> explicit counterpart.
>
> It should have been replaced by :
>  * base::ScopedAllowBaseSyncPrimitivesForTesting in test files.
>  * base::ScopedAllowSyncPrimitives in non-test files
>  * base::ScopedAllowSyncPrimitivesOutsideBlockingScope when it's used on threads
>    that don't allow blocking
> The last one is strongly frowned upon but this CL aims to document existing
> behavior rather than address it. Owners are encouraged to follow-up by fixing
> unnecessary waits and more particularly unnecessary waits
> outside-blocking-scope.
>
> Note: The non-for-testing versions require friend'ing in thread_restrictions.h
> but care was taken to add these friends ahead of git cl split (since it wasn't
> possible to do a line-by-line associated CL split).
> Refer to the top-level CL if necessary :
> https://chromium-review.googlesource.com/c/chromium/src/+/1288533
>
> Please CQ if LGTY!
>
> This CL was uploaded by git cl split.
>
> R=wittman@chromium.org
>
> Bug: 766678
> Change-Id: I2c45612b77a49ca5720da95093b0cdd8845b6f03
> Reviewed-on: https://chromium-review.googlesource.com/c/1325191
> Reviewed-by: Mike Wittman <wittman@chromium.org>
> Commit-Queue: Mike Wittman <wittman@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#606478}

Bug: 766678, 907177
Change-Id: I45b48e57040721e5ff3c2bdaac62237ed7ae429e
Reviewed-on: https://chromium-review.googlesource.com/c/1349633Reviewed-by: Mike Wittman <wittman@chromium.org>
Reviewed-by: François Doray <fdoray@chromium.org>
Commit-Queue: Etienne Pierre-Doray <etiennep@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611687}

The code previously looked like this:

  #if defined(COMPILER_GCC) && defined(_FORTIFY_SOURCE)
      if (!__builtin_constant_p(dst_end - dst) || (!(dst_end - dst)))
        memset(dst, val, dst_end - dst);
  #else
      memset(dst, val, dst_end - dst);
  #endif

The #ifdef was added a long time ago, in http://crrev.com/7728f5076b20 with the
motivation:

> There is a warning in memset in glibc that gets triggered through a
> warndecl when the fill-value of memset is a non-zero constant and the
> size is zero. This warning is enabled when building with
> -D_FORTIFY_SOURCE=2. This patch fixes the warning.

The idea was presumably to skip the memset if the size is a constant zero.
However, that's not what the code is doing. It's skipping the memset if the
size is constant *non-zero*.

How did this ever work?

I don't know about GCC, but until recently, Clang would not return true for the
__builtin_constant_p expression, so the memset would always run. However, Clang
gained support for this in r347417, and now webkit_unittests started failing in
builds that use FORTIFY_SOURCE.

The desired code would be:

  if (!__builtin_constant_p(dst_end - dst) || (dst_end - dst != 0))
    memset(dst, val, dst_end - dst);

But since I couldn't reproduce any warning about memset getting called with
zero size, I think it's better to drop the whole thing and simplify the code.

Bug: 908372
Change-Id: I166b88af27ca8beacba746892d5fde09ecf1c326
Reviewed-on: https://chromium-review.googlesource.com/c/1352363
Commit-Queue: Hans Wennborg <hans@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611686}

This patch adds the serial number to base::SysInfo::HardwareInfo on
Windows only, where it represents the BIOS serial number. This is
grabbed through a WMI call.

Other platforms will follow.

Bug: 907518
Change-Id: I1b2b23c00cda286f325a0a09722dbfc5e974eb77
Reviewed-on: https://chromium-review.googlesource.com/c/1346869Reviewed-by: François Doray <fdoray@chromium.org>
Reviewed-by: Robert Liao <robliao@chromium.org>
Reviewed-by: Roger Tawa <rogerta@chromium.org>
Commit-Queue: Georges Khalil <georgesak@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611685}

According to the flakiness dashboard it got flaky on all platforms except Mac.

TBR=lazyboy@chromium.org

Bug: 909570
Change-Id: I404a5d2ba392aa521fdf99c6892580f208086775
Reviewed-on: https://chromium-review.googlesource.com/c/1352193Reviewed-by: Tim Schumann <tschumann@chromium.org>
Commit-Queue: Tim Schumann <tschumann@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611684}

This CL moves the existing AutofillDataItem to legacy and creates a new
item compatible with UITableView.

Bug: 894791
Change-Id: Id3d7af497b08e99d8977e2f77385ea5e55f5c22b
Reviewed-on: https://chromium-review.googlesource.com/c/1350953
Commit-Queue: Gauthier Ambard <gambard@chromium.org>
Reviewed-by: Chris Lu <thegreenfrog@chromium.org>
Reviewed-by: Sergio Collazos <sczs@chromium.org>
Reviewed-by: Rohit Rao <rohitrao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611683}

Bug: 907720
Change-Id: Id3ec824af0023ba9fa4bb053717741c345c15b45
Reviewed-on: https://chromium-review.googlesource.com/c/1352052Reviewed-by: Ken Rockot <rockot@google.com>
Commit-Queue: kylechar <kylechar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611682}

https://android.googlesource.com/platform/external/perfetto.git/+log/af0c7c5e6e24..f16618125056


git log af0c7c5e6e24..f16618125056 --date=short --no-merges --format='%ad %ae %s'
2018-11-28 primiano@google.com Merge "Add support for periodic flushes"


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

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: I69643914963df59545d102d6588dd694fe6df37b
Reviewed-on: https://chromium-review.googlesource.com/c/1351486Reviewed-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@{#611681}

TBR=yosin@chromium.org

Bug: 909694
Change-Id: Ie6fd36ef024ce524152d5b718fbbc848b1735f05
Reviewed-on: https://chromium-review.googlesource.com/c/1353958
Commit-Queue: Tim Schumann <tschumann@chromium.org>
Reviewed-by: Tim Schumann <tschumann@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611680}

This is a reland of 30e1dd18

Adding feature flags to slimnav.
Revert bug: https://bugs.chromium.org/p/chromium/issues/detail?id=908970

Original change's description:
> [ios] add credit card test for manual fallback
>
> Also adds AutofillManualFallbackPhaseTwo to test bots.
>
> Bug: 845472
> Change-Id: I6bd05781c09c24c0768e24acfe59efa7ce1da05d
> Reviewed-on: https://chromium-review.googlesource.com/c/1337347
> Reviewed-by: Rohit Rao <rohitrao@chromium.org>
> Reviewed-by: Ben Pastene <bpastene@chromium.org>
> Reviewed-by: Javier Ernesto Flores Robles <javierrobles@chromium.org>
> Commit-Queue: David Jean <djean@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#611171}

TBR=rohitrao@chromium.org

Bug: 845472,908970
Change-Id: I2cc0cddf0be8cea447f45f69457afbe19c840f29
Reviewed-on: https://chromium-review.googlesource.com/c/1352328
Commit-Queue: Javier Ernesto Flores Robles <javierrobles@chromium.org>
Reviewed-by: Javier Ernesto Flores Robles <javierrobles@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611679}

So the user doesn’t unlock a card through CVC just to be told that it cannot be injected in current field.

Bug: 908789
Change-Id: Ie255d36f794c94d90b0fd1e01bf80d608ef757f6
Reviewed-on: https://chromium-review.googlesource.com/c/1352759
Commit-Queue: David Jean <djean@chromium.org>
Reviewed-by: Javier Ernesto Flores Robles <javierrobles@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611678}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/80526a9b..94c524df

Please follow these instructions for assigning/CC'ing issues:
https://github.com/v8/v8/wiki/Triaging%20issues

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com

Change-Id: I59aac4c65547d1d8876347797ae400dff8a512e2
Reviewed-on: https://chromium-review.googlesource.com/c/1352984Reviewed-by: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#611677}

This CL makes sure that the animation when the Switch to Open Tab button
is used is only triggered when the TabStrip isn't shown.

Bug: 908875,908876,908878
Change-Id: I04f4f71ca2a78c62fa99a860aa0baa8fdf012290
Reviewed-on: https://chromium-review.googlesource.com/c/1352787Reviewed-by: Olivier Robin <olivierrobin@chromium.org>
Commit-Queue: Gauthier Ambard <gambard@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611676}

This CL adds support for Dynamic Type in the AutofillEditItem.

Bug: 894791
Change-Id: I1e25084fed4cb176b332fc7fa7e4af0e7957323c
Reviewed-on: https://chromium-review.googlesource.com/c/1346454
Commit-Queue: Gauthier Ambard <gambard@chromium.org>
Reviewed-by: Olivier Robin <olivierrobin@chromium.org>
Reviewed-by: Chris Lu <thegreenfrog@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611675}

The initial implementation of this histogram used 0 as the default
setting. This will incorrectly count cases where the flag is missing as
'animation disabled'. This CL fixes this by splitting the default case
into its own enum. In order to preserve correct data, the old histogram
is obsoleted and a new histogram is created.

Bug: 722548
Change-Id: I031ca38cf70ddc8b51c9a150f31e25a305b9fc7a
Reviewed-on: https://chromium-review.googlesource.com/c/1351273Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611674}

Convert T*, U* class allocations from new to MakeGarbageCollected

Bug: 757708
Change-Id: Ib5c347738f538b42019314a7e2ce65b230d840e2
Reviewed-on: https://chromium-review.googlesource.com/c/1352073
Commit-Queue: Keishi Hattori <keishi@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611673}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/e9e2ac7b3cbb..62103075707c


Created with:
  gclient setdep -r src-internal@62103075707c

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: Ia1987b77d0f28f5887be1f88625e3de808f6c847
Reviewed-on: https://chromium-review.googlesource.com/c/1352502Reviewed-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@{#611672}

TBR: alemate@chromium.org
Bug: 854101
Change-Id: I0119223034d6399dfd6fd50d3fb0e4821c356f65
Reviewed-on: https://chromium-review.googlesource.com/c/1243195
Commit-Queue: Denis Kuznetsov <antrim@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Sergey Poromov <poromov@chromium.org>
Reviewed-by: Alexander Hendrich <hendrich@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611671}

https://dawn.googlesource.com/dawn.git/+log/cf714a81c86e..596d6fe00db7


git log cf714a81c86e..596d6fe00db7 --date=short --no-merges --format='%ad %ae %s'
2018-11-28 cwallez@chromium.org Result: Fix documentation and a typo


Created with:
  gclient setdep -r src/third_party/dawn@596d6fe00db7

The AutoRoll server is located here: https://autoroll.skia.org/r/dawn-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_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
TBR=cwallez@chromium.org

Change-Id: Iefbca39f6f500032f47b95bd5d0e051e887c24a2
Reviewed-on: https://chromium-review.googlesource.com/c/1352501Reviewed-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@{#611670}

The AwSettingsTest.testCacheMode is now passing due to:
https://chromium-review.googlesource.com/c/chromium/src/+/1339720

BUG=893570,841556
TBR=ntfschr@chromium.org,cduvall@chromium.org

Cq-Include-Trybots: master.tryserver.chromium.android:android_mojo

Change-Id: Icd210dcfaf8d5830f1128834e3ea16d58c179569
Reviewed-on: https://chromium-review.googlesource.com/c/1352786
Commit-Queue: Tim Volodine <timvolodine@chromium.org>
Reviewed-by: Tim Volodine <timvolodine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611669}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/ff43a0af6b51..e9e2ac7b3cbb


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

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: Id63d991882e94ca5b1bf999fa9bafd000f8d7b2e
Reviewed-on: https://chromium-review.googlesource.com/c/1352499Reviewed-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@{#611668}