GitLab

https://pdfium.googlesource.com/pdfium.git/+log/a1ea4276f87f..c765d2ac8676


git log a1ea4276f87f..c765d2ac8676 --date=short --no-merges --format='%ad %ae %s'
2018-06-19 vmiklos@collabora.co.uk Add FPDFText_GetMatrix() API
2018-06-19 art-snake@yandex-team.ru Use const pointers within GetDirectInteger function.


Created with:
  gclient setdep -r src/third_party/pdfium@c765d2ac8676

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: Ibd4c206a4321d4097081a7697f3db32238e16f0e
Reviewed-on: https://chromium-review.googlesource.com/1106357Reviewed-by: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#568523}

It does nothing.

Change-Id: I9f170d43a18fe5e07032fd1f4a8e093a65992ee4
Reviewed-on: https://chromium-review.googlesource.com/1106003Reviewed-by: Florin Malita <fmalita@chromium.org>
Commit-Queue: Mike Klein <mtklein@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568522}

Bug:713357
Change-Id: I559932e082f59f4dd918caca971d5e6eae688490

NOTRY=true # CQ flaky

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

The new tab button ink drop needed a larger size than the default
and overriding to pass bounds size corrected a rendering artifact
on the highlight.

Bug: 853700
Change-Id: Iff98f43049df3fa0c7142c3213707f423b6b1c14
Reviewed-on: https://chromium-review.googlesource.com/1105487
Commit-Queue: Orin Jaworski <orinj@chromium.org>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568520}

Bug: 773382
Change-Id: Ie7cbbf2c74bfbf1f1522b2a1f775a392545ad0a9
Reviewed-on: https://chromium-review.googlesource.com/1088196
Commit-Queue: Sébastien Marchand <sebmarchand@chromium.org>
Reviewed-by: François Doray <fdoray@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568519}

The "multidevice" settings-section is only suppose to appear when the
Chrombook has a potential host. This information comes from a mojo
call on that takes place further down the DOM tree than the basic-page
element so the connected devices infrastructure must itself be able to
detach any significant elements based on the results of the mojo call.
By wrapping the entire multidevice settings-section element in a
separate container element, we can make the container keep the entire
section from the DOM without tinkering further up the tree.

Change-Id: I766164a2d04ea42f77bb0c101a17c2e1eadad016
Cq-Include-Trybots: luci.chromium.try:closure_compilation
Reviewed-on: https://chromium-review.googlesource.com/1105185Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Commit-Queue: Jordy Greenblatt <jordynass@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568518}

Update the incognito NTP background color to match the modern incognito
toolbar color. Also update some text colors and remove the toolbar
shadow when the incognito NTP is showing. A future CL will show the shadow
on scroll.

BUG=814881

Change-Id: I1995ec644781268ea1054a457dde0593d16fb0f9
Reviewed-on: https://chromium-review.googlesource.com/1105379Reviewed-by: Ted Choc <tedchoc@chromium.org>
Reviewed-by: Becky Zhou <huayinz@chromium.org>
Commit-Queue: Theresa <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568517}

Bug: 678885
Change-Id: I52f8062a480c2657827dffda231382f48b2b6ef6
Reviewed-on: https://chromium-review.googlesource.com/1096536
Commit-Queue: Kim Paulhamus <kpaulhamus@chromium.org>
Reviewed-by: Maria Khomenko <mariakhomenko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568516}

This can be nullptr and this is always checked against nullptr
except this place.

BUG=NONE
TEST=covered by unit test

Change-Id: Ie96065820a16dd14552a03d62ae7b06b4e2facb6
Reviewed-on: https://chromium-review.googlesource.com/1105698Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Mitsuru Oshima <oshima@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568515}

Also clean up the code and re-enable
RenderWidgetHostViewGuestSurfaceTest.TestGuestSurface.

Bug: 730193, 844469
Change-Id: I20f17fda6094b1ffb6bbb1482ccd14f6c20175ea
Reviewed-on: https://chromium-review.googlesource.com/1104798
Commit-Queue: Saman Sami <samans@chromium.org>
Reviewed-by: Fady Samuel <fsamuel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568514}

[Cros Multidevice] tether::HostScanScheduler: Remove restrictions on host scans if SecureChannel API is present.

This conditionally (behind the chromeos::features::kMultiDeviceApi flag) removes the
following restrictions introduced by the following CLs:
1) "Stop scans when device is locked": https://chromium-review.googlesource.com/c/chromium/src/+/940609
2) "Do not perform host scans while the device is locked": https://chromium-review.googlesource.com/c/chromium/src/+/1045254
3) "Delay host scans slightly after unlock": https://chromium-review.googlesource.com/c/chromium/src/+/941583

