GitLab

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}

llvm symbolizer is a more efficient symbolizer than addr2line, objdump,
etc.

In this cl, I 1)created a wrapper instance to interact with
llvm symbolizer, 2)made the stack script to use llvm symbolizer instance,
and then 3)added llvm symbolizer into isolated inputs.

Bug: 774267
Change-Id: I971fb808b97f3a569eb9615f99efa41e3a56f3cb
Reviewed-on: https://chromium-review.googlesource.com/789376Reviewed-by: agrieve <agrieve@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Zhiling Huang <hzl@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521820}

https://chromium.googlesource.com/angle/angle.git/+log/4fba4a97bc08..12a18ad357bc

$ git log 4fba4a97b..12a18ad35 --date=short --no-merges --format='%ad %ae %s'
2017-12-01 oetuaho Simplify interface block instance recording
2017-12-01 cwallez Add PackedEnumBitSet, use it for buffer binding validation

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=geofflang@chromium.org

Change-Id: Iacf96120475548f6001870a1f790ba7986917093
Reviewed-on: https://chromium-review.googlesource.com/809539Reviewed-by: angle-deps-roller . <angle-deps-roller@chromium.org>
Commit-Queue: angle-deps-roller . <angle-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521819}

* Removed the no-goma assertion since the bug has already been resolved.
* Changed the CC and CXX command to reflect the changes in the analyzer
  wrapper script. (crrev.com/2667853004 and crrev.com/2748793004)

Bug: 791239
Change-Id: I0c7470213eb769e19f4db64fbb0421ee99a9a06e
Reviewed-on: https://chromium-review.googlesource.com/804607Reviewed-by: Sylvain Defresne <sdefresne@chromium.org>
Commit-Queue: Yuwei Huang <yuweih@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521818}

Content script and Page Action sample extension that demos
auto/programmatic insertion by highlighting html elements
that contain user inserted words.

Bug: None
Change-Id: I4d4887777dfdc4d76f45ad923b2bb5d297faed39
Reviewed-on: https://chromium-review.googlesource.com/707296
Commit-Queue: Crystal Lambert <crystallambert@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521817}

This CL is part of the effort to have a separate RasterInterface implementation
in the the GPU process. After this CL, --enable-raster-decoder will cause
- a RasterInterface client to have a RasterCmdBuffStub on the server side and
- a GLES2Interface client to have a GLES2CmdBuffStub on the server side

With this CL, RasterCmdBuffStub and GLES2CmdBuffStub only differ in that
RasterCmdBuffStub insists on being associated with an offscreen context.

In the future, {Raster,GLES2}CmdBuffStub will diverge. Soon RasterCmdBuffStub
will have a special RasterDecoder decoder.

Bug: 789238
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: I313868192ccbd1c17c102ae1bb91c46a528b178d
Reviewed-on: https://chromium-review.googlesource.com/796951Reviewed-by: Victor Miura <vmiura@chromium.org>
Commit-Queue: Jonathan Backer <backer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521816}

This change updates the filter-matches.html test to use the Web
Bluetooth Test interface. This will help us migrate the test to
the wpt/ directory, since testRunner is not going to be used
anymore.

BUG=509038

Change-Id: Id53632e8b3c7a979c29904f53fbea2d5a5f7f3bc
Reviewed-on: https://chromium-review.googlesource.com/783498
Commit-Queue: Ovidio Henriquez <odejesush@google.com>
Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org>
Reviewed-by: Vincent Scheib <scheib@chromium.org>
Reviewed-by: Conley Owens <cco3@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521815}

NetworkHandles should be supported in Lollipop and newer releases.

Change-Id: Ia19095b883926daf97456d81201a3e8d93859467
Reviewed-on: https://chromium-review.googlesource.com/809224
Commit-Queue: Paul Jensen <pauljensen@chromium.org>
Reviewed-by: Helen Li <xunjieli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521814}

Previously the code queried TestScreen. This is problematic as
content_browsertests uses TestScreen, which *always* returns a display
id of 2000. When mus gets the event the event is then dropped (because
it doesn't know about 2000). This changes EventInjector to query
WindowTreeHost and has WindowTreeHostMus override GetDisplayId() to
return the real display id.

BUG=786453
TEST=none

Change-Id: I01b9ce9096a0a3e7d6ca9cf85706afb0213035a7
Reviewed-on: https://chromium-review.googlesource.com/809493Reviewed-by: Elliot Glaysher <erg@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521813}

This has been unnecessary in the past with YouTube VP9 encodings,
but for some reason other VP9 encoding types show artifacts if
the configuration change is not processed.

BUG=729600
TEST=no more artifacts on http://dashjs.eb.epiclabs.io/

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: Id91f112ff8a1f1877cade3e8a86af39b05ff80a0
Reviewed-on: https://chromium-review.googlesource.com/802629
Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
Reviewed-by: Frank Liberato <liberato@chromium.org>
Reviewed-by: Dan Sanders <sandersd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521812}

