GitLab

Original change's description:
> Revert "[On-device adaptive brightness] Implement an AlsReader to ambient light."
> 
> This reverts commit ea692f36.
> 
> Reason for revert: broke the linux-chromeos-dbg (https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/linux-chromeos-dbg/7744)
> 
> Original change's description:
> > [On-device adaptive brightness] Implement an AlsReader to ambient light.
> > 
> > 
> > Bug: 881215
> > Change-Id: I1cd5bf7ea517e426b54df1f4ebbb5a843b991dbe
> > Reviewed-on: https://chromium-review.googlesource.com/1209000
> > Reviewed-by: Michael Martis <martis@chromium.org>
> > Reviewed-by: Dan Erat <derat@chromium.org>
> > Commit-Queue: Jia Meng <jiameng@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#589843}
> 
> TBR=derat@chromium.org,jiameng@chromium.org,martis@chromium.org
> 
> Change-Id: Id12029b7d3b46eaed672525fe0bcf96960ea143c
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Bug: 881215
> Reviewed-on: https://chromium-review.googlesource.com/1215603
> Reviewed-by: Jia Meng <jiameng@chromium.org>
> Commit-Queue: Jia Meng <jiameng@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#589850}

TBR=derat@chromium.org,jiameng@chromium.org,martis@chromium.org

Change-Id: I8f170731509b2b23d469519fd45d5876175111d5
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 881215
Reviewed-on: https://chromium-review.googlesource.com/1217962Reviewed-by: Jia Meng <jiameng@chromium.org>
Commit-Queue: Jia Meng <jiameng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590115}

This reverts commit bb7972c1.

Reason for revert: crbug.com/882642

Original change's description:
> [Blink/SPv175+] Change DCHECK(chunk clip escaped layer clip) to a DLOG
> 
> The PaintChunkToCcLayer algorithm was originally designed for
> SPv2 compositor, and it was expected the layerization algorithm should
> never assign a chunk to a excessively clipped layer, thus the DCHECK.
> 
> Later this algorithm was adopted in SPv175 to be used with the
> SPv1 compositor. There is a known bug that in certain corner case we
> can fail to escape clip, and the bug is difficult to fix in the
> legacy architecture. The DCHECK is expected to be a "soft" one that
> we have a fail-safe path to recover in a sane way.
> 
> This CL converts the DCHECK to a DLOG in SPv1 mode, and it should still
> trap in SPv2 mode. In addition, it reverts a workaround to a nullptr
> bug in the fail-safe path, and add a test for the fail-safe.
> 
> BUG=881788,853357
> 
> Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
> Change-Id: I4606acf4885f3344bb45a901bb2e8e46dbcda49a
> Reviewed-on: https://chromium-review.googlesource.com/1213952
> Reviewed-by: vmpstr <vmpstr@chromium.org>
> Reviewed-by: Philip Rogers <pdr@chromium.org>
> Commit-Queue: Tien-Ren Chen <trchen@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#590052}

TBR=vmpstr@chromium.org,trchen@chromium.org,pdr@chromium.org

Change-Id: I8f669d48422eb2cc3bb21db2d4866857710c3fbb
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 881788, 853357
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Reviewed-on: https://chromium-review.googlesource.com/1217712Reviewed-by: Tien-Ren Chen <trchen@chromium.org>
Commit-Queue: Tien-Ren Chen <trchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590114}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/11bc3991530d..727453b25672


git log 11bc3991530d..727453b25672 --date=short --no-merges --format='%ad %ae %s'
2018-09-10 recipe-roller@chromium.org Roll recipe dependencies (trivial).


Created with:
  gclient setdep -r src/third_party/depot_tools@727453b25672

The AutoRoll server is located here: https://autoroll.skia.org/r/depot-tools-chromium-autoroll

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

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

This reworks restricted sessions to have granular control over
specific permissions: target discovery, browser target, etc.

Target handler can now operate in autoAttachOnly mode which
is used for extensions. Previously we just banned target handler
from extension sessions, which broke OOPIF debugging for them.

Bug: 870314
Change-Id: I0c3e8860aca547bb631e2a9615e58ac33465d88e
Reviewed-on: https://chromium-review.googlesource.com/1212089Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: Pavel Feldman <pfeldman@chromium.org>
Commit-Queue: Dmitry Gozman <dgozman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590112}

https://chromium.googlesource.com/catapult.git/+log/03c80a36415d..b3b8b5883ce2


git log 03c80a36415d..b3b8b5883ce2 --date=short --no-merges --format='%ad %ae %s'
2018-09-10 bsheedy@chromium.org Refactor quests to support instrumentation and browser tests


