GitLab

https://chromium.googlesource.com/catapult.git/+log/767f070f1df4..6b8f67cc144c

$ git log 767f070f1..6b8f67cc1 --date=short --no-merges --format='%ad %ae %s'
2018-03-14 cjgrant VR: Remove UpdateTexturesAndSizes metric

Created with:
  roll-dep src/third_party/catapult
BUG=chromium:806886


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.


TBR=sullivan@chromium.org

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

Bug: 779637
Change-Id: Ib41fb81f13e40465f5ae56f10c86426207c17702
Reviewed-on: https://chromium-review.googlesource.com/981118Reviewed-by: Ned Nguyen <nednguyen@google.com>
Commit-Queue: Emily Hanley <eyaich@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546117}

TBR=maruel@chromium.org

Bug: 731360
Change-Id: I189644631ee8781f8590bc3dce95abf6849b766f
No-Try: True
Reviewed-on: https://chromium-review.googlesource.com/982099
Commit-Queue: Andrii Shyshkalov <tandrii@chromium.org>
Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
Reviewed-by: Marc-Antoine Ruel <maruel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546116}

Currently, I'm
hardcoding values for Android and returning 0 for all other platforms.
In a subsequent CL I'll pick the right icon size from the list provided
by the developer, based on this size.

TBR=peter@chromium.org

Bug: 813564
Change-Id: If1d302a7439f7533d1c5649cce7eb2d0bf5583bc
Reviewed-on: https://chromium-review.googlesource.com/968865
Commit-Queue: Anita Woodruff <awdf@chromium.org>
Reviewed-by: Anita Woodruff <awdf@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Martin Barbella <mbarbella@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546115}

The root cause of this was that a copy of the toolbar was being created
in fullscreen mode. It seems like having separate NSThemeFrame subclasses
for fullscreen and non-fullscreen is unsupported.

This change causes a regression by making the toolbar too large in
fullscreen mode; https://crbug.com/825968 was filed to address this.

Bug: 824757
Change-Id: I9d63a1646f5dbfd0666f367d1dc859359e91552f
Reviewed-on: https://chromium-review.googlesource.com/980600Reviewed-by: Sidney San Martín <sdy@chromium.org>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Commit-Queue: Leonard Grey <lgrey@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546114}

GCC's analogous command-line argument is -Wno-unused-local-typedefs, with an
's' at the end, and //build/config/compiler/BUILD.gn already passes it to
the compiler unconditionally when clang is not being used.

This CL prevents warnings in the GCC build that look like this:

    cc1plus: warning: unrecognized command line option ‘-Wno-unused-local-typedef’

Change-Id: Icec95a6d1cf3a4bcd4f3a0acb7f002850aa9f7af
Reviewed-on: https://chromium-review.googlesource.com/980942Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
Commit-Queue: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com>
Cr-Commit-Position: refs/heads/master@{#546113}

TBR=maruel@chromium.org

Bug: 807149
Change-Id: If98643d43b34edef6916eb6b669f4a98c2494018
No-Try: True
Reviewed-on: https://chromium-review.googlesource.com/982096Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
Reviewed-by: Marc-Antoine Ruel <maruel@chromium.org>
Commit-Queue: Andrii Shyshkalov <tandrii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546112}

Add "UsePdfCompositorServiceForTest" experiment to the field trial under
tests for all desktop platforms. It tests the new PDF generation service
which supports OOPIF printing.

BUG=824867

Change-Id: I808c8ed04509e5d6a6074d35b4d569f22c6c3e77
Reviewed-on: https://chromium-review.googlesource.com/981176Reviewed-by: Lei Zhang <thestig@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Wei Li <weili@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546111}

Issue 824772 is a potential cause of issue 818214. Report whether
devtools is in use to investigate if there could be other causes.

Bug: 818214
Change-Id: Ia714353016a65473e5926ce7cbea9f65058bb39d
Reviewed-on: https://chromium-review.googlesource.com/980585Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Commit-Queue: Kevin McNee <mcnee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546110}

