GitLab

Spellchecker has a heuristic that, if the bounding box of an editing host
is not in viewport, don't check anything in the editing host.

This is wrong as there might still be descendants of the editing host
inside the viewport. Hence, this patch removes the heuristic.

Bug: 768231
Change-Id: I22995b365c6a3e10eedb76a4868746f09261e733
Reviewed-on: https://chromium-review.googlesource.com/903265
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534848}

This reverts commit 036ea24b.

Reason for revert: Causing build failure on Cast Audio Linux:
https://ci.chromium.org/buildbot/chromium.linux/Cast%20Audio%20Linux/8575

Original change's description:
> Introduce WebRtcRemoteEventLogManager
> 
> WebRtcRemoteEventLogManager is a member of WebRtcEventLogManager, in
> charge of managing remote-bound WebRTC event logs:
> * Store remote-bound log files locally, persisting them between session
>   of Chrome.
> * Uploading them when permissible (when no active peer connections are
>   present, with which the upload's increased bandwidth utilization might
>   interfere).
> * Purge remote-bound log files from local disk once an upload attempt
>   was made, regardless of whether it was successful. (Otherwise, we might
>   end up attempting multiple times, wasting bandwidth on an upload that
>   always fails after a non-trivial amount of data was pushed upstream.
>   More refined retry behavior is to be added at a later stage.)
> 
> Upcoming related work:
> * Actual implementation of the uploader (this CL deals with managing the
>   files to be uploaded, and the timing of the upload).
> * Implementation of the JS hooks.
> 
> Bug: 775415
> Change-Id: Ib5ee6081ca13d85cb8a3f38d6462bbd61a99dcae
> Reviewed-on: https://chromium-review.googlesource.com/891219
> Commit-Queue: Elad Alon <eladalon@chromium.org>
> Reviewed-by: Avi Drissman <avi@chromium.org>
> Reviewed-by: Guido Urdaneta <guidou@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#534826}

TBR=avi@chromium.org,guidou@chromium.org,terelius@chromium.org,eladalon@chromium.org

Change-Id: I2bc87f1002eac26f4c77bc5082be45db80b0449d
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 775415
Reviewed-on: https://chromium-review.googlesource.com/905826Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534847}

We're shipping the kResourcesBeforeDCL in M65, so remove the other
behaviors now that we've branched.

Bug: 513459
Change-Id: Id5b5f0bac5c35c0e3a3f574a4695858916c40283
Reviewed-on: https://chromium-review.googlesource.com/875261Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Jesse Doherty <jwd@chromium.org>
Commit-Queue: Nate Chapin <japhet@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534846}

This reverts commit 022ed8ae.

Reason for revert: this broke Cast Audio bots, https://ci.chromium.org/buildbot/chromium.linux/Fuchsia%20ARM64%20Cast%20Audio/4367

Original change's description:
> RenderProcessHost exiting is an implicit PeerConnection removal
> 
> When a RenderProcessHost exits clearly or crashes, all of its
> PeerConnections should be considered as removed.
> 
> Bug: 775415, 805398, 808402
> Change-Id: I223e6e867758ef05d896608fbdcc3bc824238dd8
> Reviewed-on: https://chromium-review.googlesource.com/899348
> Commit-Queue: Elad Alon <eladalon@chromium.org>
> Reviewed-by: Guido Urdaneta <guidou@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#534840}

TBR=guidou@chromium.org,terelius@chromium.org,eladalon@chromium.org

Change-Id: I6f33dded2bba23f471c73495518fdded3ccbc3dc
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 775415, 805398, 808402
Reviewed-on: https://chromium-review.googlesource.com/905638Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Commit-Queue: Andrey Kosyakov <caseq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534845}

https://webrtc.googlesource.com/src.git/+log/29f14322d13e..dffead8835d1

$ git log 29f14322d..dffead883 --date=short --no-merges --format='%ad %ae %s'

Created with:
  roll-dep src/third_party/webrtc


The AutoRoll server is located here: https://webrtc-chromium-roll.skia.org

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=master.tryserver.chromium.linux:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng;master.tryserver.chromium.win:win-msvc-dbg
TBR=webrtc-chromium-sheriffs-robots@google.com

Change-Id: I193181e14cd93321906bc4fde31c453a65439a5a
Reviewed-on: https://chromium-review.googlesource.com/905628
Commit-Queue: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#534844}