These restricitons were necessary because Tether and Smart Lock used different BLE comminication stacks. Now that the
SecureChannel API is integrated into Tether (the BLE communication scheme that Tether and Smart Lock share), these
restrictions are no longer necessary.

Bug: 824568, 752273, 817554
Change-Id: Id63ba851c702502420ae42b99efcd5f18102aa34
Reviewed-on: https://chromium-review.googlesource.com/1105618Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Commit-Queue: Ryan Hansberry <hansberry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568513}

The system touches need to be cancelled whenever the context menu is
shown in order to prevent webview interaction after the context menu is
displayed.

Wait until the context menu element is available before determining if
the element supports a displyed context menu.

Bug: 853298
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I15bd7d4148f83646763504dd8370dce49e37dff3
Reviewed-on: https://chromium-review.googlesource.com/1104989
Commit-Queue: Mike Dougherty <michaeldo@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568512}

Bug: 789632
Cq-Include-Trybots: luci.chromium.try:linux_mojo
Change-Id: Idbea61afbedd446993f01f5701a8f4ef484c5926
Reviewed-on: https://chromium-review.googlesource.com/1103188
Commit-Queue: Clark DuVall <cduvall@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568511}

When zoom-for-dsf enabled, element_bound_in_document is in physical pixel;
however, minReadableCaretHeight is hard-coded css pixel value. So we need
to applied page zoom factor to the min caret height before calculate the
new page scale.

Bug: 848434
Change-Id: I3fe529032fbc380f4dc90a42a0fef532b79ba38b
Reviewed-on: https://chromium-review.googlesource.com/1085559
Commit-Queue: Ella Ge <eirage@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568510}

Until now, we had to use IsSecureContext() to check whether an execution
context is a secure context manually. But we can use [SecureContext]
instead of the manual check now. After this change, all related APIs
including ServiceWorkerContainer will not be exposed in non-secure
context.

Chrome status: https://www.chromestatus.com/feature/4835970390163456

Bug: 542499, 854058
Change-Id: I0e207fee5c591d595c0e11c121cc8a0f555b5be3
Reviewed-on: https://chromium-review.googlesource.com/818666
Commit-Queue: Jinho Bang <jinho.bang@samsung.com>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568509}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/7edcaa70..c9229d20

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

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

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,machenbach@chromium.org,kozyatinskiy@chromium.org,sergiyb@chromium.org

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

This CL removes un-necessary allocations in LocaleUtils.java
and moves the matching Python CHROME_TO_ANDROID_LANGUAGE_MAP
variable to resource_utils.py, in preparation of a future CL
where it will be used by another Python script as well.

BUG=846633
R=agrieve@chromium.org, jbudorick@chromium.org, estevenson@chromium.org

Change-Id: Ie6eba71b259c2fef410afe526b7478dc56866887
Reviewed-on: https://chromium-review.googlesource.com/1106162Reviewed-by: agrieve <agrieve@chromium.org>
Commit-Queue: David Turner <digit@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568507}

With the new autoplay policy, the heuristic to take audio focus for
muted autoplay no longer works and web pages ends up stealing audio
focus for no audible reasons.

Bug: 845016
Change-Id: Ie34d3a66ac5027720fe4ee4546b4c320127f3870
Reviewed-on: https://chromium-review.googlesource.com/1087784Reviewed-by: Camille Lamy <clamy@chromium.org>
Reviewed-by: Dan Sanders <sandersd@chromium.org>
Reviewed-by: Becca Hughes <beccahughes@chromium.org>
Commit-Queue: Mounir Lamouri <mlamouri@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568506}

SendCached.*() never works as our imagination goes.
Cached found devices are always ignored in SendDevices().

Also sends out paired devices in SendCachedDevicesFound(). A paired
device can still have different UUIDs from last time we report to
Android, which should get the latest UUID list as long as it's scanning.
As a matter of fact, the secure client test needs to know the updated
UUIDs on a paired device in order to figure out which one to connect to.

This has an impact on crbug/853037 and crbug/841041 also, as devices are
always paired before connected in BlueZ.

BUG=b:78593133,chromium:853037,chromium:841041
TEST=Confirm from logs that UUIDs are updated even for paired devices

Change-Id: I6f1dae8be9bb1eb9b0d8cb5c2a146ec07d4ee099
Reviewed-on: https://chromium-review.googlesource.com/1105559
Commit-Queue: Qiyu Hu <qiyuh@google.com>
Reviewed-by: Luis Hector Chavez <lhchavez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568505}

Bug: 715355
Change-Id: I246fe81e0d51d27f53135a9664e8a1bbf5f84bfa
Reviewed-on: https://chromium-review.googlesource.com/1105197
Commit-Queue: Stuart Langley <slangley@chromium.org>
Reviewed-by: Sasha Morrissey <sashab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568504}