Bug: 747349
Change-Id: Ied3abb6f93a391bf6581275efbd96b3763413de9
Reviewed-on: https://chromium-review.googlesource.com/976540Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Reviewed-by: Achuith Bhandarkar <achuith@chromium.org>
Commit-Queue: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546109}

Async Tracing (using TraceEvent.startAsync/finishAsync) used to be a
no-op if native has not loaded yet. Now they are deferred to
EarlyTraceEvent and stored on the java side until native is loaded then
are sent ala TraceEvent.begin/end

Bug: 822816
Change-Id: I612d03213b832cc6d381d98203bc5c9aca4ab12b
Reviewed-on: https://chromium-review.googlesource.com/971763Reviewed-by: dsinclair <dsinclair@chromium.org>
Reviewed-by: Dmitry Skiba <dskiba@chromium.org>
Reviewed-by: agrieve <agrieve@chromium.org>
Commit-Queue: Mohamed Heikal <mheikal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546108}

https://skia.googlesource.com/skia.git/+log/2ef4525daf15..33f02edb14bb

$ git log 2ef4525da..33f02edb1 --date=short --no-merges --format='%ad %ae %s'
2018-03-27 robertphillips Switch DDL rendering to be a Via in DM (take 2)

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;luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
TBR=mtklein@chromium.org

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

BUG=814587

Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: Ia607af378e66fa6c9b62dae780b51931dcef7184
Reviewed-on: https://chromium-review.googlesource.com/981894Reviewed-by: Rohit Rao <rohitrao@chromium.org>
Commit-Queue: Peter Lee <pkl@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546106}

Embedded devices have limited storage capacity generally. But current default
hard coded value is 5MB per an origin in application cache storage. But embedders
often want to reduce the default hard coded value per an origin as well. So it would
be good if we give the power them to set the maximum cache size per an origin for
application cache through the command line.

Bug: 824619
Change-Id: I078365ec412834c024a92ff5ec4ad5d00452e2a7
Reviewed-on: https://chromium-review.googlesource.com/979877
Commit-Queue: Gyuyoung Kim <gyuyoung.kim@lge.com>
Reviewed-by: Antoine Labour <piman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546105}

This is a reland of d260e9cf

It was reverted because of crbug.com/824716, these weren't new crashes
but known crashes mislabeled as a fallout of this change.
http://cl/190471699 fixes the crash backend to not rely on
"content::BrowserThreadImpl::IOThreadRun" being in the signature.

Only diff in this CL is to use base::debug::Alias() in methods that we
don't want optimized (i.e. IOThreadRun) out as CHECK_GT was seen as
optimized out in some of the reported crashes (even though the same
pattern as before was used by this CL..?)