In component builds, SQLite's API methods are exported from the
chromium_sqlite component, which means they are visible to the dynamic
library loader. This opens up the following possibilities:

1) A system library calls into our SQLite instead of calling into the
   system's SQLite library which it was built against. The patches in
   our SQLite version lead to different behavior from the system's
   SQLite, which can cause subtle failures. This happens if the dynamic
   library loader resolves the system library's symbol imports with our
   SQLite's exported symbols.
2) A system library loads the system SQLite, and we end up calling into
   it, instead of calling into our version of SQLite. This happens if
   the dynamic library loader resolves our symbol imports with the
   system's SQLite library.

Both possibilities above lead to the possibility that the component
build will behave differently from the release build, in subtle and
potentially non-deterministic ways. This is not a purely academic
concern. https://crbug.com/807487 happened because we use NSS on Linux,
and NSS invokes SQLite via a complex plugin system. On non-component builds,
NSS (a system library) loads and uses the system version of SQLite. On
component builds, NSS ends up using our SQLite.

This CL fixes the problem by adding a chrome_ prefix to all the symbols
exported from SQLite3. In C++ libraries, namespaces can make prefixing
easy. Unfortunately, SQLite is a C library, so the prefixing is fairly
heavy-handed. A high-level overview of the approach follows:

* An extract_sqlite_api Python script reads SQLite's header, extracts
  the names of all exported symbols, and writes a header file consisting
  of renaming preprocessor macros, e.g.
      #define sqlite3_init chrome_sqlite3_init
  David Benjamin <davidben@chromium.org> designed the approach and wrote
  the original version of the script.
* The script that we use to generate SQLite's amalgamation now also
  invokes the extract_sqlite_api script described above, and saves the
  output to amalgamation/rename_exports.h.
* The SQLite component exposes an sqlite3.h header that must be used by
  all SQLite3 users in Chromium. This header now #includes
  rename_exports.h (containing the renaming preprocessor macros) before
  #including amalgamation/sqlite3.h.
* sqlite3.c (the main output of the amalgamation process) does not
  #include "sqlite3.h". However, in order to facilitate autoconf builds,
  it does #include a "config.h", if a certain preprocessor define
  exists. We abuse that define to have sqlite.c always load config.h,
  and have config.h load our rename_exports.h.

This CL also adds a PRESUBMIT.py that runs unit tests for the
extract_sqlite_api Python script, which ensures that the script will not
break accidentally. Both the unit tests and the PRESUBIMT script are
inspired from //tools/vim.

Bug: 807093, 807487
Change-Id: If3868ba119ffd4ccbb06d1a6fcd4cc2ecd9ef2ae
Reviewed-on: https://chromium-review.googlesource.com/898549Reviewed-by: Chris Mumford <cmumford@chromium.org>
Commit-Queue: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534843}

Move deinitialisation of TaskQueue's OnTaskStartedHandler and
OnTaskCompletedHandler to main thread and avoid race condition.

R=skyostil@chromium.org
BUG=809424

Change-Id: I1c67ceead20e9b8463de054ce3040314d4fee002
Reviewed-on: https://chromium-review.googlesource.com/904605Reviewed-by: Sami Kyöstilä <skyostil@chromium.org>
Commit-Queue: Alexander Timin <altimin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534842}

Debugging code to track app terminiating while loading
user profile is added in M63. Two milestones has passed
and the problem no longer happens. Hence removing it.

Bug: 717585
Change-Id: I7df6ea9c4ab9809e4a86b36136aa69e1b03a5ead
Reviewed-on: https://chromium-review.googlesource.com/905063Reviewed-by: Achuith Bhandarkar <achuith@chromium.org>
Commit-Queue: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534841}

When a RenderProcessHost exits clearly or crashes, all of its
PeerConnections should be considered as removed.

Bug: 775415, 805398, 808402
Change-Id: I223e6e867758ef05d896608fbdcc3bc824238dd8
Reviewed-on: https://chromium-review.googlesource.com/899348
Commit-Queue: Elad Alon <eladalon@chromium.org>
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534840}

This change removes the use of transparency on the location bar when
modern is enabled. This simplifies the logic required to run animations
and fixes a flickering issue when entering and exiting the tab switcher.

This change also changes the background color of the asset to white.
This allows it to be easily tinted which will also be required for the
composited version.

BUG=803098,803091

