GitLab

Update the New Tab Bubble Promo String to "Add tabs and switch between
pages".

Bug: 779656
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: Ia42386ecc45e45ccf93105d48ff5bdd898cf4058
Reviewed-on: https://chromium-review.googlesource.com/809844Reviewed-by: edchin <edchin@chromium.org>
Commit-Queue: Gregory Chatzinoff <gchatz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521860}

Revert "Reland "Enable video capture service by default on platforms where it is rolling out with M61.""

This reverts commit 0fdb7a80.

Reason for revert: broke webkit_layout_tests: https://uberchromegw.corp.google.com/i/chromium.webkit/builders/WebKit%20Linux%20Trusty%20Leak/builds/12888

Original change's description:
> Reland "Enable video capture service by default on platforms where it is rolling out with M61."
> 
> This is a reland of 1e2e99ef
> 
> The reason for the revert was a Webkit layout test failing with this CL. With
> https://chromium-review.googlesource.com/c/chromium/src/+/806442 landed to fix that test,
> this CL should now be able to reland without modification.
> 
> Original change's description:
> > Enable video capture service by default on platforms where it is rolling
> > out with M61.
> >
> > Bug: 721812
> > Change-Id: I1de0f625a1fb106e2dea664675e94267e66fc2fd
> > Reviewed-on: https://chromium-review.googlesource.com/719416
> > Commit-Queue: Christian Fremerey <chfremer@chromium.org>
> > Reviewed-by: Emircan Uysaler <emircan@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#517761}
> 
> TBR=emircan@chromium.org
> 
> Bug: 721812
> Change-Id: If69cdb660b0b97a28084b6bd0610234d5abb232f
> Reviewed-on: https://chromium-review.googlesource.com/809530
> Reviewed-by: Christian Fremerey <chfremer@chromium.org>
> Commit-Queue: Christian Fremerey <chfremer@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#521800}

TBR=emircan@chromium.org,chfremer@chromium.org

Change-Id: Iee20ddb4dabf156cd3709151792cc374b0b50194
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 721812
Reviewed-on: https://chromium-review.googlesource.com/809770Reviewed-by: Derek Cheng <imcheng@chromium.org>
Commit-Queue: Derek Cheng <imcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521859}

This is a reland of 52dda118
Original change's description:
> [Media Router] Better sink availability tracking
> 
> - When sink availability changes for an MRP, start/stop observing sinks only for that MRP
> - Make WiredDisplayMRP report sink availability updates
> 
> Bug: 789277,777650
> Change-Id: I3d1a087ca39a4830403d6d2f0f00bf1411388f33
> Reviewed-on: https://chromium-review.googlesource.com/794106
> Reviewed-by: Derek Cheng <imcheng@chromium.org>
> Commit-Queue: Takumi Fujimoto <takumif@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#521550}

Bug: 789277, 777650
Change-Id: I0a2edc4af121fa675548f9d545bb6048b05e2f13
Reviewed-on: https://chromium-review.googlesource.com/809333Reviewed-by: Derek Cheng <imcheng@chromium.org>
Commit-Queue: Takumi Fujimoto <takumif@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521858}

This CL adds support to filter code coverage results by list of
directories or files so that the script can run faster without having
to generate a report for every executed file.

Bug: 789691
Change-Id: I2e954872b7f1113cd04b8e609ffdabf0578db762
Reviewed-on: https://chromium-review.googlesource.com/809295
Commit-Queue: Yuke Liao <liaoyuke@chromium.org>
Reviewed-by: Abhishek Arya <inferno@chromium.org>
Reviewed-by: Max Moroz <mmoroz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521857}

Previously the targets to be compiled (but not run) were specified
explicitly, effectively duplicating the logic already present in the GN
build configuration files.

Bug: 707031
Change-Id: I8c6715f9f862a04a49c81030ba9d0212f0468ec9
Reviewed-on: https://chromium-review.googlesource.com/802189
Commit-Queue: Wez <wez@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Reviewed-by: Scott Graham <scottmg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521856}

This is more consistent.

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

This change requests focusing of the first item after selecting
an item. Generally that should focus the newly connecting item as
soon as the list is updated.

Bug: 739633
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I728658d1bbc916c56793960c576e47fe5bc91354
Reviewed-on: https://chromium-review.googlesource.com/806440Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Commit-Queue: Steven Bennetts <stevenjb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521854}