Original change's description:
> Refactor BrowserThreadImpl, BrowserProcessSubThread, and BrowserMainLoop
>
> This brings back the invariant that BrowserThread::IO isn't available
> before BrowserMainLoop::CreateThreads(). This was broken to fix issue
> 729596 to bring up the thread earlier for ServiceManager but it is
> important that code that posts to BrowserThread::IO statically have an
> happens-after relationship to BrowserMainLoop::CreateThreads(). Exposing
> it statically earlier put that invariant at risk.
>
> Thankfully fixing issue 815225 resulted in finally reaching the long
> sought goal of only having BrowserThread::UI/IO. Now that the IO thread
> is also kicked off before it's named statically, BrowserThreadImpl no
> longer needs to be a base::Thread, hence this refactoring.
>
> Before this CL:
>  * BrowserThreadImpl was a base::Thread
>    (could be a fake thread if SetMessageLoop was used)
>  * BrowserProcessSubThread was a BrowserThreadImpl
>    (performed a bit more initialization)
>  * BrowserProcessSubThread was only used in production (in
>    BrowserMainLoop)
>  * BrowserThreadImpl was used for fake threads (BrowserMainLoop for
>    BrowserThread::UI) and for testing (TestBrowserThread(Impl)).
>  * BrowserThreadImpl overrode Init/Run/CleanUp() from base::Thread to
>    perform some sanity checks as well as drive IOThread's Delegate (ref.
>    BrowserThread::SetIOThreadDelegate())
>  * BrowserProcessSubThread re-overrode Init/Run/CleanUp() to perform
>    per-thread //content initialization (tests missed out on that per
>    TestBrowserThread bypassing BrowserProcessSubThread by directly
>    subclassing BrowserThreadImpl).
>
> With this CL:
>  * BrowserThreadImpl is merely a scoped object that binds a provided
>    SingleThreadTaskRunner to a BrowserThread::ID.
>  * BrowserProcessSubThread is a base::Thread and performs all of the
>    initialization and cleanup specific to //content (this means it now
>    also manages BrowserThread::SetIOThreadDelegate())
>  * BrowserProcessSubThread can be brought up early before being bound to
>    a BrowserThread::ID (BrowserMainLoop handles that through
>    BrowserProcessSubThread ::RegisterAsBrowserThread())
>
> Unfortunate exceptions required for this CL:
>  * IOThread::Init() (invoked through BrowserThreadDelegate) perfoms
>    blocking operations this was previously performed before installed
>    the ThreadRestrictions on BrowserThread::IO. But now that //content
>    is initialized after bringing up the thread, a
>    base::ScopedAllowBlocking is required in scope of IOThread::Init().
>  * TestBrowserThread previously bypassing BrowserProcessSubThread by
>    directly subclassing BrowserThreadImpl meant it wasn't subject to
>    ThreadRestrictions (unfortunate becomes it denies allowance
>    verification to product code running in unit tests). Adding it back
>    causes DCHECKs, as such
>    BrowserProcessSubThread::AllowBlockingForTesting was added to allow
>    this CL to pass CQ.
>
> Of note:
>  * BrowserProcessSubThread is still written as though it supports many
>    BrowserThread::IDs but in practice it's mostly always
>    BrowserThread::IO (except in ThreadWatcherTest I think). This change
>    was big enough that I didn't bother also breaking that
>    generalization.
>  * BrowserThreadImpl's constructor was made private to ensure only
>    BrowserProcessSubThread and a few select callers get to drive it (to
>    avoid previous missed initialization issues)
>  * Atomics to manage BrowserThread::SetIOThreadDelegate were removed.
>    Restriction was instead added that this only be called before
>    initialization and after shutdown (this was already the case).
>
> Follow-ups to this CL:
>  * //ios duplicates this logic and will need to undergo the same change
>    as a follow-up
>  * Fixing ios will allow removal of base::Thread::SetMessageLoop hack :)
>  * Removing BrowserThreadGlobals::lock_ to address crbug.com/821034 will
>    be much easier
>  * BrowserThread post APIs should DCHECK rather than no-op if using a
>    BrowserThread::ID before it's registered.
>
> Bug: 815225, 821034, 729596
> Change-Id: If1038f23079df72203b1e95c7d26647f8824a726
> Reviewed-on: https://chromium-review.googlesource.com/969104
> Reviewed-by: John Abd-El-Malek <jam@chromium.org>
> Commit-Queue: Gabriel Charette <gab@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#544440}

TBR=jam@chromium.org

Bug: 815225, 821034, 729596, 824716
Change-Id: I9a180975c69a008f8519d1d3d44663aa58a74a92
Reviewed-on: https://chromium-review.googlesource.com/980793Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Gabriel Charette <gab@chromium.org>
Commit-Queue: Gabriel Charette <gab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546104}

Remove the WebMouseEvent dependency in MouseEvent
and all its subclasses like DragEvent and WheelEvent.

Bug: 820249
Change-Id: Icc62baea6862901cb91a531f7b649c6858ee94dd
Reviewed-on: https://chromium-review.googlesource.com/956543
Commit-Queue: Navid Zolghadr <nzolghadr@chromium.org>
Reviewed-by: Ella Ge <eirage@chromium.org>
Reviewed-by: Mustaq Ahmed <mustaq@chromium.org>
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546103}

