GitLab

NOTRY=true  # tests are covered by CQ

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

TL;DR for non-mojo reviews: No functional changes in your code. All
mechanical aesthetic changes.

This cleans up all message pipe, data pipe, and shared buffer APIs to
reflect the intended stable ABI of the initial mojo_core release, adding
extensible options structs where appropriate and homogenizing argument
ordering conventions. Also renames some badly named types and begins
eliminating the split C/C++ flag constant definitions in favor of using
C macros everywhere.

Documentation formatting is also made more consistent, and the thunk
table ordering is mostly finalized here.

The only functional change is a small drive-by bugfix in
MojoGetBufferInfo where the implementation was not filling in the actual
size of the MojoSharedBufferInfo struct. This has no effect on any
current production uses of the API.

TBR=miu@chromium.org
TBR=jam@chromium.org
TBR=kinuko@chromium.org

Bug: 819046
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: I5c1019bf1fe95a9295a0d053544e867fdebadde8
Reviewed-on: https://chromium-review.googlesource.com/1041149
Commit-Queue: Ken Rockot <rockot@chromium.org>
Reviewed-by: Jay Civelli <jcivelli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555808}

In ContentViewRenderView, waiting an extra frame to remove the
background prevents flashes of black from Android's default Surface
content, and flashes of the compositor's default background.

Bug: internal b/73804884
Test: repro bug
Change-Id: Ib221403890200be6e842e0d85780d18db859d159
Reviewed-on: https://chromium-review.googlesource.com/1041185Reviewed-by: Bo <boliu@chromium.org>
Commit-Queue: Thoren Paulson <thoren@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555807}

PaintLayer::GetBackgroundPaintLocation returns a mask of where the
background should paint and is used for determining if composited
scrolling can occur at all through:
PaintLayerScrollableArea::ComputeNeedsCompositedScrolling.

If composited scrolling is not used, callsites handle not actually
painting onto the scrolling contents layer, see:
CompositedLayerMapping::UpdateBackgroundPaintsOntoScrollingContentsLayer

This patch breaks the dependency cycle introduced by [1]. Instead of
querying compositing state, this patch special-cases the root layer
so that kBackgroundPaintInScrollingContents can be returned even if
there is no overflow because the root layer creates scrolling contents
layers in this case.

[1] https://crrev.com/9e0775c12ad12

Bug: 835755
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: I139f2f85c68d267de80c7b1e534a9fcef9af3983
Reviewed-on: https://chromium-review.googlesource.com/1042529Reviewed-by: Steve Kobes <skobes@chromium.org>
Commit-Queue: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555806}

|childWindowsDidChange| was removed from the delegate, so these methods
are now noops.

Change-Id: I5becdd5797c0adc14a9c2f53d0f78d5ce684ceea
Reviewed-on: https://chromium-review.googlesource.com/1040946Reviewed-by: Sidney San Martín <sdy@chromium.org>
Commit-Queue: Leonard Grey <lgrey@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555805}

It has another cert for OCSP tests not used by the EmbeddedTestServer.

Bug: 755309
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: Ic43314cf9f8e2978848a75764a4323ce34b0006a
Reviewed-on: https://chromium-review.googlesource.com/1033192
Commit-Queue: Matt Menke <mmenke@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Ryan Sleevi <rsleevi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555804}

Updates to the media_router WATCHLIST:
- Add c/b/ui/media_router/
- Fix the path for c/common/media_router/

Change-Id: I286bbae96da0f801997e69634642a19001e46ac6
Reviewed-on: https://chromium-review.googlesource.com/1042276Reviewed-by: Adam Parker <amp@chromium.org>
Commit-Queue: Takumi Fujimoto <takumif@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555803}

Since b66db7c4, WebView can now get the
channel. Variations uses this to filter experiments.

Stand-alone WebView will report "unknown" channel. Experiments which do
not specify any channel will apply to stand-alone WebView; see
CheckStudyChannel in study_filtering.cc.

BUG=758290

Change-Id: I6174b63c6995cb950e5ec349891ad579d24e7396
Reviewed-on: https://chromium-review.googlesource.com/1041206Reviewed-by: Bo <boliu@chromium.org>
Commit-Queue: Paul Miller <paulmiller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555802}

TBR=nednguyen@google.com
NOTRY=true

Bug: 839494
Change-Id: Idd671cbbf0cdd81f7a3417573d03e4e6cda6e4c6
Reviewed-on: https://chromium-review.googlesource.com/1042282Reviewed-by: Annie Sullivan <sullivan@chromium.org>
Commit-Queue: Annie Sullivan <sullivan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555801}

Bug: 598073

Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: I59722f8aa6c1946c3f2cf00bbbad0d8c96e0d12f
Reviewed-on: https://chromium-review.googlesource.com/1041486Reviewed-by: Matt Menke <mmenke@chromium.org>
Commit-Queue: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555800}

