GitLab

This adds the Material icons we intend to use if
the categories are not yet available - mostly if
the user is offline during the First Run experience,
or if the sqlite DB got corrupted for some reason.

Bug: 888176
Change-Id: I2dcc31ae2b5afbe55561a389296239ba4c566a1c
Reviewed-on: https://chromium-review.googlesource.com/1244737
Commit-Queue: Justin DeWitt <dewittj@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Reviewed-by: Cathy Li <chili@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594421}

This migrates ReadingListDownloadService from NetworkChangeNotifier to
NetworkConnectionTracker, which works with the network service enabled.

Bug: 887057
Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs;luci.chromium.try:linux_mojo
Change-Id: Ic86d3bca9b77a53f97e9039fa35369a8fa9968b1
Reviewed-on: https://chromium-review.googlesource.com/1239339Reviewed-by: Eric Noyau <noyau@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Commit-Queue: Robbie McElrath <rmcelrath@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594420}

Reland of CL https://chromium-review.googlesource.com/c/chromium/src/+/1241842.
(Confirmed that the code builds on Cast builders, and manually examined
all references to targets under //third_party/fuchsia-sdk to verify
that all FIDL targets have been modified to reference the new sdk/
subdir.)

This script uses the metadata JSON files in the SDK to generate a
BUILD.gn in //third_party/fuchsia-sdk/sdk. The build file is
regenerated whenever a new SDK is downloaded using "gclient sync".

Only FIDL libraries are migrated for now. Additional metadata types can
be migrated in followup CLs.

TBR=scottmg@chromium.org
TBR=sky@chromium.org

Bug: 888753
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: I7ec714982cdfbb6f6ccd8fad3cd7cbb48af4eb1c
Reviewed-on: https://chromium-review.googlesource.com/1246681
Commit-Queue: Kevin Marshall <kmarshall@chromium.org>
Reviewed-by: Kevin Marshall <kmarshall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594419}

This will allow other Observables and potentially others to use
Sequencer. Added tests.

Improved the efficiency of Sequencer. The old version used
recursion heavily, which meant that the stack could grow
arbitrarily large. The new version flattens the stack and
avoids wrapping Runnables in other Runnables, saving both
stack and heap space.

Bug: None
Test: cast_base_junit_tests
Change-Id: I401a6fac6f2029e7d2744a459e03c64dd7a311ee
Reviewed-on: https://chromium-review.googlesource.com/1187633Reviewed-by: Simeon Anfinrud <sanfin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594418}

This aligns us more closely with how TalkBack treats clickables. Note that at the moment, only ARC++ sets the |clickable| property.

Bug: b:111083342
Change-Id: Ida5383ee34ae30b8d01a556c48044096a909eac4
Reviewed-on: https://chromium-review.googlesource.com/1243670
Commit-Queue: David Tseng <dtseng@chromium.org>
Reviewed-by: Yuki Awano <yawano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594417}

Change-Id: Ib0054cbbfd7eb07c59e27e32d9dbd3d2b636c277
Reviewed-on: https://chromium-review.googlesource.com/1244242Reviewed-by: Donn Denman <donnd@chromium.org>
Commit-Queue: Donn Denman <donnd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594416}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/ba614d6f..2012676a

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,v8-waterfall-sheriff@grotations.appspotmail.com

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

Contacts app is currently filtered out on the container side, which
makes it completely inaccessible to Chrome. However, Contacts
can still show up in system UI (when searching for app shortcuts,
in Shelf when launched through Play Store or an intent).

Bug: b:116356923
Test: set enable-app-shortcut-search, enter "cont" in the search box,
  observe that "Add contact" shortcut is badged with the Contacts icon
  and opens Contacts when clicked.

Change-Id: Id0a108cd08024fd92b779c953c211cafb4445130
Reviewed-on: https://chromium-review.googlesource.com/1246287Reviewed-by: Yury Khmel <khmel@chromium.org>
Commit-Queue: Vladislav Kaznacheev <kaznacheev@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594414}

This CL adds a remote-shell event to plumb more display information,
namely the size in pixels and the EDID blob.

Bug: b:77972358
Bug: b:112480270
Test: Print size and EDID in HWC.
Change-Id: Ie254184033ae9426300962c474c1e40b40fad6c8
Reviewed-on: https://chromium-review.googlesource.com/1238564Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Commit-Queue: Dominik Laskowski <domlaskowski@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594413}

Make them available to other unit tests.