Change-Id: Ia56660da21f615840f6ea2902a3252b8809d337f
Reviewed-on: https://chromium-review.googlesource.com/899772
Commit-Queue: Matthew Jones <mdjones@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534839}

In the current implementation, the copy request is handled by
DelegatedFrameHost::RequestCopyOfOutput, which add copy request to
the compositor frame of the browser. After this patch, the copy
request will be handled by the
CompositorFrameSinkSupport:RequestCopyOfSurface which adds the
copy request to the surface where the copy request needs to be make.

TEST: exiting test cases on copy requests should cover all the usage

Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel
Change-Id: I5c0b4572a7b8ed5fce0f5ee10f5d4dd982912e0a
Reviewed-on: https://chromium-review.googlesource.com/881548Reviewed-by: Yuri Wiitala <miu@chromium.org>
Reviewed-by: ccameron <ccameron@chromium.org>
Commit-Queue: Yi Xu <yiyix@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534838}

BUG=

Change-Id: I5372417f961594c3907ebde5f38a1512c83f189d
Reviewed-on: https://chromium-review.googlesource.com/903182Reviewed-by: Maria Khomenko <mariakhomenko@chromium.org>
Commit-Queue: Maria Khomenko <mariakhomenko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534837}

- keep_alive ensures we do not exit/shutdown.
- drag'n'drop disables drag and drop.

Bug: 784495
Change-Id: I65525cf5065db48bc14db93af3f3b6e86bc715c7
Reviewed-on: https://chromium-review.googlesource.com/871835
Commit-Queue: Jacob Dufault <jdufault@chromium.org>
Reviewed-by: Achuith Bhandarkar <achuith@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534836}

Reporte crash can happen if |ContentViewCore.onRotationChanged| is called
after CVC is destroyed, therefore mWebContents is set to null. Added
null check against the variable to prevent crash.

Bug: 808971
Change-Id: I7719d2d0c26b36b94eeff406d655512111e58c2d
Reviewed-on: https://chromium-review.googlesource.com/903342Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534835}

Implements WriteFile in SmbFileSystem using TempFileManager.

Bug: chromium:757625
Change-Id: I176079aca1bb752f628c86942f2ee89b46c19729
Reviewed-on: https://chromium-review.googlesource.com/894983Reviewed-by: Zentaro Kavanagh <zentaro@chromium.org>
Commit-Queue: Allen Vicencio <allenvic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534834}

https://chromium.googlesource.com/catapult.git/+log/e6e84629dbe5..874bc7c4eabb

$ git log e6e84629d..874bc7c4e --date=short --no-merges --format='%ad %ae %s'
2018-02-06 charliea Disable all CPU tracing agent integration tests on Windows

Created with:
  roll-dep src/third_party/catapult


The AutoRoll server is located here: https://catapult-roll.skia.org

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=master.tryserver.chromium.android:android_optional_gpu_tests_rel
TBR=sullivan@chromium.org

Change-Id: I8468b18bb72c450df3d79595fa2788204d52d857
Reviewed-on: https://chromium-review.googlesource.com/905460Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#534833}

This bumps the experimental builder to 50% and also
marks it as "compile_only", which means that we don't
include any debug symbols (this speeds up the build).

R=jbudorick@chromium.org
BUG=694033

Change-Id: I73713462395bcc360172883aa898af72c8a8ecd7
Reviewed-on: https://chromium-review.googlesource.com/898366Reviewed-by: John Budorick <jbudorick@google.com>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Dirk Pranke <dpranke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534832}

Fixes a bug where memory-infra tracing would count private_dirty memory
also as shared_dirty memory in a certain detail view (but not in aggregates).
Record a memory-infra trace as described on
https://chromium.googlesource.com/chromium/src/+/lkcr/docs/memory-infra/
then click a memory dump, click e.g. "Browser" in the Analysis view,
scroll down, and click the triangle toggle next to Total and then
Native heap. Before this change, entries with "Private dirty" != 0
would always have the same value in the "Shared dirty" column (but
not the other way round).  After this change, at most one of
the two columns is != 0.

Actually turning on the warning is blocked on an issue in protobuf
(see crbug.com/809157), so this will happen in a future CL.

TBR=sky

Bug: 177475
Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: I663f225f817accd5ee7319e33e2779aafd9c85c6
Reviewed-on: https://chromium-review.googlesource.com/902065
Commit-Queue: Nico Weber <thakis@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Erik Chen <erikchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534831}