In crrev.com/c/1013221, we want to disable TouchpadOverscrollHistoryNavigation
on Windows and Linux. But we also disable it on CrOS because I forgot checking
OS_CHROMEOS. In this patch, we enable TouchpadOverscrollHistoryNavigation on
OS_CHROMEOS which is same as today stable.

TouchpadOverscrollHistoryNavigation is Aura only, OS_MACOSX does not check
this flag.

Bug: 838741
Change-Id: Ib9362bc74af1cb800fab665079017fbcb7880402
Reviewed-on: https://chromium-review.googlesource.com/1039867Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Commit-Queue: Jianpeng Chao <chaopeng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555799}

TBR=nednguyen@google.com
NOTRY=true

Bug: 839470
Change-Id: I7010d53bfdc84b9ac540735df8be060c9e5c2735
Reviewed-on: https://chromium-review.googlesource.com/1042279Reviewed-by: Annie Sullivan <sullivan@chromium.org>
Commit-Queue: Annie Sullivan <sullivan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555798}

Add a third earcon for dictation cancelled, and modify which earcon
plays when so the user is more aware of the current dictation state.

Bug: 801398
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I3af2dd619e493e7697be5b5628539d9f6a56c7f1
Reviewed-on: https://chromium-review.googlesource.com/1040364Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Commit-Queue: Zach Helfinstein <zhelfins@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555797}

Known issues:
 * Skia doesn't support creating promise image from YUV textures.
   https://crbug.com/skia/7902
 * Skia doesn't support drawing YUV textures directly, we have to
   convert YUV textures to a RGB textures first. https://crbug.com/skia/7901
 * Skia doesn't support alpha channel for YUV format.
   https://crbug.com/skia/7903

Test: Test it with YouTube
Cq-Include-Trybots: 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;luci.chromium.try:win_optional_gpu_tests_rel
Change-Id: Ia9fdc3d3ce972035025d3aec3813eef97619c6ed
Reviewed-on: https://chromium-review.googlesource.com/1003228Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Reviewed-by: Michael Wasserman <msw@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Commit-Queue: Peng Huang <penghuang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555796}

These policies are intended to allow developers to control which image
formats are supported on their pages (and on the pages they embed,) and
to enforce that images used are well compressed and not full of
metadata which does not contribute to the displayed image.

Explainers for these features can be found at
https://github.com/WICG/feature-policy/blob/gh-pages/policies/optimized-images.md

Bug: 837348, 837350
Change-Id: Ie92517291a453286ca0d745f8dc497f040c06592
Reviewed-on: https://chromium-review.googlesource.com/1033726Reviewed-by: Nate Chapin <japhet@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Commit-Queue: Ian Clelland <iclelland@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555795}

Part of ongoing effort to get automation tree working
in chromecast.

PS 1 is baseline for copied files. Modifications on top
of that in PS >=2.

Bug: 73383411
Test: None
Change-Id: I30328354dd523f1dc5aadbf7eda708e6be4ba5d2
Reviewed-on: https://chromium-review.googlesource.com/1035447Reviewed-by: Alex Sakhartchouk <alexst@chromium.org>
Reviewed-by: David Tseng <dtseng@chromium.org>
Commit-Queue: Randy Rossi <rmrossi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555794}

Bug: 814860
Change-Id: I53c9de7111efb35e73317245647e3659e3bc4a6d
Reviewed-on: https://chromium-review.googlesource.com/1040271
Commit-Queue: Rebekah Potter <rbpotter@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555793}

The raw pointer returned by GetNetworkContext() shouldn't be hold onto. This
CL adds documentation to the method and fixes devtools_server.cc to not hold
onto the raw pointer as a member.

Bug: 821000
Change-Id: If6e1a7c9a6742980755ffabd4c3b0d8fe0fa392e
Reviewed-on: https://chromium-review.googlesource.com/1042352Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Commit-Queue: Helen Li <xunjieli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555792}

This Cl is the first in a 3 CL series to move the NavigationRequest
creation to the NavigationController. The end goal is to have Navigator
take a NavigationRequest as an argument to Navigate instead of the
pending NavigationEntry.

Summary of the changes in this CL:
1) Navigator
 - NavigatorImpl::RequestTransferURL becomes NavigateFromFrameProxy. It calls
   NavigationControllerImpl::NavigateFromFrameProxy instead of creating a
   NavigationEntry and navigating to it directly.
 - NavigatorImpl::NavigateNewChildFrame becomes
   StartHistoryNavigationInNewChild. It calls
   NavigationControllerImpl::StartHistoryNavigationInNewChild instead of creating
   a NavigationEntry and navigating to it directly.