This time, add build dependencies for the "pdf_test_utils" source_set.

Change-Id: I75a1665c61e77032f218686f272e3788cb059474
Reviewed-on: https://chromium-review.googlesource.com/1246682Reviewed-by: Henrique Nakashima <hnakashima@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594412}

The default implementation supports the GL tests to run on MSan successfully.

Bug: 889186
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:linux_vr;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Change-Id: I6d0f7bef6ddba8a2b508d1fd0c732dac1fb31205
Reviewed-on: https://chromium-review.googlesource.com/1246292Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Commit-Queue: Aldo Culquicondor <acondor@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594411}

https://skia.googlesource.com/skia.git/+log/90b47106a6e1..03a36fd1b06d


git log 90b47106a6e1..03a36fd1b06d --date=short --no-merges --format='%ad %ae %s'
2018-09-26 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/swiftshader d73b871379e0..96a1ceb171cf (1 commits)
2018-09-26 stephana@google.com [infra] Upgrade Go to 1.11
2018-09-26 robertphillips@google.com Work around MSVC issue on older tool chains
2018-09-26 fmalita@chromium.org [skottie] Add a property setter sample/GM
2018-09-26 allanmac@google.com Updates for Vulkan AMD GCN


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

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=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
TBR=bsalomon@chromium.org

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

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/4977a156c2fc..9a53f1444701


Created with:
  gclient setdep -r src-internal@9a53f1444701

The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-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=mmoss@chromium.org

Change-Id: Ia2ad4c4c0705671dbe131256d1f62e221b4e7a92
Reviewed-on: https://chromium-review.googlesource.com/1246229Reviewed-by: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#594409}

Bug: 846473
Change-Id: I46923a902045b531578439e73068c0fd93c66691
Reviewed-on: https://chromium-review.googlesource.com/1240301Reviewed-by: Matt Menke <mmenke@chromium.org>
Commit-Queue: Edward Jung <edwardjung@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594408}

Changes in this CL:
- Remove have_seen_accelerometer_data_ variable. As this variable is not
  set if the device doesn't have kAshEnableTabletMode flag.
- Only observe the display/lid/input device events if the ui mode is
  allowed to be changed.

No functionality is changed in this CL.

Bug: 887042
Change-Id: Ic42d4cc0c25667e7aa67efcf26f65032082db126
Reviewed-on: https://chromium-review.googlesource.com/1244289Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Xiaoqian Dai <xdai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594407}

This reverts commit 2b62fe72.

Reason for revert: The change did not fix any crashes.

Original change's description:
> gpu: Expand oopr workaround to fallback to ES2 to all android versions.
> 
> Temporarily make sure we always fallback to using ES2 for all android
> versions to understand whether a particular crash spike associated with
> the oopr experiment is a result of oopr enabling ES3 for skia.
> 
> R=​ericrk@chromium.org
> 
> Bug: 884659
> 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: If5668a65d967294d07687f8d09a114153aa0d09f
> Reviewed-on: https://chromium-review.googlesource.com/1232198
> Reviewed-by: Eric Karl <ericrk@chromium.org>
> Commit-Queue: Khushal <khushalsagar@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#592248}

TBR=khushalsagar@chromium.org,ericrk@chromium.org

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

Bug: 884659
Change-Id: Ibf107c8e5c9bd42273393c8c8389f1cbd431d0fb
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
Reviewed-on: https://chromium-review.googlesource.com/1246298Reviewed-by: Khushal <khushalsagar@chromium.org>
Commit-Queue: Khushal <khushalsagar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594406}

This patch converts a bool that indicates that we must do a subtree
update of paint properties to a bitmask of reasons.

The intent is to be able to clear some of the reasons when doing a
prepaint walk, avoid some unnecessary work.

R=chrishtr@chromium.org, pdr@chromium.org, wangxianzhu@chromium.org

Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I32f1c905ba5648b34d9e544a7291817dc8b02ae7
Reviewed-on: https://chromium-review.googlesource.com/1244336
Commit-Queue: vmpstr <vmpstr@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594405}

This change adds support for pre-recorded address and payment in
Autofill Capture Site Tests. A recent change,
5e3e7faf, allows the Action Recorder
Extension to record a user's saved address and payment information when
recording a test recipe. This change completes the cycle by allowing the
automation test framework to set up the saved address and payment
information contained in a test recipe.