Created with:
  gclient setdep -r src/third_party/catapult@b3b8b5883ce2

The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll

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=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:881017
TBR=sullivan@chromium.org

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

GCL: http://cl/212327439

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

https://skia.googlesource.com/skia.git/+log/52fd68762ae4..303e83e6b3c8


git log 52fd68762ae4..303e83e6b3c8 --date=short --no-merges --format='%ad %ae %s'
2018-09-10 egdaniel@google.com Let unbudgeted, unique keyed resources stay in gpu ResourceCache.
2018-09-10 jvanverth@google.com Consolidate more shadow generation code.


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

The AutoRoll server is located here: https://autoroll.skia.org/r/skia-autoroll

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

Change-Id: I4e5859559b506dcfd52fba9471699079a76eff51
Reviewed-on: https://chromium-review.googlesource.com/1217482Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#590109}

Bug: 775132
Change-Id: Ib31b7e9e5ef031abd47b4608bec5accb9181311e
Reviewed-on: https://chromium-review.googlesource.com/1217592Reviewed-by: Pavel Feldman <pfeldman@chromium.org>
Commit-Queue: Dmitry Gozman <dgozman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590108}

Bug: 866126
Change-Id: I4c300a57b7fbb9041419f9806eb0e656a22f1fbd
Reviewed-on: https://chromium-review.googlesource.com/1197791
Commit-Queue: Sky Malice <skym@chromium.org>
Reviewed-by: Filip Gorski <fgorski@chromium.org>
Reviewed-by: Becky Zhou <huayinz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590107}

Implement commit Journal operations for Journal storage on C++ side.

Bug:879855

Change-Id: I8bf9d38571a4c83f7110be2d0043a8471171ba8c
Reviewed-on: https://chromium-review.googlesource.com/1200943
Commit-Queue: Gang Wu <gangwu@chromium.org>
Reviewed-by: Filip Gorski <fgorski@chromium.org>
Reviewed-by: Sky Malice <skym@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590106}

When setting the visible rect properly, the coded size was
inadvertently also changed to be the visible rect.  This CL puts
it back.

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

This is a follow-up to http://crrev.com/c/1150824 - instead of having
Document keep track of its AXContexts, let the garbage collector do the
work for us. Each AXContext owns a Persistent<AXObjectCache>, and
the associated Document has a WeakPersistent<AXObjectCache>. That way
when the last AXContext goes out of scope, the AXObjectCache will be
cleaned up automatically.

This requires a few changes due to assumptions that AXObjectCache couldn't
outlive its corresponding document.

Bug: 867324
Change-Id: Id0479f59c9a9652b2cb321ed14369e8996748d8a
Reviewed-on: https://chromium-review.googlesource.com/1162743
Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org>
Reviewed-by: Alice Boxhall <aboxhall@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590104}

Also adjust FileEnumerator's build rules.

Change-Id: I4a151782f35518f720296c1e5ed3e14910dccfc5
Reviewed-on: https://chromium-review.googlesource.com/1215045Reviewed-by: Alexei Filippov <alph@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590103}

merge_results.py outputs a log line for every file that it 'merges'.
Some of these files are only 'merging' one file. This makes the step log
on buildbot be incredibly verbose, since there are thousands of
artifacts generated by webkit_layout_tests.

This CL changes the behavior to only log something if it's doing a
non-trivial merge. 'Merges' which only merge one file aren't logged.

Change-Id: I6e5bf7316a2f1ab41f8997582b12368c23456378
Reviewed-on: https://chromium-review.googlesource.com/1217594Reviewed-by: Robert Ma <robertma@chromium.org>
Commit-Queue: Stephen Martinis <martiniss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590102}

Using wpt-import in Chromium d476f83e.
With Chromium commits locally applied on WPT:
d7762551 "Consistently use single quotes in Background Fetch WPTs."


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

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

Directory owners for changes in this CL:
ericwilligers@chromium.org:
  external/wpt/css/motion
meade@chromium.org:
  external/wpt/web-animations

NOAUTOREVERT=true
TBR=raphael.kubo.da.costa@intel.com

No-Export: true
Change-Id: I4ad93e94f176e1809a9004d6cd2ebef266c703e2
Reviewed-on: https://chromium-review.googlesource.com/1217508
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@{#590101}

This workaround appears to mostly be necessary for compositing and
rasterization contexts, and has a performance cost when used with
WebGL. Disable it there.

Bug: 882317
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: I7dc89d11b2818f3af029d0dfb62d1a6e6fabfef3
Reviewed-on: https://chromium-review.googlesource.com/1217586Reviewed-by: ccameron <ccameron@chromium.org>
Reviewed-by: Kai Ninomiya <kainino@chromium.org>
Commit-Queue: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590100}