2) NavigationController:
 - StartHistoryNavigationInNewChild is a new function that contains code that
   used to be in NavigatorImpl::NavigateNewChildFrame. It is called when creating
   a subframe during a history navigation. It will try to perform a history
   navigation in the child frame.
 - NavigateFromFrameProxy is a new function that contains code moved from
   NavigatorImpl::RequestTransferURL. It creates a NavigationEntry and a
   NavigationRequest for the navigation, and asks the Navigator to perform them.

Bug: 803859
Change-Id: I45891c21dc8f1e86e3f1bc1829ee3a92af1a5bfb
Reviewed-on: https://chromium-review.googlesource.com/959012
Commit-Queue: Camille Lamy <clamy@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555791}

https://webrtc.googlesource.com/src.git/+log/01042067beb1..a1f566b28a69

$ git log 01042067b..a1f566b28 --date=short --no-merges --format='%ad %ae %s'

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


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
TBR=webrtc-chromium-sheriffs-robots@google.com

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

This prevents builders of different archs from overwriting each
other.

Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester
Change-Id: I5a1e88601e0872e51282d52bb5151fcedd02ab3b
Reviewed-on: https://chromium-review.googlesource.com/1042354Reviewed-by: Andrei Kapishnikov <kapishnikov@chromium.org>
Commit-Queue: Paul Jensen <pauljensen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555789}

When the target element of a paint worklet has an associated link, then
the 'paint' function will be invoked when the link's href is changed
from a visited URL to an unvisited URL (or vice versa).

This CL changes the behavior by detecting whether the target element
of a paint worklet has an associated link or not. If it does, then don't
paint.

TBR=haraken@chromium.org

Bug: 835589
Change-Id: I5fdf85685f863c960a6f48cc9a345dda787bece1
Reviewed-on: https://chromium-review.googlesource.com/1035524Reviewed-by: Xida Chen <xidachen@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Commit-Queue: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555788}

Add a browser test for extension updater when an extension is uninstalled
in the middle of an update session.

This is to verify changes in https://chromium-review.googlesource.com/1033468
and https://chromium-review.googlesource.com/1037906.

Bug: 837371
Change-Id: I9754b21b0afb67b158c2b36b795898fb584d432e
Reviewed-on: https://chromium-review.googlesource.com/1041161
Commit-Queue: Minh Nguyen <mxnguyen@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: Sorin Jianu <sorin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555787}

TouchscreenScroll user action used to show the frequency of GSBs
with touchscreen source; it's not needed anymore since the performance
scrolling metrics for ScrollBegin show the frequency.

Bug: 838700
Change-Id: If74fc0ad2cda1ac4e2a3ae14939b04e468b2b35d
Reviewed-on: https://chromium-review.googlesource.com/1017015Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Commit-Queue: Sahel Sharifymoghaddam <sahel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555786}

https://chromium.googlesource.com/catapult.git/+log/a87e87c2a7f4..19282cf9d32d

$ git log a87e87c2a..19282cf9d --date=short --no-merges --format='%ad %ae %s'
2018-05-03 simonhatch Dashboard - Remove find_change_points_exp
2018-05-03 nednguyen Update method names in cache_temperature_unittes to be consistent with Telemetry code style

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.


TBR=sullivan@chromium.org

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

This CL makes the accessory a real keyboard accessory and not just a
component that happens to be shown sometimes when a caller decides to.

The keyboard accessory can be shown due to a variety of reasons:
- there are suggestions to show
- there are password actions available for this site
- there is general help available for this site (i.e. bottom sheets)

Therefore, having providers of suggestions or actions decide when to
show the accessory would move the responsibility to callers although
the mediator has all data to decide the state - probably even more than
the caller.

Bug: 828832
Change-Id: I648c73cb1c14c19c38da64dc40692e96e6ca56c6
Reviewed-on: https://chromium-review.googlesource.com/1028230Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
Commit-Queue: Friedrich Horschig <fhorschig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555784}

It is failing flakily.

NOTRY=true
TBR=nednguyen@google.com

Bug: 839470
Change-Id: Ia5657133812ffa541dca0ff0c72db819ee7163ea
Reviewed-on: https://chromium-review.googlesource.com/1042271Reviewed-by: Annie Sullivan <sullivan@chromium.org>
Commit-Queue: Annie Sullivan <sullivan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555783}

Bug: 776877
Cq-Include-Trybots: 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
Change-Id: I9d9590a5174db94392a447ab280e9218b37c2958
Reviewed-on: https://chromium-review.googlesource.com/1040725Reviewed-by: Antoine Labour <piman@chromium.org>
Commit-Queue: Peng Huang <penghuang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555782}

Download links from chrome://indexeddb-internals/ always give empty zip file

Bug: 819207
Change-Id: I3490fdf5e837c91cec5cbaf0ebbdfd892471be5e
Reviewed-on: https://chromium-review.googlesource.com/1038864Reviewed-by: Joshua Bell <jsbell@chromium.org>
Commit-Queue: Joshua Bell <jsbell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555781}