The fix is to reduce the scope of the |lock_| during track adapter
creation because Create[Local/Remote]TrackAdapter() may synchronize with
another thread that is busy waiting for the |lock_|. There is no reason
to hold the |lock_| while creating the adapter; we are ensured no other
adapters of the same kind (=local/remote) are created concurrently
because they may only be created on the appropriate thread (local =
main thread, remote = signaling thread) which is the thread currently
running the operation. In other words, at most 1
GetOrCreateLocalTrackAdapter() on the main thread and at most 1
GetOrCreateRemoteTrackAdapter() on the signaling thread can run at the
same time.

This is the equivalent of the WebRtcMediaStreamAdapterMap fix
(https://chromium-review.googlesource.com/c/868656/) but for the track
adapter map.

The deadlock is quite rare, but due to recent unrelated changes it has
become frequent enough that it is easily reproducible on some platforms
and applications, see bug.

Bug: 813574
Change-Id: I2e7ba605db973221f80443267fd099c5973ab818
Reviewed-on: https://chromium-review.googlesource.com/980949
Commit-Queue: Henrik Boström <hbos@chromium.org>
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546102}

Mostly moving things around, refactoring...

1. Move GetRTCStatsCallback from rtc_peer_connection_handler.cc to
   rtc_stats.[h/cc] where other blink/webrtc stats-related content-glue
   is placed, and rename it RTCStatsCollectorCallbackImpl.

   This allows it to be used by content's RTCRtpSender and
   RTCRtpReceiver in follow-up CLs.

2. Remove unused content::RTCRtpSender-constructor.

3. Move WebRTCStatsReportCallbackResolver from RTCPeerConnection.cpp
   to its own file.

   This allows it to be used by blink's RTCRtpSender and RTCRtpReceiver
   in follow-up CLs.

4. Implement new PeerConnectionInterface::GetStats() functions in
   MockPeerConnectionImpl (need to wait for
   https://webrtc-review.googlesource.com/c/src/+/62900 to land and roll
   into chromium).

Bug: 680172
Change-Id: Ief18b2fb96ebc292149af606bd0edd87bac9e961
Reviewed-on: https://chromium-review.googlesource.com/973368
Commit-Queue: Henrik Boström <hbos@chromium.org>
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546101}

 * Mac10.10 Tests
 * Mac10.11 Tests
 * Mac10.12 Tests
 * Mac10.13 Tests

No-Try: True
Bug: 790162, 790157, 790160, 818391, 790164
Change-Id: I9bc62e97f97012ca147f09e7ddb82b96169588ed
Reviewed-on: https://chromium-review.googlesource.com/982002Reviewed-by: Sergiy Byelozyorov <sergiyb@chromium.org>
Commit-Queue: Andrii Shyshkalov <tandrii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546100}

This CL adds a switch allowing the choose which icon to use for the
search button in the bottom toolbar.

Bug: 826192
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: I363822bd9fa94606bf5422b0664febc91b81e03e
Reviewed-on: https://chromium-review.googlesource.com/980935
Commit-Queue: Gauthier Ambard <gambard@chromium.org>
Reviewed-by: Eric Noyau <noyau@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546099}

Bug: 819223
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: I41edb5310f0529f9d770f5b415cd6f5179a89d1a
Reviewed-on: https://chromium-review.googlesource.com/980672Reviewed-by: Gauthier Ambard <gambard@chromium.org>
Commit-Queue: Justin Cohen <justincohen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546098}

Currently I am working on touch selection module from Samsung,
parallely trying to improve touch selection module in open source.
Hence visibility of ongoing reviews in touch selection will help me
to understand and early planning of upcoming patches. Also it will
help in guiding Samsung peer contributors as well.

Change-Id: Ifbc6b49a9ff01c618ab8f7be0269c6580a90961a
Reviewed-on: https://chromium-review.googlesource.com/981837Reviewed-by: Mohsen Izadi <mohsen@chromium.org>
Commit-Queue: AJITH KUMAR V <ajith.v@samsung.com>
Cr-Commit-Position: refs/heads/master@{#546097}

Bug: 825908
Change-Id: I51019116cbcd2ca8ca969efa77ce4ea93f90450a
Reviewed-on: https://chromium-review.googlesource.com/980669Reviewed-by: Simon Hatch <simonhatch@chromium.org>
Commit-Queue: Emily Hanley <eyaich@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546096}