In some cases, vec->at(i) was used as a more-readable alternative to
(*vec)[i]. In others, it was used for const access to maps. at has
questionable interactions with exceptions (see
https://groups.google.com/a/chromium.org/forum/#!msg/cxx/6TDgM5g-NH4/NJSmyU01BgAJ),
so I've added (*vec)[i] where possible, and bounds checked everywhere.


Bug: 881604
Change-Id: Ia38ec235a8264a54ddc0dbe570c79e0227fe0f9e
Reviewed-on: https://chromium-review.googlesource.com/1217104Reviewed-by: Varun Khaneja <vakh@chromium.org>
Commit-Queue: Daniel Rubery <drubery@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590099}

Change-Id: I30d965d28b5b2713b141899e494b254f67a38df5
Reviewed-on: https://chromium-review.googlesource.com/1217759Reviewed-by: John Chen <johnchen@chromium.org>
Commit-Queue: Tatiana Buldina <buldina@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590098}

Enable on the command line by passing
"--enable-features=WebRtcHideLocalIpsWithMdns"
Check runtime setting with
base::FeatureList::IsEnabled(features::kWebRtcHideLocalIpsWithMdns)

Bug: chromium:875740
Change-Id: Ic8afd743d1b78da165cacb21ebc10837262af086
Reviewed-on: https://chromium-review.googlesource.com/1214328Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Commit-Queue: Zach Stein <zstein@google.com>
Cr-Commit-Position: refs/heads/master@{#590097}

This CL may cause a small binary size increase, roughly proportional
to how long it's been since our last AFDO profile roll. For larger
increases (around or exceeding 100KB), please file a bug against
gbiv@chromium.org. Additional context: https://crbug.com/805539

The AutoRoll server is located here: https://autoroll.skia.org/r/afdo-chromium-autoroll

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

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

The number 8 for the initial capacity was picked at random.

This seems to help especially with the float perf tests.

Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
Change-Id: Ie4217a459848e7269c791cf864f9aab163d7895d
Reviewed-on: https://chromium-review.googlesource.com/1216813Reviewed-by: Emil A Eklund <eae@chromium.org>
Commit-Queue: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590095}

We're planning on adding more types of VM tests, so this flag should
come in handy in the future.

Bug: 876587
Change-Id: I0db628151ae2016b4fd891fdbd5064ee41b1720f
Reviewed-on: https://chromium-review.googlesource.com/1217073
Commit-Queue: Ben Pastene <bpastene@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590094}

This became necessary to build Chrome after [1] when building without the
sysroot.

[1] https://chromium.googlesource.com/chromium/src/+/297928530fc400a897f62fa98ccf4a5485990f22

BUG=879147
TBR=dpranke

Change-Id: Iff2d59b247cd764f404f0beeaf232cc8dc8188aa
Reviewed-on: https://chromium-review.googlesource.com/1214699Reviewed-by: Michael Moss <mmoss@chromium.org>
Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590093}

Test ChromeDriver.testTakeElementScreenshot fails on Android platforms.
Disabling test for now.

Bug: chromedriver:2579
Change-Id: I5ceb2cf4ba39cbfbeb37c851724e0b7ccd5a9925
Reviewed-on: https://chromium-review.googlesource.com/1217601Reviewed-by: John Chen <johnchen@chromium.org>
Commit-Queue: Artur Khachatryan <khachatryan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590092}

This CL moves the extension-view-manager to a shared location to be used
by other WebUIs. The immediate use case is for a new welcome page; see
linked bug for details.

Bug: 874146
Change-Id: Ieb168e61cf6ae02e04d624c92a131e9ec38fcdae
Reviewed-on: https://chromium-review.googlesource.com/1157241Reviewed-by: Hector Carmona <hcarmona@chromium.org>
Commit-Queue: Scott Chen <scottchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590091}

The root cause was that item of type ItemTypeSavedPasswords was not
being properly formatter in |-collectionView:cellForItemAtIndexPath:|

Also sets the detail text of the item at the time of creation, and not
only when the preference changes.

Bug: 882583
Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs
Change-Id: I68a3d8660e520a99ec59b3fc48fb2f78dc59b5fe
Reviewed-on: https://chromium-review.googlesource.com/1217503Reviewed-by: Peter Lee <pkl@chromium.org>
Commit-Queue: Moe Ahmadi <mahmadi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590090}

URLFetcher will stop working with advent of Network Service, and
SimpleURLLoader is the replacement API for most clients.
This CL migrates chromeos::chromeos::AttestationCAClient and the
respective unittests away from URLFetcher.