Bug: 754889
Change-Id: I60bc810728bed4759dac3a406f0eae36a1e11820
Reviewed-on: https://chromium-review.googlesource.com/794491Reviewed-by: Bryan McQuade <bmcquade@chromium.org>
Commit-Queue: Steven Holte <holte@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521853}

This avoid hitting a DCHECK that was introduced in
https://chromiumcodereview.appspot.com/2401083003 where we tried clean
up notifications to the model thread about encryption information.
By re-using the existing ApplyUpdates methods (and DCHECKs) we now
realize that we sometimes call ApplyUpdates before the initial sync is
completed. This is probably wrong and definitely, since the initial
sync will call ApplyUpdates and pass encryption information. Sending it
before that will just be confusing for the proc.

Bug: 789950
Change-Id: Ifc2b01efbc71145574f9106c67ce9aebfc8f6b99
Reviewed-on: https://chromium-review.googlesource.com/807664Reviewed-by: Pavel Yatsuk <pavely@chromium.org>
Reviewed-by: Mikel Astiz <mastiz@chromium.org>
Commit-Queue: Sky Malice <skym@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521852}

Bug: 167187
Change-Id: If36e8f8eb3667a505818edec7cdff3bb36bd8831
Reviewed-on: https://chromium-review.googlesource.com/804663Reviewed-by: Eric Roman <eroman@chromium.org>
Reviewed-by: Will Harris <wfh@chromium.org>
Commit-Queue: Chris Bentzel <cbentzel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521851}

Added kNoClockless flag in the test. This is expected to fix the
flake.

Bug: 788387
Change-Id: Ife4a443ef30d4f9b656e52ece3c1025cee5c0a96
Reviewed-on: https://chromium-review.googlesource.com/809507
Commit-Queue: Sergey Ulanov <sergeyu@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521850}

This requires fixing NativeValueTraitsImplTest.IDLCallbackFunction to
use ASSERT_DEATH_IF_SUPPORTED. The conditional handling for Official vs
normal builds is also removed, for simplicity.

Bug: 779820, 707031
Change-Id: Ib2563d8b6ca792ce916d7be907956d33329e4ba4
Reviewed-on: https://chromium-review.googlesource.com/802355
Commit-Queue: Wez <wez@chromium.org>
Reviewed-by: Jochen Eisinger <jochen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521849}

https://pdfium.googlesource.com/pdfium.git/+log/12ec6760afd9..c45271e053c8

$ git log 12ec6760a..c45271e05 --date=short --no-merges --format='%ad %ae %s'
2017-12-05 thestig Remove redundant field in struct FXCMAP_CMap.
2017-12-05 thestig Fix CXFA_SimpleParser member destruction order.
2017-12-05 thestig Avoid integer overflows in CPDF_FixedMatrix::Transform().

Created with:
  roll-dep src/third_party/pdfium
BUG=791616,791048


The AutoRoll server is located here: https://pdfium-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=dsinclair@chromium.org

Change-Id: Id9a3a2c72218d95099dc5a350d51e2050758e565
Reviewed-on: https://chromium-review.googlesource.com/809312
Reviewed-by: <pdfium-deps-roller@chromium.org>
Commit-Queue: <pdfium-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521848}

These machines were moved to the chromium.android waterfall a while
back but their JSON entries were forgotten. Remove the definitions of
these bots and the test suite exceptions referring to them. (The
presubmit checks caught all of the stray exceptions.)

Add cast_junit_test_lists to Cast Android (dbg) on chromium.android,
which is presuambly where it should have been placed during this
migration.

BUG=662541

Change-Id: Iaa0453b17e06e31096ecf4e770557ad6aa7d7fd6
Reviewed-on: https://chromium-review.googlesource.com/809633Reviewed-by: John Budorick <jbudorick@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521847}

Bug: 792133
Change-Id: Iaa99ae16b359560f60e23c07cace1241781b6bbd
Reviewed-on: https://chromium-review.googlesource.com/809296Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Commit-Queue: Doug Arnett <dougarnett@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521846}

Bug: 768982
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I030f371dcbc1fbef3bcc01ce1daa110cd5b6ad1f
Reviewed-on: https://chromium-review.googlesource.com/807144Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: dsinclair <dsinclair@chromium.org>
Commit-Queue: Henrique Nakashima <hnakashima@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521845}

This test appears to timeout 100% of the time under Linux, so adding the
Timeout expectation to prevent it from causing try-bot failures until
the issue is addressed.