Bug: 847905
Change-Id: I6a5b9cc246dc59cbab4e4e0c6362c148e1820a14
Reviewed-on: https://chromium-review.googlesource.com/1241756Reviewed-by: Sebastien Seguin-Gagnon <sebsg@chromium.org>
Commit-Queue: Yiming Zhou <uwyiming@google.com>
Cr-Commit-Position: refs/heads/master@{#594404}

content setting out of the decision on whether we can start Background
Fetch.

For details, see this doc:
https://docs.google.com/document/d/1rPYSlbzScw_6PLUJ3m96ZLIkxXVAWyBSL75-VDJEMso/edit?usp=sharing

Bug: 886896
Change-Id: Ie6ba2ad6b906ab136eb65b846e67d34bad41e7e6
Reviewed-on: https://chromium-review.googlesource.com/1245799
Commit-Queue: Mugdha Lakhani <nator@chromium.org>
Reviewed-by: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594403}

Change-Id: I786ced74864fa3a26f9ebebc2d481c0a3ddc0871
Reviewed-on: https://chromium-review.googlesource.com/1244439Reviewed-by: Donn Denman <donnd@chromium.org>
Commit-Queue: Marcin Wiącek <marcin@mwiacek.com>
Cr-Commit-Position: refs/heads/master@{#594402}

https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools.git/+log/903514f95445..b07993ebf420


git log 903514f95445..b07993ebf420 --date=short --no-merges --format='%ad %ae %s'
2018-09-26 dj2@everburning.com Remove SetContextMessageConsumer from markv_codec_test (#1926)
2018-09-26 dj2@everburning.com Remove stats use of internal API (#1924)
2018-09-26 stevenperron@google.com Allow 0 as argument to scalar replacement. (#1917)


Created with:
  gclient setdep -r src/third_party/SPIRV-Tools/src@b07993ebf420

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

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

As explained in https://crbug.com/889301#c5, the test failure in
single_process_mash_content_browsertests on linux-chromeos-rel is
already expected and covered by an entry in
//testing/buildbot/filters/chromeos.single_process_mash.content_browsertests.filter:
    -SitePerProcessBrowserTest.*

Therefore, there is no point in additionally disabling the test via
//content/browser/site_per_process_browsertest.cc

Bug: 889301
Change-Id: Id86d39792939c06b2972443ea8caecad774ee6e1
Reviewed-on: https://chromium-review.googlesource.com/1246285Reviewed-by: Antoine Labour <piman@chromium.org>
Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594400}

This reverts commit d572ce1d.

Reason for revert: Caused regression crbug.com/889435

Original change's description:
> [css-flex] Update to newer spec about definite flex item sizes
>
> Implements this change:
> https://github.com/w3c/csswg-drafts/commit/5b5db39d21f3658ae2f4d7992daaf822aca178d8
>
> external/wpt/css/css-flexbox/percentage-heights-003.html ostensibly tests
> this, but I don't think the test is correct (and we don't pass it)
>
> TESTED=css3/flexbox/definite-main-size.html
>
> Bug: 784059
> Change-Id: I8ee0ee797b54a8166849ab6e9b9f019b9e43760b
> Reviewed-on: https://chromium-review.googlesource.com/1240871
> Commit-Queue: Christian Biesinger <cbiesinger@chromium.org>
> Commit-Queue: Emil A Eklund <eae@chromium.org>
> Reviewed-by: Emil A Eklund <eae@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#593707}

TBR=cbiesinger@chromium.org,dgrogan@chromium.org,eae@chromium.org

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

Bug: 784059,889435
Change-Id: Ia74fb5cf500aebcb876672497cce5295b0959b43
Reviewed-on: https://chromium-review.googlesource.com/1246291
Commit-Queue: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594399}

Bug: 862689
Change-Id: If9713d4a079965047df35a8f5a4e93adf7e390bf
Reviewed-on: https://chromium-review.googlesource.com/1246299Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594398}

https://chromium.googlesource.com/catapult.git/+log/8498332d304e..3cf15a9b47a0


git log 8498332d304e..3cf15a9b47a0 --date=short --no-merges --format='%ad %ae %s'
2018-09-26 benjhayden@chromium.org Fix links in tracing/docs/


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

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: I9c56697c0f15c753c72ee9b24fe760effc873a8d
Reviewed-on: https://chromium-review.googlesource.com/1246226Reviewed-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@{#594397}

Focus would move from the bubble dialog to lock contents view, which would then
try to focus the auth user, which was a stale pointer that had been deleted.

Bug: 884402
Change-Id: I72d729642f819d4ab2aa23c1e71edc6e851ae5ff
Reviewed-on: https://chromium-review.googlesource.com/1239512
Commit-Queue: Jacob Dufault <jdufault@chromium.org>
Reviewed-by: Wenzhao (Colin) Zang <wzang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594396}