Paper-button-light doesn't support the alt property, so aria-label should be used instead.
R=dmazzoni@chromium.org, fukumi@chromium.org

Tested: Manually using Jaws
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I8db2a1c399f41fafc577634062df37972a80a816
Reviewed-on: https://chromium-review.googlesource.com/890778Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Reviewed-by: Hector Carmona <hcarmona@chromium.org>
Commit-Queue: Nektarios Paisios <nektar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534830}

This CL replaces |getSelectPopupForTesting| with the one that simply
returns its visibility (showing or hidden), which is enough for
testing purposes. It helps CVC not return/expose non-public class
when moved to content_public https://crrev.com/c/900884

Bug: 807155
Change-Id: I8dbdace17ace9068ee7807dfa1abf7ac85f4c357
Reviewed-on: https://chromium-review.googlesource.com/902982Reviewed-by: Bo <boliu@chromium.org>
Reviewed-by: Changwan Ryu <changwan@chromium.org>
Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534829}

https://skia.googlesource.com/skia.git/+log/2fb7c8aef57e..744160486520

$ git log 2fb7c8aef..744160486 --date=short --no-merges --format='%ad %ae %s'
2018-02-06 angle-skia-autoroll Roll skia/third_party/externals/angle2/ bfeed4ddf..ca5c10598 (1 commit)
2018-02-06 reed Can't correctly call computeFastBounds on maskfilter w/ device geo
2018-02-05 halcanary SkQP: download_model complains when files.checksum is missing
2018-02-06 angle-skia-autoroll Roll skia/third_party/externals/angle2/ 2d1c0a2b8..bfeed4ddf (1 commit)
2018-02-06 stephana Remove ConstraintLayout from skqp app
2018-02-06 bsalomon Revert "move GrColor.h to private, IWYU"
2018-02-06 skcms-skia-autoroll Roll skia/third_party/externals/skcms/ 6fd3bac65..2908ce856 (1 commit)

Created with:
  roll-dep src/third_party/skia


The AutoRoll server is located here: https://autoroll.skia.org

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=master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
TBR=bsalomon@chromium.org

Change-Id: I58a89fe497e14f31153acb5f223423d8a4f9bd02
Reviewed-on: https://chromium-review.googlesource.com/905446
Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#534828}

Bug: 799074
Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_vr;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: I06c20525b10187804949ed9bed7485e483802d15
Reviewed-on: https://chromium-review.googlesource.com/903047Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Reviewed-by: David Dorwin <ddorwin@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534827}

WebRtcRemoteEventLogManager is a member of WebRtcEventLogManager, in
charge of managing remote-bound WebRTC event logs:
* Store remote-bound log files locally, persisting them between session
  of Chrome.
* Uploading them when permissible (when no active peer connections are
  present, with which the upload's increased bandwidth utilization might
  interfere).
* Purge remote-bound log files from local disk once an upload attempt
  was made, regardless of whether it was successful. (Otherwise, we might
  end up attempting multiple times, wasting bandwidth on an upload that
  always fails after a non-trivial amount of data was pushed upstream.
  More refined retry behavior is to be added at a later stage.)

Upcoming related work:
* Actual implementation of the uploader (this CL deals with managing the
  files to be uploaded, and the timing of the upload).
* Implementation of the JS hooks.

Bug: 775415
Change-Id: Ib5ee6081ca13d85cb8a3f38d6462bbd61a99dcae
Reviewed-on: https://chromium-review.googlesource.com/891219
Commit-Queue: Elad Alon <eladalon@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534826}

Since most tracing agents only care about receiving start/stop
tracing signals, a default implementation is provided for other
methods to reduce boilerplate code.

Bug: 808839
Change-Id: I4645add6e7e81a25d0e923c8afcdf8f5dc3a7a13
Reviewed-on: https://chromium-review.googlesource.com/868575
Commit-Queue: Ehsan Chiniforooshan <chiniforooshan@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Luis Hector Chavez <lhchavez@chromium.org>
Reviewed-by: oysteine <oysteine@chromium.org>
Reviewed-by: Charlie Andrews <charliea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534825}

It was missed in r533917.

Bug: 809381,808182
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I4b7d574e2a1f6b3522547def1b2c6615e974143a
Reviewed-on: https://chromium-review.googlesource.com/904851
Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org>
Reviewed-by: Hector Carmona <hcarmona@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534824}