This will let us keep skcms `gn analyze` compatible more easily.

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

https://chromium.googlesource.com/chromiumos/chromite.git/+log/5295eaac6d22..8642bcc3248f

$ git log 5295eaac6..8642bcc32 --date=short --no-merges --format='%ad %ae %s'
2018-05-01 bmgordon cbuildbot_launch: Remove old state handling

Created with:
  roll-dep src/third_party/chromite
BUG=chromium:829665


The AutoRoll server is located here: https://chromite-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.


TBR=chrome-os-gardeners@chromium.org

Change-Id: I657a9225a76249b9e4a18304f426bc5bee42a305
Reviewed-on: https://chromium-review.googlesource.com/1042378Reviewed-by: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#555779}

Add a render test that checks layout of:
 - peeking bar
 - card while its thumbnail is loading
 - card after the thumbnail has loaded
 - card with offline badge
 - full sheet
 - full sheet scrolled

BUG=835450

Change-Id: I8860d9eca6fd7f54e794b08076749cae0f3ecbe1
Reviewed-on: https://chromium-review.googlesource.com/1039876
Commit-Queue: Theresa <twellington@chromium.org>
Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555778}

Previously WaitUntilEnded() would not install an on-error closure, and
so would fail to exit on pipeline errors, causing the test to hang
rather than fail.

WaitUntilEnded() now waits for either end or error, and EXPECTs a
PIPELINE_OK status before returning.

Also tweaked the naming of RunUntilIdle* to RunUntilQuit to avoid
confusion with the RunLoop::RunIntilIdle() API behaviour.

Bug: 836785
Change-Id: Idcf9bbec5ac0d7d78e2ba0530eaed0748a1626c8
Reviewed-on: https://chromium-review.googlesource.com/1041807Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Commit-Queue: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555777}

This reverts commit e02bb35e.

Why? Previous-step cl/193316519 is rolled back as this feature breaks working
sites, and further refinement is necessary before it should be enabled by
default. See https://crbug.com/729954#c26 onwards.

Bug: 729954,837771
Change-Id: I806364dc9a5812a0e57f76f4a3db02e6803a8d5f
Reviewed-on: https://chromium-review.googlesource.com/1042535Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Commit-Queue: Ami Fischman <fischman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555776}

Bug: None
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel
Change-Id: I502f8f0c154fcc319cd3c5170cee53d9eb940f32
Reviewed-on: https://chromium-review.googlesource.com/1040847Reviewed-by: weiliangc <weiliangc@chromium.org>
Commit-Queue: Antoine Labour <piman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555775}

Versions /1 and /2 (viz hit testing) are flaky, but /0 is fine, so we'll
keep /0 enabled.

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

- Remove |enable_webrtc=false| from the Cast Audio bot configuration.
- Set |enable_webrtc=true| by default, rather than based on whether
  |is_cast_audio_only| is set.

This requires a roll of OpenH264 to pick up changes that fix it not to
use pthreads APIs that are not present under Fuchsia.

Bug: 800653
Change-Id: Ieaa5b10bd64aab421db8163dd260b1283068d362
Reviewed-on: https://chromium-review.googlesource.com/1039766Reviewed-by: Henrik Boström <hbos@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Reviewed-by: Stephen Lanham <slan@chromium.org>
Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555773}

Bug: 838609
Change-Id: Idd7f0043064894b414565d2d4e4955658b9cfccb
Reviewed-on: https://chromium-review.googlesource.com/1041069Reviewed-by: Patrick Noland <pnoland@chromium.org>
Commit-Queue: Sky Malice <skym@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555772}

When signin cookies are "cleared on exit" through the Chrome settings,
Dice would rebuild them on next startup, which defeats the point of
that cookie settings.
To fix this, tokens are not loaded when signin cookies are cleared on
exit. Instead, the tokens are revoked on the server, and deleted from
the database.
The secondary accounts are completely removed from Chrome, but the
primary account is kept in authentication error state, so that Sync
can display an error.

TBR=treib, eugenebut

Bug: 836862
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: I5a72b3a173242494ad1c996765c838bb9a7f09f1
Reviewed-on: https://chromium-review.googlesource.com/1042392
Commit-Queue: David Roger <droger@chromium.org>
Reviewed-by: Marc Treib <treib@chromium.org>
Reviewed-by: Mihai Sardarescu <msarda@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555771}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/e043a8b3..1f462965

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: Ic0de3034053e0f7368ba535b770ae0bd2e92bfa8
Reviewed-on: https://chromium-review.googlesource.com/1042211Reviewed-by: v8 autoroll <v8-autoroll@chromium.org>
Commit-Queue: v8 autoroll <v8-autoroll@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555770}