This patch fixes:
1. ::first-line style is not applied when there are other
   anonymous inline boxes.
2. Inspector getPlatformFonts protocol collects fonts from
   two levels deep. Changed the logic not to include
   anonymous boxes to the depth limit.

Also the incorrect expectation was fixed; legacy counts
glyphs in ::first-letter twice.

Bug: 636993, 714962
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
Change-Id: Ia028710b728e8e9172b540a46b42d804c9f57699
Reviewed-on: https://chromium-review.googlesource.com/1245078Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Commit-Queue: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594395}

This defines basic build targets for a Trichrome build using the
upstream package names/configuration. The shared library APK contains
the 32-bit version of libmonochrome.so and a few autogenerated Java
pieces only at this stage, which means the total size of the three APKs
is significantly larger than Monochrome at present.

Bug: 887078
Change-Id: I3fcdfd6d7f717665a15c05dbb53602deda526b73
Reviewed-on: https://chromium-review.googlesource.com/1135546Reviewed-by: Ted Choc <tedchoc@chromium.org>
Reviewed-by: Tobias Sargeant <tobiasjs@chromium.org>
Reviewed-by: Tibor Goldschwendt <tiborg@chromium.org>
Reviewed-by: agrieve <agrieve@chromium.org>
Commit-Queue: Richard Coles <torne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594394}

DecryptingDemuxerStream had no traces and the DecyrptingVideoDecoder
had some old-style, incomplete traces. This adds traces to the
former and expands the latter. Specifically we now have:
- DecryptingDemuxerStream::DecryptPendingBuffer [async]
- DecryptingDemuxerStream::WaitingForDecryptionKey [async]
- DecryptingVideoDecoder::DecodePendingBuffer [async]
- DecryptingVideoDecoder::WaitingForDecryptionKey [async]

The DVD traces used to use a trace_id and provide a buffer size,
but this isn't really necessary since the start trace is tagged
correctly just by using |this| and providing the timestamp.

BUG=879970
TEST=passes cq

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: If21288e6c47414ec038f034bba381fcebf5ca99b
Reviewed-on: https://chromium-review.googlesource.com/1244164Reviewed-by: Xiaohan Wang <xhwang@chromium.org>
Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594393}

The generated serial is stored in SharedPreferences in order to keep it
consistent between reboots.

Bug: internal b/111077464
Test: look at logs
Change-Id: If988936bedd4fe9a9946ef2671a747dfc622ecf7
Reviewed-on: https://chromium-review.googlesource.com/1237524
Commit-Queue: Thoren Paulson <thoren@chromium.org>
Reviewed-by: Simeon Anfinrud <sanfin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594392}

Implementing a cached_image_fetcher to interact with the existing
cache/network classes.

Bug: 882970
Change-Id: Ibf95b561a069b94785c5a10a66b39399af8acf68
Reviewed-on: https://chromium-review.googlesource.com/1239251Reviewed-by: Dominic Battré <battre@chromium.org>
Reviewed-by: Mathieu Perreault <mathp@chromium.org>
Reviewed-by: Sky Malice <skym@chromium.org>
Reviewed-by: Filip Gorski <fgorski@chromium.org>
Commit-Queue: Brandon Wylie <wylieb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594391}

Change-Id: I03c0eeb61bd02f3c095a72b455de2d7ad3262569
Reviewed-on: https://chromium-review.googlesource.com/1246150Reviewed-by: Ehsan Karamad <ekaramad@chromium.org>
Commit-Queue: Ian Clelland <iclelland@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594390}

This reverts commit 239e5b82.

> The old sizes.py perf test used to check for a whole set of performance
> regressions. This is now handled elsewhere with the exception of the SI
> check. The SI check is fairly simple, however, and doesn't require all
> of the the perf_expectations infrastructure which is now obsolete.
>
> This CL removes the obsolete perf_expectations, hard codes the expected
> number of SIs in the script, and removes the windows and android code
> as it doesn't actually do anything.
>
> Bug: 572393

CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_chromium_archive_rel_ng;luci.chromium.try:mac_chromium_archive_rel_ng;luci.chromium.try:win_archive;luci.chromium.try:win_x64_archive;master.tryserver.chromium.android:android_archive_rel_ng
TBR=dpranke