Use GetPromisedUrlFromHeaderBlock() instead of GetUrlFromHeaderBlock()
for pushed HTTP/2 headers.

Remove dangerous GetDefaultUrlWithPath() and inline pushed URLs instead
in SpdyNetworkTransactionTests.

Pass URL from SpdySession to SpdyStream so that GetUrlFromHeaderBlock()
does not need to be called once more.

Change-Id: Ibc51015d20d0f5a3cf1431ad668feff1662a178a
Reviewed-on: https://chromium-review.googlesource.com/896808
Commit-Queue: Bence Béky <bnc@chromium.org>
Reviewed-by: Ryan Hamilton <rch@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534823}

Refer Sashi CL - https://codereview.chromium.org/2855943002/

Bug: 717665
Change-Id: If7a5214d05786f5959a5619dc727b68e6c462ec

Tried to start local demo, but sign-in is not working.

Change-Id: If7a5214d05786f5959a5619dc727b68e6c462ec8
Reviewed-on: https://chromium-review.googlesource.com/903057
Commit-Queue: Lakshmi Kumar Dabbiru <dlkumar@google.com>
Reviewed-by: Mathieu Perreault <mathp@chromium.org>
Reviewed-by: Jared Saul <jsaul@google.com>
Cr-Commit-Position: refs/heads/master@{#534822}

This increases the bot from 25->50% of the load, and since
the bots are compile only, turns symbols completely off, which
should speed things up.

R=jbudorick@chromium.org
BUG=777642

Change-Id: I43505426e665f7ade473db9ed46f172be94c1e5c
Reviewed-on: https://chromium-review.googlesource.com/898350Reviewed-by: Stephen Martinis <martiniss@chromium.org>
Reviewed-by: John Budorick <jbudorick@google.com>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Dirk Pranke <dpranke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534821}

I had this CL that implements animation specific UMA:
https://chromium-review.googlesource.com/c/chromium/src/+/636305
In particular, we record frame rate when there is main thread / compositor /
main thread compositable animations in this frame. However, the main
thread compositable animations is not calculated correctly in the above
CL. The result of that is a crash which is tracked in crbug.com/781305.
In order to solve the crash, we temporary disabled the main thread
compositable animation UMA in here:
https://chromium-review.googlesource.com/c/chromium/src/+/753405

Now it is time to re-enable that UMA. This is how we check whether an
animation is main thread compositable or not: we first check whether the
effects can start on compositor or not. For example, a transform animation
will be able to start on compositor. Then we check whether the target
element can start on compositor or not. If the target element is not
paint into its own backing, we know that this is due to a running
experiment.

The problem with the above logic is SVG element. For example, if we
have a transform animation on an SVG element, the effect can be started
on compositor but the SVG element cannot start on compositor. In order
to tell whether this is a main thread compositable, we have to exclude
the SVG element.

This CL fixed the problem. It re-enables a unit test and added another
test for SVG element.

Bug: 781305
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: I030f2e7d2061589ccb0a62f12744b1097855f2f7
Reviewed-on: https://chromium-review.googlesource.com/895409Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Commit-Queue: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534820}

Previously third_party/content_shell_fonts were used on Linux, but not
Android. Updated the scripts to use it instead of the the files provided
by Linux distro.

Bug: 787020
Change-Id: Idf71c65a45466682f25a23474dcc67925af59466
Reviewed-on: https://chromium-review.googlesource.com/903240Reviewed-by: Dominik Röttsches <drott@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Sergey Ulanov <sergeyu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534819}

This is a reland of 295cd31f.

Original change's description:
> [Nav Experiment] Update NavigationItem URL for location.replace.
> 
> location.replace changes the URL of WKBackForwardListItem. Update the
> URL of NavigationItem to that of the host WKBackForwardListItem upon
> access. It's done this way because location.replace cannot be reliably
> distinguished from normal navigations in either WKNavigationDelegate
> callback or URL KVO.
> 
> This fixes NavigationTestCase/testWindowLocationReplaceAndChangeHash.
> 
> Bug: 807428
> Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
> Change-Id: Iaef4ed5efd788283050b43a3b4e988311ec9cf76
> Reviewed-on: https://chromium-review.googlesource.com/894490
> Commit-Queue: Danyao Wang <danyao@chromium.org>
> Reviewed-by: Eugene But <eugenebut@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#533315}