Several chrome extensions namespace aliases are declared both in
namespace extensions:: and extensions::(anonymous). This is not failing
in non-jumbo build as on each unit it is declared one time. But on jumbo
build same compilation unit includes both aliases, breaking compilation.

Bug: 746956
Change-Id: Ic2255b204a832e7079bda24afb7e8769658dc2e4
Reviewed-on: https://chromium-review.googlesource.com/1105052Reviewed-by: Toni Barzic <tbarzic@chromium.org>
Commit-Queue: José Dapena Paz <jose.dapena@lge.com>
Cr-Commit-Position: refs/heads/master@{#568503}

Bug: 854239
Change-Id: If6d20625d0bacac7020c4729bba77491f2b435f4
TBR: charliea@chromium.org
NOTRY: true
Reviewed-on: https://chromium-review.googlesource.com/1106430Reviewed-by: Annie Sullivan <sullivan@chromium.org>
Commit-Queue: Annie Sullivan <sullivan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568502}

Adds metrics for duration of ReadDirectory

Bug: 757625
Change-Id: I03a30296a01db87fdc2c1133c512385d6a6bc967
Reviewed-on: https://chromium-review.googlesource.com/1099692Reviewed-by: Brian White <bcwhite@chromium.org>
Commit-Queue: Allen Vicencio <allenvic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568501}

This CL introduces the main skeleton of the observer implementation,
and the necessary wiring into the processor.

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

The only thing the native CVC does now is (as an WebContentsObserver)
adjust renderer view focus/screen info when renderer is updated.
This CL moves that reponsibility to WebContentsAndroid, and deletes
the entire class. There is no functional change.

Bug: 598880
Change-Id: I9a1f3a2e0df5457439a27675d3786aa6703e06ac
Reviewed-on: https://chromium-review.googlesource.com/1083911Reviewed-by: Bo <boliu@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568499}

- Add hotword listening settings entry
- Update logic for enable Assistant

Bug: b/78191741
Cq-Include-Trybots: luci.chromium.try:closure_compilation
Change-Id: Ibeb5230e6a550c38a1d01ac4edee505ccf6db478
Reviewed-on: https://chromium-review.googlesource.com/1099717
Commit-Queue: Yue Li <updowndota@chromium.org>
Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Luis Hector Chavez <lhchavez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568498}

Nothing was receiving this yet so it should be safe to change.

Bug: 649026
Change-Id: I964e91edab78f94f08b20dc89eeb2dd09879dc8c
Reviewed-on: https://chromium-review.googlesource.com/1105465Reviewed-by: Emily Stark <estark@chromium.org>
Commit-Queue: Matt Mueller <mattm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568497}

WebContents activates the "disable rendering" optimisation when the
WebContents is hidden. This means that when a video is playing in
Picture-in-Picture, then the WebContents is hidden, the video will stop
playing in the Picture-in-Picture window.

Similarly to content capturing (e.g. mirroring / tab capture), this
optimisation should not be activated when in Picture-in-Picture mode.

This will only affect one tab at a time, as users cannot enter
Picture-in-Picture mode from multiple tabs.

Bug: 848812
Change-Id: I98a0e769ad4c412ea50db4de2ab63e64f3b752f2
Reviewed-on: https://chromium-review.googlesource.com/1105339Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: apacible <apacible@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568496}

Adding collapsableMode property in ListMode which can have 2 values:
 + ListModelCollapsableModeHeader
 + ListModelCollapsableModeFirstCell

The header mode is used to when the header to collapse a section. When
collapsed, a section contains no item.

The first cell mode is used to when the first cell to collapse a
section. When collapsed, a section contains the first item.


Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: If46f85d5c412b1b799099635fefe7a8c8d11bbf2
Reviewed-on: https://chromium-review.googlesource.com/1101558
Commit-Queue: Jérôme Lebel <jlebel@chromium.org>
Reviewed-by: Sergio Collazos <sczs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568495}

CL to enable on Dev and Canary: http://cl/200424143

Bug: 750327
Change-Id: Ica7ac69480d5739d4cc35d692b911c51f6547b15
Reviewed-on: https://chromium-review.googlesource.com/1104949Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Varun Khaneja <vakh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568494}

This is used by Chromevox.

Bug: b/110195060
Test: manual
Change-Id: I9e22aacf0c3335d70eb92ea9b66f6e11a7ef2f7c
Reviewed-on: https://chromium-review.googlesource.com/1105028
Commit-Queue: Kevin Schoedel <kpschoedel@chromium.org>
Reviewed-by: Alex Sakhartchouk <alexst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568493}

interface is macro for struct in some Windows headers which
causes problems when Windows headers get exposed to code that
has named variables or functions interface. This happened
with the newly added jumbo support in chrome/browser/extensions.