No-Try: true
Bug: 789533
Change-Id: I384d355689004eadcf16d6357ed164fca05760a4
Reviewed-on: https://chromium-review.googlesource.com/809826Reviewed-by: Wez <wez@chromium.org>
Reviewed-by: Justin Novosad <junov@chromium.org>
Commit-Queue: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521844}

Bug: 792162
Change-Id: I9e7fbe7484e914a3af14f808c4a9eb81d2b98228
Reviewed-on: https://chromium-review.googlesource.com/808754Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521843}

We are busily converting over the test configs for the waterfalls
to the new `generate_buildbot_json` tooling; until everything
is converted, and we have docs written for how to use this,
we want only a very small number of people making changes to
these files.

R=kbr@chromium.org, jbudorick@chromium.org
BUG=662541

Change-Id: I45432632c914a721fc2704e1b57a02399c624a2f
Reviewed-on: https://chromium-review.googlesource.com/809684Reviewed-by: John Budorick <jbudorick@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Dirk Pranke <dpranke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521842}

In Chrome:
- WebAPK's channel is set under "Sites" notification group and
  "readable origin" as the channel, the same channel as Webapps.
- If the device is Android o+, Chrome will set a channel to the
  notification.

In WebAPK:
- WebApkServiceImpl#notifyNotification() is deprecated. Chrome calls
  notifyNotificationWithChannel() instead.
- If on Android O+, WebAPK will ensure the notification channel is
  created if its notifications have a channel id.

To test this change, we need to make sure the following cases all work:
- New WebAPK, new Chrome;
- New WebAPK, old Chrome;
- Old WebAPK, new Chrome.

Bug: 700228
Change-Id: I176a8d45f021a33ea441837476b1ca09e973a48b
Reviewed-on: https://chromium-review.googlesource.com/786300Reviewed-by: Robert Sesek <rsesek@chromium.org>
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Reviewed-by: Peter Kotwicz <pkotwicz@chromium.org>
Reviewed-by: Anita Woodruff <awdf@chromium.org>
Commit-Queue: Xi Han <hanxi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521841}

As the first step of ScrollSnapPoints, this patch implements it on main
thread at GestureScrollEnd. It introduces necessary data structures:
SnapAreaData and SnapContainerData, updates the data after style change
and layout, implements a naive algorithm to select snap points at
intended-end-position, adds unit-tests for logic and adds sim-tests for
behavior.

Bug: 778257
Change-Id: I307d51254bd9ab9b7a42b0614d181adac662fa47
Reviewed-on: https://chromium-review.googlesource.com/756887Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Reviewed-by: Darren Shen <shend@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Reviewed-by: Majid Valipour <majidvp@chromium.org>
Commit-Queue: Sandra Sun <sunyunjia@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521840}

Regression recently introduced in
https://chromium-review.googlesource.com/c/chromium/src/+/782563
without apparent failing tests.

Bug: 
Change-Id: I68dfebce4597234d88428bae7a37d10dd99b93d8
Reviewed-on: https://chromium-review.googlesource.com/808928Reviewed-by: Robert Sesek <rsesek@chromium.org>
Commit-Queue: Mikel Astiz <mastiz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521839}

The CL tweaks StoragePartitonInterceptor (in
isolated_origin_browsertest.cc) so that it can be configured to inject
different origins, depending on needs of individual tests.  This tweak
is supported by changes in base/lazy_instance.h (adding of inequality
operator implemented on top of the already existing equality operator),
and in render_process_host_impl.cc/.h (to support creating a test-only
StoragePartitionService via a base::Callback, rather than via a function
pointer).

Tweaks of StoragePartitonInterceptor allow forking of
IsolatedOriginTest.LocalStorageOriginEnforcement test into 2 separate
tests:
- LocalStorageOriginEnforcement_IsolatedAccessingNonIsolated
- LocalStorageOriginEnforcement_NonIsolatedAccessingIsolated
The second test is introduced by this CL and was failing before this CL.

Tweaks of ChildProcessSecurityPolicyImpl::CanAccessDataForOrigin
disallow requests from non-isolated renderers (in which case
CheckOriginLock will return NO_LOCK) if the request is for
an isolated origin.  This makes the new test pass.

Bug: 509125, 764958
Change-Id: Ibfff2c91cb2ac51966e1d89295f10592a3814c08
Reviewed-on: https://chromium-review.googlesource.com/775060
Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521838}

DevTools: roll the inspector_protocol to allows crlf in protocol descriptions, update headless generator.