There are users of TCP socket APIs who do not care about the specific read/write
errors. One example is net::HttpServer.
This CL makes the observer param optional.

Bug: 721401
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: I028a01b6b8e3dea87a3865b704cc15347a3f2793
Reviewed-on: https://chromium-review.googlesource.com/978033Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Commit-Queue: Helen Li <xunjieli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546095}

No need to use MutableComputedStyle there.

Bug: 813068
Change-Id: If1ce7d3048af3ae7085ad09dd04350a5d4f1dd67
Reviewed-on: https://chromium-review.googlesource.com/980537Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546094}

Following bot results are included.
4362 4366 4367 4370 4371 4373 4375 4379 4385 4389 4395 4397 4398 4400
4401

5 lines were removed and 9 lines were deflaked by consecutive
results since 4322.

TBR=eae@chromium.org, mstensho@chromium.org
NOTRY=true

Bug: 591099
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: I9e099f354bc5411ed6a24ea9579546196ab1a19d
Reviewed-on: https://chromium-review.googlesource.com/979573
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546093}

Replaces the following GCStates with GCPhase counterparts.
- kGCRunning
- kSweeping
- kSweepingAndIdleGCScheduled
- kSweepingAndPreciseGCScheduled

Bug: 757440
Change-Id: I92b40d326bbedfe66ce41aca7d563968eaf3b28a
Reviewed-on: https://chromium-review.googlesource.com/980412
Commit-Queue: Keishi Hattori <keishi@chromium.org>
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546092}

(Report them to UMA, that is)

Bug: 787679, 808286
Change-Id: I7ad003574fd62c3429024b7ce45e55a2b39662bb
Reviewed-on: https://chromium-review.googlesource.com/975823
Commit-Queue: Maks Orlovich <morlovich@chromium.org>
Reviewed-by: Jesse Doherty <jwd@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546091}

This change updates base::span to match the std::span R6 proposal.
Quoting from the proposal document [1]:

Changes from R5:
 - Added constexpr qualifier to all iterator access functions on span.
 - Removed length() member function from span.
 - Removed constructor from span that took a nullptr_t.
 - Removed move constructor and move assignment operator.
 - Corrected definitions of comparison operations to take arguments
  by-value rather than by-reference.

[1] http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p0122r6.pdf

TBR=mkwst@chromium.org

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Ibd217c296a15b5ddf74162eb58a2b97674b9d293
Reviewed-on: https://chromium-review.googlesource.com/976123
Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Adam Langley <agl@chromium.org>
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: vmpstr <vmpstr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546090}

1. Consolidate logic to create VideoResourceUpdater into helper
   functions.
2. Improve ResourceType enum readability.
3. Delete dead code.
4. Fix software compositing tests expectations to ensure no new shared
   bitmap allocations.

Bug: 730660
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I1c4120b511a4e411f2699462eb03d9843a85c0a3
Reviewed-on: https://chromium-review.googlesource.com/977891Reviewed-by: danakj <danakj@chromium.org>
Commit-Queue: kylechar <kylechar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546089}

These keys are pinned in the client and rotated annually.

Bug: 820479
Change-Id: I5d38e7ac182d6794d86354334a7a92ab6da67c8a
Reviewed-on: https://chromium-review.googlesource.com/956974
Commit-Queue: Joshua Pawlicki <waffles@chromium.org>
Reviewed-by: Emily Stark <estark@chromium.org>
Reviewed-by: Sorin Jianu <sorin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546088}