Bug: 850484
Change-Id: I5d838bad5658bfe97542b32647e182348f63c4cc
Reviewed-on: https://chromium-review.googlesource.com/1106339Reviewed-by: Ken Rockot <rockot@chromium.org>
Commit-Queue: Daniel Bratell <bratell@opera.com>
Cr-Commit-Position: refs/heads/master@{#568492}

- Add a string to list extensions under items to be removed.
- Modify confirmation message to clarify to users that their extensions
  were disabled because of the settings reset.

Bug: 853339
Change-Id: Ie57d4434ab5aa89f287038a1d45e0840678991aa
Reviewed-on: https://chromium-review.googlesource.com/1103220Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Commit-Queue: Nick Burris <nburris@google.com>
Cr-Commit-Position: refs/heads/master@{#568491}

https://skia.googlesource.com/skia.git/+log/f2030783094e..ba61029c5b49


git log f2030783094e..ba61029c5b49 --date=short --no-merges --format='%ad %ae %s'
2018-06-19 caryclark@skia.org fix op fuzz timeout
2018-06-19 angle-skia-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com Roll third_party/externals/angle2 2dabb4a367c3..7df52383cfdf (1 commits)
2018-06-19 fmalita@chromium.org Use SkJSONWriter for viewer UI serialization
2018-06-19 caryclark@skia.org fix bookmaker files
2018-06-19 caryclark@skia.org fix fuzzer bugs in pathops


Created with:
  gclient setdep -r src/third_party/skia@ba61029c5b49

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;luci.chromium.try:win_optional_gpu_tests_rel

BUG=chromium:831647,chromium:853938
TBR=kjlubick@chromium.org

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

This makes the 16 elevation shadow for the Omnibox match the specs
given for MD Refresh.

This CL also divorces the Omnibox shadows from the Aura window shadow
drawing logic.

Bug: 845305, 823535
Change-Id: Ibbda26b465b528805a1be591a23a20cc09df7643
Reviewed-on: https://chromium-review.googlesource.com/1100006Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Tommy Li <tommycli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568489}

The NetworkService currently ignores all Reporting headers, since we
haven't implemented the BACKGROUND_SYNC permissions check in a way that
works across service/process boundaries.  This adds a browser test that
verifies this (and while we're at it, verifies that we _don't_ ignore
Reporting headers when we're using the legacy non-service network
stack).

Bug: 845559
Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester;luci.chromium.try:linux_mojo;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I3e7c1ab446e067e7f8af6fd80d3abc9b2d5187ad
Reviewed-on: https://chromium-review.googlesource.com/1067465
Commit-Queue: Douglas Creager <dcreager@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568488}

Set the document title to the title of the tab being printed, so that
the task manager will show the correct task title.

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

This reverts commit 5916ae31.

Bug: 854102
Reason for revert: Renderers still crashing - will have to investigate further.

Original change's description:
> Reland "[SessionStorageS13N] Enabling mojo SessionStorage by default"
> 
> This is a reland of 1bd58466
> 
> Original change's description:
> > [SessionStorageS13N] Enabling mojo SessionStorage by default
> > 
> > Bug: 716490
> > Change-Id: I08c9bc35d1e9f8f86adc6c88fb7ab8069bcf7e8f
> > Reviewed-on: https://chromium-review.googlesource.com/1072918
> > Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
> > Reviewed-by: John Abd-El-Malek <jam@chromium.org>
> > Commit-Queue: Daniel Murphy <dmurph@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#563169}
> 
> Bug: 716490
> Change-Id: I5c5911a5f98e84934837fb9025431a8f98bea6ba
> Reviewed-on: https://chromium-review.googlesource.com/1104825
> Reviewed-by: John Abd-El-Malek <jam@chromium.org>
> Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
> Commit-Queue: Daniel Murphy <dmurph@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#568244}

TBR=dmurph@chromium.org,jam@chromium.org,mek@chromium.org

Change-Id: I5cb433aa9dd9acefb8cb34cb9cc7e5820b9931cf
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 716490
Reviewed-on: https://chromium-review.googlesource.com/1106398Reviewed-by: Daniel Murphy <dmurph@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568486}

[1] introduced AudioServiceLaunchOnStartup feature which we want to roll out
with a new experiment group. Updating field trial to run the config on bots
first.

[1] https://chromium-review.googlesource.com/c/chromium/src/+/1104681

Bug: 851611,853781
Change-Id: I3796a8ac205a6d37706a86e8647c933ee510f41a
Reviewed-on: https://chromium-review.googlesource.com/1105957Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Commit-Queue: Olga Sharonova <olka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568485}

Bug: 851163
Change-Id: I651da22403ba5597667549970b29d7d47a62f73b
Reviewed-on: https://chromium-review.googlesource.com/1105491Reviewed-by: Mike Wittman <wittman@chromium.org>
Commit-Queue: Xi Cheng <chengx@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568484}