This removes the final use of BuildInfo.isAtLeastO from chromium code.

This was previously blocked on robolectric not supporting O (but this
has since been resolved by crbug.com/729135).

Bug: 783418
Test: ninja chrome_junit_tests
Change-Id: Ib7d4af9ff74912ccadfa3c9cae57553f3a217e94
Reviewed-on: https://chromium-review.googlesource.com/806745Reviewed-by: Richard Coles <torne@chromium.org>
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Commit-Queue: Nate Fischer <ntfschr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521811}

Using wpt-import in Chromium a3ce2d31.

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

Note to sheriffs: This CL imports external tests and adds
expectations for those tests; if this CL is large and causes
a few new failures, please fix the failures by adding new
lines to TestExpectations rather than reverting. See:
https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md

TBR=qyearsley

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

This CL only adds |const| to SecurityOrigin and thus doesn't change the behavior.

This CL replaces most of
- WebPrivatePtr<SecurityOrigin> -> WebPrivatePtr<const SecurityOrigin>
- scoped_refptr<SecurityOrigin> -> scoped_refptr<const SecurityOrigin>
- SecurityOrigin* -> const SecurityOrigin*
- SecurityOrigin& -> const SecurityOrigin&

Most of the modifications are done mechanically by PCRE:
s/(WebPrivatePtr<|scoped_refptr<|((?<!const)\s+)|\(|^)((::)?blink::)?SecurityOrigin([&\*>])/$1const $3SecurityOrigin$5/g

The following SecurityOrigin references remain non-const:
- SecurityContext::security_origin_
- SecurityContext::GetMutableSecurityOrigin()
- ExecutionContext::GetMutableSecurityOrigin()
- Document::UpdateSecurityOrigin()
- RemoteSecurityContext::SetReplicatedOrigin()
- SecurityOrigin::IsolatedCopy()
- Some local variables
- Some methods in unit tests

(For isolated world SecurityOrigin for XHRs)
- IsolatedWorldSecurityOriginMap
- XMLHttpRequest()::isolated_world_security_origin_
- XMLHttpRequest::XMLHttpRequest()
- XMLHttpRequest::GetMutableSecurityOrigin()
- DOMWrapperWorld::IsolatedWorldSecurityOrigin()
- DOMWrapperWorld::SetIsolatedWorldSecurityOrigin()

(For blob SecurityOrigins)
- BlobURLOriginMap
- SecurityOrigin::Create.*()
- URLRegistry::RegisterURL()
- BlobRegistry::RegisterPublicBlobURL()
- URLSecurityOriginMap::GetOrigin()

Bug: 779730
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: Ie4a1a5cc2add20c1c1b9d0d6d5dff9ea9ec46240
Reviewed-on: https://chromium-review.googlesource.com/744586
Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521809}

Also rewrite some if-else statements without if (!cond).

Change-Id: If70a32a7baa5d2e70480831646ebf46eea8b8993
Reviewed-on: https://chromium-review.googlesource.com/804833Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521808}

Before, we weren't packaging localized pak files with the Android cast
shell, and ResourceBundle wasn't looking in the APK assets for these pak
files.

Bug: internal b/70031131
Test: CQ and tried it out with an Android build
Change-Id: I65adbaf552dfce6be62c4c4035d221f42b330c4d
Reviewed-on: https://chromium-review.googlesource.com/807406Reviewed-by: Luke Halliwell <halliwell@chromium.org>
Commit-Queue: Thoren Paulson <thoren@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521807}

This patch ensures that we initialize all font creation params before
reading them and abort creating a typeface if the reader is invalid.

R=enne@chromium.org, ericrk@chromium.org

Bug: 785675
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel
Change-Id: I7baabeb460c9cb06026c8a82989c7c6f7e970f8f
Reviewed-on: https://chromium-review.googlesource.com/808748Reviewed-by: Khushal <khushalsagar@chromium.org>
Commit-Queue: vmpstr <vmpstr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521806}

This makes it much easier to analyse CDM crashes.

Tested with --enable-crash-reporter-for-testing, which will upload
a crash report and print a crash ID to stdout. Then confirmed that
we have the CDM version in the crash report.

See crash ID 27c2f5df78d977e227 for an example crash.

BUG=788937

Change-Id: Ifa565f0d01a78cfef2329704ea3bc3feb9a5723a
Reviewed-on: https://chromium-review.googlesource.com/792258
Commit-Queue: Xiaohan Wang <xhwang@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521805}

This test is intermittently failing. Based on the screenshots from the failing
try bots, it appears the issue is that the test is tapping at the beginning of
"hello world" instead of at the end.