Change-Id: I299a8172b86e0b456f12b245077986ae52f4c594
Reviewed-on: https://chromium-review.googlesource.com/807245Reviewed-by: Alex Clarke <alexclarke@chromium.org>
Reviewed-by: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org>
Commit-Queue: Pavel Feldman <pfeldman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521837}

Introduce an optional param "raw_manifest_flags" in shell Apk AndroidManifest.xml.
It can be filled with:
<uses-feature android:name="android.hardware.ram.low" android:required="true" />
if an unbound WebAPK is targeting low ram devices.

Bug: 791080
Change-Id: Ie9968ec477a0dbd0694d37aae72f7454fc797ef2
Reviewed-on: https://chromium-review.googlesource.com/809088Reviewed-by: Glenn Hartmann <hartmanng@chromium.org>
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Commit-Queue: Xi Han <hanxi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521836}

In RTL mode a tab transitioning from non-pinned to pinned ends up with
no visible favicon. This cl fixes this problem, and also uses the
correct tab width to calculate the iconview's position in non-pinned
RTL mode.

Bug: 789347
Change-Id: I972ef71c47811f9b2a5cf6ca2ac5f2c654d0c2bc
Reviewed-on: https://chromium-review.googlesource.com/795151Reviewed-by: Avi Drissman <avi@chromium.org>
Commit-Queue: Jayson Adams <shrike@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521835}

In the scenario provided in the bug, the size is initially
small like the video popup. All the lifecycle events happen,
and then a fresh layout occurs with the full size, making
space for the toolbar.

Bug: 789958
Change-Id: I528ae2b94f51dd25bc1d259697d35cfc201b6ed7
Reviewed-on: https://chromium-review.googlesource.com/809016Reviewed-by: Nicolas Dossou-Gbété <dgn@chromium.org>
Commit-Queue: Michael van Ouwerkerk <mvanouwerkerk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521834}

IsPossibleNumberImpl is doing exact the same operations as
IsPossibleNumberForString

Bug: 736387
Change-Id: I093bb9c10befdac73ae67b4a36ad7857e163813e
Reviewed-on: https://chromium-review.googlesource.com/809200Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
Reviewed-by: Mathieu Perreault <mathp@chromium.org>
Commit-Queue: Mathieu Perreault <mathp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521833}

Change-Id: I8bcc0d0ff3fec11c2e0dd037a65e025e9c40d607
Reviewed-on: https://chromium-review.googlesource.com/809084Reviewed-by: Florin Malita <fmalita@chromium.org>
Commit-Queue: Herb Derby <herb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521832}

This CL defines a new interface, VideoFrameReleaser, and adds a channel
in MojoVideoDecoder to use it, in a way that can outlive the
VideoDecoder.

On the renderer side, MojoVideoFrameReleaser is ref counted, and will
live as long as there are outstanding VideoFrames.

On the gpu side, VideoFrameHandleReleaserImpl maintains a map of
outstanding VideoFrames, and will live until the map is empty.

The old path, with special methods on mojom::VideoDecoder, is removed.
VideoDecoder implementations can now attach regular mailbox release
callbacks to their VideoFrames and expect normal results.

Bug: 737220, 733828
Change-Id: I3c26e1e98c61f180246815fcc79f6731d8a26ed4
Reviewed-on: https://chromium-review.googlesource.com/762104
Commit-Queue: Dan Sanders <sandersd@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Xiaohan Wang <xhwang@chromium.org>
Reviewed-by: Frank Liberato <liberato@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521831}

Metrics to count whether the verification request will be sent when profile is loaded.
Metrics to count the amount of time from profile loaded to verification finished.

Bug: 791171
Change-Id: I693eb5bd2289fc7ba7c295dbd45309d1b04ffe26
Reviewed-on: https://chromium-review.googlesource.com/804754Reviewed-by: Jesse Doherty <jwd@chromium.org>
Reviewed-by: Roger Tawa <rogerta@chromium.org>
Commit-Queue: Owen Min <zmin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521830}

Chrome cannot build with VS 2015 anymore. Having it listed as a
supported compiler can lead to confusion for new Chromium developers.
This change scrubs inappropriate '2015' references from the Chromium
repo.

Bug: 683729
Change-Id: I2e02bc31ae8fd57a31ac65f1bb8a45eb5a5cd433
Reviewed-on: https://chromium-review.googlesource.com/807526
Commit-Queue: Bruce Dawson <brucedawson@chromium.org>
Reviewed-by: Scott Graham <scottmg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521829}