Bug: 572393
Change-Id: Iad25e02aba593632f167bb534be95ba6a5691446
Reviewed-on: https://chromium-review.googlesource.com/1241935Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594389}

This allows users of Observable.not() to avoid importing
org.chromium.chromecast.base.Unit, while communicating the same
intent that there is nothing special about the data.

This is also in anticipation of rewriting how not() works if
Observables that can have multiple activations at once are made.
For such Observables, a fold() or reduce() operator would be a
natural way to implement not(), and forcing the type signature
of the result of reduce() to agree with not() is an unnecessary
constraint, when all that matters for not() is the lifetime of
the activation, not the data type.

Bug: None
Test: cast_base_junit_tests, cast_shell_junit_tests
Change-Id: I89f6f40695f443d9c946abaad4d00a9faa463046
Reviewed-on: https://chromium-review.googlesource.com/1241849Reviewed-by: Luke Halliwell <halliwell@chromium.org>
Commit-Queue: Simeon Anfinrud <sanfin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594388}

Some apps declare a permission-guarded yet exported="true" Activity.
Starting an intent to such an Activity will triggers a
SecurityException. Instead of crashing, we should just ignore these
intents.

Chrome already handles this case, so this CL changes WebView shell and
the default WebViewClient to behave similarly.

This change will have no impact for apps which set their own
WebViewClient, which should represent the vast majority of apps.

R=torne@chromium.org

Bug: 889300
Test: Manual - built a test app as described in http://b/115868439.
Change-Id: Ia9ff8113d4796033661366c06e186d7bb6eb288d
Reviewed-on: https://chromium-review.googlesource.com/1244547Reviewed-by: Richard Coles <torne@chromium.org>
Commit-Queue: Nate Fischer <ntfschr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594387}

Add finch config param for cronet and Chrome to retry QUIC connection on the alternate network before handshake.

The feature will be controlled by "retry_on_alternate_network_before_handshake".

Bug: 790547
Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;master.tryserver.chromium.android:android_cronet_tester
Change-Id: I5812083fe317f996313adce49f9bbd1d14b22f37
Reviewed-on: https://chromium-review.googlesource.com/1242038Reviewed-by: Misha Efimov <mef@chromium.org>
Reviewed-by: Ryan Hamilton <rch@chromium.org>
Commit-Queue: Misha Efimov <mef@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594386}

* Implement support for Event::LOAD_COMPLETE, firing AtkDocument load-
  complete and AtkObject state-change events.
* Create Event::LOAD_START, and fire AtkObject state-change events.
* Try to filter out load changes we don't want to fire an event for, e.g.
  pages which lack size. This saves each AT from having to filter these
  (presumed) irrelevant events out.

TBR=slan@chromium.org

Bug: 866331, 866333
Cq-Include-Trybots: luci.chromium.try:closure_compilation
Change-Id: I2f97563b5c2160793a09588481bd2bacf0f0eae1
Reviewed-on: https://chromium-review.googlesource.com/1234228
Commit-Queue: Joanmarie Diggs <joanmarie.diggs@gmail.com>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594385}

Checks experiment_name field on Optimization defined at PageHint
level and only whitelists if that experiment name is enabled for
the client.

Bug: 888666
Change-Id: I42425aaf9403a023d684c94ce94860cba27513f2
Reviewed-on: https://chromium-review.googlesource.com/1241214Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Commit-Queue: Doug Arnett <dougarnett@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594384}

By default, webkit_layout_test failurse are retried 3 times. But when
'--test-list' is passed, the retry count defaults to 0. To simplify the logic,
this CL makes it so that webkit_layout_test failures are always retried 3 times.

Bug: 888734
Change-Id: I46d15d71c979e5f12f334f5dcff41637f3f3aef4
Reviewed-on: https://chromium-review.googlesource.com/1244018
Commit-Queue: Erik Chen <erikchen@chromium.org>
Reviewed-by: Stephen Martinis <martiniss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594383}

Despite the fact that the docked magnifier feature is enabled
by default, some users may explicitly disable it, which will
cause crashes if the docked magnifier controller is accessed
without checking that it exists.

BUG=880428

Change-Id: I551edf47184e7c2fa79c4ebf72843758e5ef948c
Reviewed-on: https://chromium-review.googlesource.com/1245731
Commit-Queue: Ahmed Fakhry <afakhry@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594382}