BUG=773295,879782

Change-Id: I9ccdad3a73108ad3e3e7ab4f148b93048433b3bd
Reviewed-on: https://chromium-review.googlesource.com/1202223
Commit-Queue: Antonio Gomes <tonikitoo@igalia.com>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590089}

Bug: 881144
Change-Id: Idc5292cecf9a3d4dbc101a9c44c47bd3db62dab6
Reviewed-on: https://chromium-review.googlesource.com/1208941Reviewed-by: Alexander Timin <altimin@chromium.org>
Reviewed-by: Ken Rockot <rockot@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Kai Ninomiya <kainino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590088}

Previously we prevented the login bubbles from overlapping into the shelf.
This had some annoying side effects like obscuring the password field. This
CL removes that part of the widget repositioning logic.

A future CL will address the potential case of login bubbles going off screen
on the bottom. Need to clarify the correct UX for this case.

Bug: 880224, 875787
Change-Id: Iea42cd612e9b0c57516fdc9681843182fa8d268b
Reviewed-on: https://chromium-review.googlesource.com/1217742Reviewed-by: Jacob Dufault <jdufault@chromium.org>
Commit-Queue: Quan Nguyen <qnnguyen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590087}

changes in this cl,
- Do not change the shelf's visibility if drag on the shelf that has been
  set to always shown.

- Gesture drag on the shelf should not change its auto-hide behavior. Since
  we can only change it through the context menu of shelf now.

- Fixed the failed related ShelfLayoutManagerTest*.

Bug: 880682, 881154
Change-Id: I2187c4636b1bbb5ca59149e33dbcbb8c664863b1
Reviewed-on: https://chromium-review.googlesource.com/1214049Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Min Chen <minch@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590086}

When Views are invisible by opacity 0 but still have visibility true,
screenreader would still be able to read it. We need to explicitly
set their visibility to false.

Bug: b:113731925
Test: locally build and not able to navigate to these elements with
Test: screen reader
Change-Id: Ibb1b111844dbd6021c267ef594777614cf127189
Reviewed-on: https://chromium-review.googlesource.com/1212342Reviewed-by: Muyuan Li <muyuanli@chromium.org>
Commit-Queue: Xiaohui Chen <xiaohuic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590085}

Bug: 879542
Change-Id: I3712f517ab3ee5f78eede3922335ac5e240b9816
Reviewed-on: https://chromium-review.googlesource.com/1217342Reviewed-by: Jacob Dufault <jdufault@chromium.org>
Commit-Queue: Quan Nguyen <qnnguyen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590084}

This reverts commit 9bc4c7ef.

Reason for revert: CL fixed UI jank but regressed accessibility. Will re-implement with another approach.

Original change's description:
> Fix UI jank caused by visibility change.
> 
> Previously, when animating the footer view and/or its children, we
> modified visibility so as not to receive focus/accessibility events on
> hidden views.
> 
> Unfortunately, changing the visibility of the footer view has a side
> effect of freeing up space for UiElementContainerView. When this
> happens, there is a bit of UI jank when the UiElementContainerView
> takes that available space when really that space should permanently be
> reserved for the footer. This becomes more obvious in a follow up CL in
> which we add a shadow above the footer.
> 
> Now, we don't modify view visibility. Instead, we update focus behavior
> as appropriate before animations start and after they end.
> 
> See bug for repro steps.
> 
> Bug: b:113871610
> Change-Id: Ic8aa509c722ace44675a3ab7c7e0453c0aa4a352
> Reviewed-on: https://chromium-review.googlesource.com/1197906
> Commit-Queue: David Black <dmblack@google.com>
> Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#588926}

TBR=xiaohuic@chromium.org,dmblack@google.com

# Not skipping CQ checks because original CL landed > 1 day ago.

Bug: b:113871610
Change-Id: I81f93ff5b641fab87e9b00fffc1c6c428ff44388
Reviewed-on: https://chromium-review.googlesource.com/1216812Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Commit-Queue: David Black <dmblack@google.com>
Cr-Commit-Position: refs/heads/master@{#590083}

This patch flips the flag of Continue Reading to default on.

Bug: 882602, 843839
Test: manual.
Change-Id: Idaebea1a12926d1a64482b06af3644e55fc01b4a
Reviewed-on: https://chromium-review.googlesource.com/1217593Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Tao Wu <wutao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590082}

Also embellish the PA API a bit to make accessing the new zero-fill
functionality more usable.

There are likely additional call sites that can make use of this functionality.

Bug: 864462
Change-Id: I8881c5774b6083b210f5160d4b4f2ac345f2467e
Reviewed-on: https://chromium-review.googlesource.com/1212443
Commit-Queue: Chris Palmer <palmer@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590081}