Bug: 823831
Change-Id: I60dc7eb1d6a24e6e2e898c23dcacf1a74f06ccfd
Reviewed-on: https://chromium-review.googlesource.com/978223Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Commit-Queue: Chandan Padhi <c.padhi@samsung.com>
Cr-Commit-Position: refs/heads/master@{#546087}

We stored the previous match state for :empty, for elements affected by
:empty selectors, on their computed style. For :empty in non-rightmost
compound selectors, we would set the flag on on an already calculated
computed style. That required the ComputedStyle to be mutable.

Also, this flag didn't really work as we weren't trying to detect when
an element changed between empty and non-empty state. Instead, modify
CheckForEmptyStyleChange to check if there are any element or non-empty
text nodes before/after the added/removed node. If there are, no :empty
selector matching needs to be updated.

Bug: 813068
Change-Id: Ic2e7c9a855067267d84c50c71215114a834e92ae
Reviewed-on: https://chromium-review.googlesource.com/980946Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546086}

This CL adds a check when initializing the ContextProvider for layout
tests. We should retry the on transient failures but just crash for
fatal failures. There is no compositing mode fallback in layout tests
for simplicity, so we can't do much other than crash here.

The reason for this change is that ClusterFuzz was picking up access to
some uninitialized data in some vaguely related code. This happens
because there is a fatal failure in CreateDisplayOutputSurface() that is
ignored. The crash stack should now pinpoint exactly where the failure
was and make problems easier to diagnose.

Bug: 817758
Change-Id: I766c0526e0e2c01d16be922f78de1b89365ae401
Reviewed-on: https://chromium-review.googlesource.com/980653Reviewed-by: Antoine Labour <piman@chromium.org>
Commit-Queue: kylechar <kylechar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546085}

In NativeWidgetMacNSWindow, sendEvent: will *not* call [super sendEvent:] for
events that might be the start of a drag, which prevents the window from
receiving the event if we think it might start a drag. Any LMouseDown could
start a drag, so that causes mouse clicks that aren't on some other NSView to
not raise the window. Fix that by not returning early when maybe starting a
drag.

Bug: 775984
Change-Id: Ibe93e45dc4dde39630a3d97f5a148de018c99ab2
Reviewed-on: https://chromium-review.googlesource.com/980701Reviewed-by: Trent Apted <tapted@chromium.org>
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546084}

In websocket_stream_test.cc, test methods take URL, host (with optional
port), and path arguments, which are redundant.  This CL removes the
host and path arguments and generates them from URL.

Also, every test uses the same origin and host_for_cookies, therefore
there is no need to pass those as arguments either.

Bug: 825231
Change-Id: I31c0c7a44e3e0d28d10c5b1b0c61b2fc744c7e48
Reviewed-on: https://chromium-review.googlesource.com/980958Reviewed-by: Adam Rice <ricea@chromium.org>
Commit-Queue: Bence Béky <bnc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546083}

Bug: 820299
Change-Id: I9e380416b18f30294fe7cb969a0ce7d0ab1fd7bd
Reviewed-on: https://chromium-review.googlesource.com/977910Reviewed-by: Darren Shen <shend@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546082}

When investigating failures due to handling of large traces,
we disabled some of the pages on v8.browsing_mobile benchmarks.
Some of these are enabled later on v8.browsing_mobile but not
on v8.browsing_mobile-future. Enabling them now.

BUG=chromium:799080

Change-Id: I8b25464be3f01d71d1b3cce07e0c66db8b0b5427
Reviewed-on: https://chromium-review.googlesource.com/962244Reviewed-by: Ned Nguyen <nednguyen@google.com>
Reviewed-by: Michael Hablich <hablich@chromium.org>
Commit-Queue: Mythri Alle <mythria@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546081}

Bug: 823655
Change-Id: If6dfa9d775d3be37b72b4cf5f2fd9db89763819a
Reviewed-on: https://chromium-review.googlesource.com/981314Reviewed-by: Hans Wennborg <hans@chromium.org>
Commit-Queue: Hans Wennborg <hans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546080}

This patch implements Range.getClientRects and getBoundingClientRect
by implemeting LayoutText::AbsoluteQuadsForRange, the underlying
function to compute quads for a range of text.

VisibleUnits and TouchAdjustment are other users of this function.

crbug.com/698038 added some logic to clear the quad vector under
specific condition for legacy, but the logic is a bit complicated.
This patch tries to match to the spec without using the same logic.
There may be a need to tweak the logic a little more, but the new
logic seems to be more interoperable with Edge/Gecko.

Bug: 636993, 755750
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: I5c6323680285a4e03d64109cd5681c788f6a6bbf
Reviewed-on: https://chromium-review.googlesource.com/979732Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#546079}