https://chromium.googlesource.com/catapult.git/+log/6b77e41141aa..37c17ee783f3

$ git log 6b77e4114..37c17ee78 --date=short --no-merges --format='%ad %ae %s'
2017-12-05 eakuefner [TBMv2] Implement TagMap equality in Python
2017-12-05 perezju [Telemetry] Raise AppCrashException on multiple browser PIDs

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: If1b9b65d1b4a96cc161e28a33ebc9b1868d40f6f
Reviewed-on: https://chromium-review.googlesource.com/809532
Reviewed-by: <catapult-deps-roller@chromium.org>
Commit-Queue: <catapult-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521828}

This is a reland of d0de1771 now that
crrev.com/00fb4b7e landed fixing the lock-up
issue we previously saw.

Original change's description:
> [CFI] Use ProtectedMemory in CertVerifyProcNSS
>
> Because CertVerifyProcNSS dynamically resolves a pointer to the function
> CERT_CacheOCSPResponseFromSideChannel(), Control Flow Integrity [1]
> indirect call (cfi-icall) checking can not verify that it is the
> intended target for that function pointer call site.
>
> Since we can not use cfi-icall to check the function pointer, instead we
> place the pointer in ProtectedMemory, a wrapper for keeping variables in
> read-only memory except for when they are initialized. After setting the
> pointer in protected memory we can use the UnsanitizedCfiCall wrapper to
> disable cfi-icall checking when calling it since we know it can not be
> tampered with.
>
> [1] https://www.chromium.org/developers/testing/control-flow-integrity
>
> Bug: 771365
> Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester;master.tryserver.chromium.mac:ios-simulator-cronet
> Change-Id: I5d65b3591681f3daa917b6516eec1e5e47513d12
> Reviewed-on: https://chromium-review.googlesource.com/765098
> Reviewed-by: Peter Collingbourne <pcc@chromium.org>
> Reviewed-by: Eric Roman <eroman@chromium.org>
> Commit-Queue: Peter Collingbourne <pcc@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#517169}

Bug: 771365
Change-Id: I908d37ce805f6673f96f7eebdba22be45fe96912
Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester;master.tryserver.chromium.mac:ios-simulator-cronet
Reviewed-on: https://chromium-review.googlesource.com/783590Reviewed-by: Eric Roman <eroman@chromium.org>
Reviewed-by: Peter Collingbourne <pcc@chromium.org>
Commit-Queue: Peter Collingbourne <pcc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521827}

This preference was used to allow NPAPI plugins to be always-authorized,
and following their removal only affected whether crashy plugins would
continue to be re-loaded.

Bug: 418069
Change-Id: I1a50121ca2d2453823e56ddd4a803caa24ee271a
Reviewed-on: https://chromium-review.googlesource.com/775911Reviewed-by: Drew Wilson <atwilson@chromium.org>
Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
Commit-Queue: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521826}

Bug: 661629
Change-Id: I39858457456e28ecf4fdf5e7d3c1c875746dae78
Reviewed-on: https://chromium-review.googlesource.com/809201Reviewed-by: Avi Drissman <avi@chromium.org>
Commit-Queue: Charlie Harrison <csharrison@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521825}

Bug: 667560
Change-Id: Id0d481cde735bffe33504486f1378a5f9fbaaec4
Reviewed-on: https://chromium-review.googlesource.com/807401
Commit-Queue: Erik Luo <luoe@chromium.org>
Reviewed-by: Will Chen <chenwilliam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521824}

This CL removes RecordingImageBufferSurface.

Bug: 776806
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: I01e3d77702d92beef2fe73d7ecf7ad51df7ac86d
Reviewed-on: https://chromium-review.googlesource.com/809189
Commit-Queue: Olivia Lai <xlai@chromium.org>
Reviewed-by: Justin Novosad <junov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521823}

This isn't needed anymore with URLLoaderInterceptor.

Bug: 776589
Change-Id: Ic2a7dd35175e052be7874bc0105e2f758bca26a9
Reviewed-on: https://chromium-review.googlesource.com/809533Reviewed-by: Yuzhu Shen <yzshen@chromium.org>
Commit-Queue: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521822}

Bug: 792098
Change-Id: If75e986571a3490c4d70e22a4748e43b517ba857
Reviewed-on: https://chromium-review.googlesource.com/809099Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521821}