https://webrtc.googlesource.com/src.git/+log/b2d711673390..cf64a04acdf3


git log b2d711673390..cf64a04acdf3 --date=short --no-merges --format='%ad %ae %s'
2018-09-10 phoglund@webrtc.org Bump tryserver mac versions and xcode versions.
2018-09-10 mbonadei@webrtc.org Refactor initialization of GetRealTimeClock singleton.
2018-09-10 srte@webrtc.org Adds initial data window field trial to GoogCC.
2018-09-10 henrik.lundin@webrtc.org NetEq tools: Fixing an issue with measuring the simulation time
2018-09-10 aleloi@webrtc.org Added flags for the adaptive analog AGC in audioproc_f.


Created with:
  gclient setdep -r src/third_party/webrtc@cf64a04acdf3

The AutoRoll server is located here: https://autoroll.skia.org/r/webrtc-chromium-autoroll

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=luci.chromium.try:linux_chromium_archive_rel_ng;luci.chromium.try:mac_chromium_archive_rel_ng

BUG=chromium:None
TBR=webrtc-chromium-sheriffs-robots@google.com

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

This CL only handles the files in //remoting. The files in //net were
tackled in https://crrev.com/c/1188959. Parallel CLs will tackle other
directories.

net::IOBuffer is (thread-safe) ref-counted. Asides from improving the
ability to reason about instance ownership locally, creating instances
via base::MakeRefCounted makes it possible to use 1-based ref-counting
in the future (see base/memory/ref_counted.h).

This CL is mechanical, to avoid introducing any behavior changes. The
difficult cases will be tackled by follow-up CLs. The following
transformations were performed.

* new IOBufferType(args) => base::MakeRefCounted<IOBufferType>(args)
* new IOBufferType => base::MakeRefCounted<IOBufferType>()
* scoped_refptr x(base::MakeRefCounted<IOBufferType>(args)) =>
  scoped_refptr x = base::MakeRefCounted<IOBufferType>(args)
* scoped_refptr<IOBufferType>(base::MakeRefCounted<IOBufferType>(args)) =>

  base::MakeRefCounted<IOBufferType>(args)
* In comments: creates a new IOBufferType => creates an IOBufferType
  (so it wouldn't trigger future searches for "new BufferType")
* Instantiated static members in HttpResponseBodyDrainer,
  HttpNetworkTransaction, HttpProxyClientSocket, WritersTest,
  UDPSocketTest, TestDelegate, UDPSocketPerfTest
  (needed to fix linker errors)
* arraysize -> base::size (where needed to pass presubmit checks)
* git cl format

Change-Id: I4feed626ef76c0da3934748ea063ce317ce2ce86
Reviewed-on: https://chromium-review.googlesource.com/1200571Reviewed-by: Gary Kacmarcik <garykac@chromium.org>
Commit-Queue: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590079}

This makes D3D11VideoDecoder use the visible rect from the H264
decoder when constructing a VideoFrame.

Change-Id: Ic8a3095a86bb9282a6d1fcf06aed1cf6aeef60d7
Reviewed-on: https://chromium-review.googlesource.com/1217354Reviewed-by: Dan Sanders <sandersd@chromium.org>
Commit-Queue: Frank Liberato <liberato@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590078}

https://chromium.googlesource.com/catapult.git/+log/77a15654a753..03c80a36415d


git log 77a15654a753..03c80a36415d --date=short --no-merges --format='%ad %ae %s'
2018-09-10 benjhayden@chromium.org Add scalar-span for v2spa


Created with:
  gclient setdep -r src/third_party/catapult@03c80a36415d

The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll

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

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

This CL only handles the difficult cases in //remoting. The easy cases
were tackled by mechanical CLs, such as https://crrev.com/c/1188959 for
//net. Parallel CLs will tackle other difficult cases.

net::IOBuffer is (thread-safe) ref-counted. Asides from improving the
ability to reason about instance ownership locally, creating instances
via base::MakeRefCounted makes it possible to use 1-based ref-counting
in the future (see base/memory/ref_counted.h).

This CL replaces raw IOBuffer pointers with scoped_refptr<net::IOBuffer>
in some APIs. Local inspection of the impacted implementations should
reveal that no extra reference churn was introduced.

Change-Id: I59940c49e6635540a4a42840919ff114b3a1941f
Reviewed-on: https://chromium-review.googlesource.com/1215463Reviewed-by: Gary Kacmarcik <garykac@chromium.org>
Commit-Queue: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590076}