I'm unable to reproduce the problem locally, but my best guess as to why this is
happening is that we're not waiting to make sure the text has actually been
committed before attempting to find the bounds of the span element that's
supposed to be after the text, so I'm adding this check (which we also have in
testDeleteWordMarkedWithSpellingMarker()).

Bug: 789954
Change-Id: I06b85282057c361adc9da3f6ee289870ecf0c164
Reviewed-on: https://chromium-review.googlesource.com/802187Reviewed-by: Changwan Ryu <changwan@chromium.org>
Commit-Queue: Ryan Landay <rlanday@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521804}

There were code in ui/views that didn't know about the class
property type specialization for gfx::Insets* and Views* so they
got the default template implementation.

In jumbo builds the compiler noticed that there was code
using the default implementation before the specialization
appeared and it triggered a compilation error.

The fix is to declare the specialization so that all code uses it.

Bug: 773275
Change-Id: Ifa925a2002ba930af16dc6940a04b2a480721438
Reviewed-on: https://chromium-review.googlesource.com/786190Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: David Reveman <reveman@chromium.org>
Commit-Queue: Daniel Bratell <bratell@opera.com>
Cr-Commit-Position: refs/heads/master@{#521803}

Refactors waitOnJavaScriptStep to be more strict. The behavior should
be identical to the old implementation except:
1. Attempting to use waitOnJavaScriptStep without the proper JavaScript
    code to do so results in a failure.
2. JavaScript test failures that occur while waiting for a step are
    caught and reported immediately instead of whenever Java calls
    endTest.

Bug: 
Change-Id: I2ce955f31c6c90355400f42b2f66c5ff4b042538
Reviewed-on: https://chromium-review.googlesource.com/809386Reviewed-by: agrieve <agrieve@chromium.org>
Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Commit-Queue: Brian Sheedy <bsheedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521802}

Bug: 721395
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: I8a2cd64bc04c33fa984af3ebff7d053738f5ccd4
Reviewed-on: https://chromium-review.googlesource.com/806355Reviewed-by: Helen Li <xunjieli@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Commit-Queue: Randy Smith <rdsmith@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521801}

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/809530Reviewed-by: Christian Fremerey <chfremer@chromium.org>
Commit-Queue: Christian Fremerey <chfremer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521800}

IDS_EXTENSION_PROMPT_RATING_ACCESSIBLE_TEXT is compliant to the ICU
message format spec (so, the unittest passes), but it's rejected
by the translation infra's ICU msg syntax checker because it has
additional constraints on the ICU syntax: A plural selector should be
at the outer most level.

Rewrite it to work with the translation infra.

Bug: 791716
Test: browser_test --gtest_filter=Extensi*.RatingsSectionA11y
Change-Id: Id88bad4554b106acebe20064fab8870e03a44843
Reviewed-on: https://chromium-review.googlesource.com/807353
Commit-Queue: Jungshik Shin <jshin@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: Mark Mentovai <mark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521799}

https://webrtc.googlesource.com/src.git/+log/83d27683a83d..c3da1e61bccf

$ git log 83d27683a..c3da1e61b --date=short --no-merges --format='%ad %ae %s'

Created with:
  roll-dep src/third_party/webrtc
BUG=None,None,None,None,None,None,None,None,None,None,None,None,None,None,None,None,None,None,None


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: I442acc10a3cf7a445c3cf847ae34a6661ae7174c
Reviewed-on: https://chromium-review.googlesource.com/809326Reviewed-by: WebRTC Roll Bot <webrtc-autoroll@chromium.org>
Commit-Queue: WebRTC Roll Bot <webrtc-autoroll@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521798}

Bug: 761003
Change-Id: If6404fb5ee6866777ccd2bfacce1f7d235fdd17b
Reviewed-on: https://chromium-review.googlesource.com/794047
Commit-Queue: Luna Lu <loonybear@chromium.org>
Reviewed-by: Ian Clelland <iclelland@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521797}

Change 'deps' to 'data_deps' in order for this helper executable to appear in
'gn desc runtime_deps' list. It is needed to satisfy test isolation
requirements. Besides, this is just a right thing to do since compilation does
not depend on this target.

R=thestig@chromium.org,mark@chromium.org

Bug: 
Change-Id: I5d14e58ce66d2415c59d96d90439d987bbe3a92c
Reviewed-on: https://chromium-review.googlesource.com/806216Reviewed-by: Mark Mentovai <mark@chromium.org>
Commit-Queue: Mark Mentovai <mark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521796}

There was a bug with a Strict Mode violation during the
NotificationManager.notify call in DownloadNotificationService2 due to
Samsung Knox. This CL fixes that by disabling Strict Mode during that
specific call.

Bug: 789134
Change-Id: Ie1ba03c1cbef942df2c832529ca85323f73dd2be
Reviewed-on: https://chromium-review.googlesource.com/804966Reviewed-by: David Trainor <dtrainor@chromium.org>
Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Commit-Queue: Joy Ming <jming@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521795}