Bug: 807428
Change-Id: I2f237fe6a03b38592eccf1adedcf8c5679552201
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Reviewed-on: https://chromium-review.googlesource.com/900103
Commit-Queue: Danyao Wang <danyao@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534818}

https://chromium-review.googlesource.com/c/chromium/src/+/902769

Adds missing <algorithm> include for std::min.

BUG=none

Change-Id: I1e4dd1ef72f9c28f5aa6836b8ac1a7fb1f532f47
Reviewed-on: https://chromium-review.googlesource.com/905204Reviewed-by: Mark Mentovai <mark@chromium.org>
Commit-Queue: Alexei Svitkine <asvitkine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534817}

TBR=anthonyvd

Bug: 809609
Change-Id: I5ed542e233feae2bc6c5faa34805837c7f0ee555
Reviewed-on: https://chromium-review.googlesource.com/905096Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Commit-Queue: Andrey Kosyakov <caseq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534816}

https://chromium.googlesource.com/angle/angle.git/+log/44dcb911c00e..bfeed4ddfcd6

$ git log 44dcb911c..bfeed4ddf --date=short --no-merges --format='%ad %ae %s'
2018-02-06 oetuaho Add a compiler perf test shader to stress traversers
2018-02-02 jie.a.chen Vulkan: Fix gcc compile error

Created with:
  roll-dep src/third_party/angle


The AutoRoll server is located here: https://angle-chromium-roll.skia.org

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=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
TBR=cwallez@chromium.org

Change-Id: Idb785881123594bea526ff1339a20ba97d01ef10
Reviewed-on: https://chromium-review.googlesource.com/905402
Commit-Queue: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#534815}

Enable the print button in the new print preview UI.

Bug: 773928
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I27a8b99e3ce23ebe718214c4eee0ab92e6b48713
Reviewed-on: https://chromium-review.googlesource.com/892399Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Commit-Queue: Rebekah Potter <rbpotter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534814}

This CL includes a group of minor fixes and improvements that will ease
the testing of Prefetching with limitless mode enabled:
* Fixes comments in PrefetchBackgroundTaskScheduler.
* Improves handling of invalid URLs and text output from
  OfflineInternalsUIMessageHandler.
* Improve debug logging in MetricsFinalizationTask.
* Use larger bundle size limit for GeneratePageBundleRequest in
  PrefetchNetworkRequestFactoryImpl when limitless mode is enabled.
* Complete TODO to make method private in SuggestedArticlesObserver.

Bug: 793109
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: Ic4c1931e6c8ab8f5bf2fdd8cfec8075f30a9b6cd
Reviewed-on: https://chromium-review.googlesource.com/869373
Commit-Queue: Carlos Knippschild <carlosk@chromium.org>
Reviewed-by: Tommy Li <tommycli@chromium.org>
Reviewed-by: Dmitry Titov <dimich@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534813}

Change:
Replace kOlderFolders with kFullscreenAppListFolders.

BUG=809324

Change-Id: Ib2f779fcd5e71a8e7a826c53b21ddaaf74126a22
Reviewed-on: https://chromium-review.googlesource.com/903412Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Weidong Guo <weidongg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534812}

Bug: chromium:757625
Change-Id: I0f68e43c7f9700d3d02d640d36c2d9a4523b4495
Reviewed-on: https://chromium-review.googlesource.com/894167Reviewed-by: Zentaro Kavanagh <zentaro@chromium.org>
Commit-Queue: Allen Vicencio <allenvic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534811}

content/browser/loader/loader_io_thread_notifier.cc has the following
include chain:
content/browser/frame_host/render_frame_host_impl.h
-> content/public/browser/content_browser_client.h
-> device/usb/public/mojom/chooser_service.mojom.h (generated header)

And so //content/browser needs a //device/usb/public/mojom dep.  This
was previously only added in //content/public/browser and could therefore
cause build flakiness.

Bug: 806965
Change-Id: I6d5254cd427fc6a6b1cfaefb26a2eb4056f62638
Reviewed-on: https://chromium-review.googlesource.com/903165Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Commit-Queue: Mostyn Bramley-Moore <mostynb@vewd.com>
Cr-Commit-Position: refs/heads/master@{#534810}

It does timeout sometimes on Win.

Bug: 667560
Change-Id: I2047340ce939414ce19b1ddc61d4423d35e12e2d
Reviewed-on: https://chromium-review.googlesource.com/904771Reviewed-by: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org>
Commit-Queue: Dmitry Gozman <dgozman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534809}