GitLab

These files need to be accessible when running wpt
outside chromium environment.

see: https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md#mojojs

This is the first step towards making these tests pass outside the Chromium CI

Bug: 1123989
Change-Id: I9600bc52f6c9ec2217ff09c72c6bdcc6a5af4b9f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2391255
Commit-Queue: Arnaud Mandy <arnaud.mandy@intel.com>
Reviewed-by: Finnur Thorarinsson <finnur@chromium.org>
Reviewed-by: Michael Moss <mmoss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805047}

Using wpt-import in Chromium 15f9f86c.

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

NOAUTOREVERT=true
TBR=smcgruer@google.com

No-Export: true
Change-Id: I5301391d0e0e188a7055a5ce67f8f3d481382376
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2398560Reviewed-by: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#805046}

This change forwards the correct --gtest_repeat arg on to gtest instead
of the incorrect --repeat arg when the --repeat flag is used with
run-swarmed.py.

Bug: 1124365
Change-Id: Ie2e8b1a74748f4230570721dfaef845cd1d4f022
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2391161Reviewed-by: Nico Weber <thakis@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Reviewed-by: Wei-Yin Chen (陳威尹) <wychen@chromium.org>
Commit-Queue: Cammie Smith Barnes <cammie@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805045}

This still ensures that the tabstrip is never in Stacked mode with any Tab Groups active. However, it allows Stacked mode if there are no groups created yet. Before, it would disallow Stacked mode if the feature was enabled, even if no groups were created yet.

To keep the separation between Tab Groups and Stacked mode, this change also takes the tabstrip out of Stacked mode if a group is created while in Stacked mode.

Change-Id: Ic359eaf95cf7fd2ebc2b3440a118b715640cfa45
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2399010Reviewed-by: Charlene Yan <cyan@chromium.org>
Commit-Queue: Charlene Yan <cyan@chromium.org>
Commit-Queue: Connie Wan <connily@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805044}

Also remove calls to assert sizes are the same since that is covered by asserting the models are in the right order. This will show better debug logs as well when tests fail.


Bug: 1124926
Change-Id: I739c9797e0785e077d16d6a29bc9cf17ce680ea1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2390664Reviewed-by: Kyle Milka <kmilka@chromium.org>
Commit-Queue: Sophey Dong <sophey@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805043}

This add additional EG test coverage for real-time Safe Browsing,
for scenarios identified by the test team when they were manually
testing this feature.

Bug: 1122997
Change-Id: I984babf81e251381965454679fa293426fc4c958
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2392977
Commit-Queue: Ali Juma <ajuma@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805042}

R=rockot@google.com

Bug: N/A
Change-Id: I33724debfb3416e6d5b54e5564fe8846f2103841
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2393976Reviewed-by: Ken Rockot <rockot@google.com>
Commit-Queue: Dominic Farolino <dom@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805041}

Skew tests are being added for the following versions:
1, 85.0.4183.81
2, 86.0.4240.16
3, 84.0.4147.89

TBR=estaab@chromium.org

Bug: 1041619
Change-Id: Ie5ceaa9820fa20f65002a67d903a96c88e953f24
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2398956Reviewed-by: Rakib Hasan <rmhasan@google.com>
Commit-Queue: Rakib Hasan <rmhasan@google.com>
Cr-Commit-Position: refs/heads/master@{#805040}

https://chromium.googlesource.com/external/github.com/AOMediaCodec/libavif.git/+log/f88383daa8de..616bd4f9aeca

$ git log f88383daa..616bd4f9a --date=short --no-merges --format='%ad %ae %s'
2020-09-03 wtc Remove 16bpc cases in avifLimitedToFullY(), etc.
2020-09-03 wtc Remove the avifCodecSpecificOptionsGet() function
2020-09-01 wtc Add the libaom-specific option tune=METRIC
2020-09-01 wtc Make avifCodecSpecificOptionsGet a const function

Created with:
  roll-dep src/third_party/libavif/src
R=dalecurtis@chromium.org

Change-Id: Ia50e27556d10ac03221d1c950bcaa510614e65f5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2398964Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Commit-Queue: Wan-Teh Chang <wtc@google.com>
Cr-Commit-Position: refs/heads/master@{#805039}

The test was intended for a time when we would fully support tablet mode
with multiple displays and no display mirroring. It seems that just will
not happen in the foreseeable future.

Fixed: 1125848
Change-Id: I13ee5c2a0dd3f717489e615caa083fb74b6b859c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2398974Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Commit-Queue: Avery Musbach <amusbach@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805038}

Before this CL, the child process start-up flow went like this:
 1.) Browser would create a Mojo invitation, with a mojom::ChildProcess
     receiver, that ChildThreadImpl would recover and bind.
 2.) ChildThreadImpl immediately creates a remote for its
     ChildProcessHost so it can start queueing messages for the browser
     process, even though it is not bound to the browser.
 3.) ChildThreadImpl asynchronously waits for ChildProcess::Initialize
     to be invoked by the browser process; this supplies a remote for
     mojom::ChildProcessHostBootstrap, which the child process uses to
     send the receiver for the remote created in (1).
 4.) Browser receives this, binding it to either
     RenderProcessHostImpl::io_thread_host_impl_ or ChildProcessHostImpl

In short, there's an awkward dance that has to be done between the
browser <-> renderer ((3) above), so that they can both immediately
initialize remotes for each other. This CL removes the extra IPC round
trip by removing ChildProcessHostBootstrap, and steps (3) & (4) above.
This is done by attaching a second message pipe to the mojo invitation
corresponding to the ChildProcessHost receiver, so the child process has
it immediately on init. At this point, the child process can create a
remote for the ChildProcessHost, and immediately bind it to the pipe
which is bound to the browser process's ChildProcessHost receiver.

Bug: N/A
R=haraken@chromium.org,rockot@google.com

Change-Id: I8f7b4b698b82e25d1c5c991c9639e57de05a6360
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2393158Reviewed-by: Ken Rockot <rockot@google.com>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: Martin Barbella <mbarbella@chromium.org>
Reviewed-by: Tal Pressman <talp@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Dominic Farolino <dom@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805037}

It was introduced in 724239 to inspect accessible trees by process id but this feature was removed in 1113674 as duplicate of inspect by window id feature

Bug: None
Change-Id: Ifec72d6ad2aef9238632588e8a65a77a37ca66d2
AX-Relnotes: n/a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2390852Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Commit-Queue: Alexander Surkov <asurkov@igalia.com>
Cr-Commit-Position: refs/heads/master@{#805036}

Bug: N/A
Change-Id: I5bb8e59f3a4cf8229bb389636f24243e6b98b64d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2393558Reviewed-by: Ken Rockot <rockot@google.com>
Commit-Queue: Dominic Farolino <dom@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805035}

https://crrev.com/c/2353193 added a "kDragDrop" UserAction to be used when
accessing dropped entries via the native file system API. But somehow I
forgot to actually hook this up to the D&D code.

This hooks it up by adding a UserAction parameter to CreateFileEntryFromPath
and CreateDirectoryEntryFromPath (and simplifying some bits of code a bit).

Bug: 1124833
Change-Id: Ic8b165441996c64f2849fada1787a613adeee675
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2392772Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Commit-Queue: Marijn Kruisselbrink <mek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805034}

Bug: 1084107
Change-Id: I3dc2e16a9907c8a6e84307b27dbec940f8361c43
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2398578Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Caitlin Fischer <caitlinfischer@google.com>
Cr-Commit-Position: refs/heads/master@{#805033}

TBR=govind@chromium.org

Change-Id: I94d408a0cfea9d20d19678f40970670d14f61c90
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2399006Reviewed-by: Ben Mason <benmason@chromium.org>
Reviewed-by: Krishna Govind <govind@chromium.org>
Commit-Queue: Ben Mason <benmason@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805032}

Replace gpuBenchmarking calls with testdriver calls.
Remove pointerevent_touch-adjustment-click_target from the SlowTests file.

Change-Id: Ifd7cb4d5ab44a8498d99f053c146442ed291848e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2398969Reviewed-by: Lan Wei <lanwei@chromium.org>
Commit-Queue: Liviu Tinta <liviutinta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805031}

Change-Id: I3dace6defe908221b2f0783d8bc1cca6a4a6ffd5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2391286Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Commit-Queue: Tarun Bansal <tbansal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805030}

https://android.googlesource.com/platform/external/perfetto.git/+log/6f29c57c715c..c107c7e93630

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/perfetto-trace-processor-linux-chromium
Please CC perfetto-bugs@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Tbr: perfetto-bugs@google.com
Change-Id: Iaa5ad35519b3988b316663b05c906fd448ec3791
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2398839Reviewed-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@{#805029}

Add trybot config for "Win10 Tests x64 1909". Need to test
rebaselining before promoting the win version

Bug: 990885,1125612
Change-Id: Id722ed9a8a841dabce21cd5694186a6cbe0fc281
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2397660Reviewed-by: Garrett Beaty <gbeaty@chromium.org>
Commit-Queue: Ian Struiksma <ianstruiksma@google.com>
Cr-Commit-Position: refs/heads/master@{#805028}

SkiaRenderer is strict about ensuring that the resource format passed in
to the display compositor via TransferableResource, which is used to
create the GrSurfaceProxy, matches the underlying SharedImageBacking's
format which is the GrSurfaceBackend.

In the context of DrawingBuffer this means that for low latency mode,
the ExternalCanvasResource must have the same format as the shared image
or swap chain. One problematic case is RGBA8 vs BGRA8 because the
default CanvasColorParams() used when creating the resource uses the
platform specific default for Skia, which is based on endianness, to
determine the format passed to the display compositor.

To solve this problem, this CL adds the shared image resource format to
ColorBuffer, and makes it the source of truth for all places that need
the format in DrawingBuffer. In particular, the CanvasColorParams is
constructed to match the underlying resource format instead of relying
on the defaults.

Bug: 1122638
Change-Id: I8c4e93d7f08566e695a3948505f98541d55b7216
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2391410
Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Kai Ninomiya <kainino@chromium.org>
Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805027}

We don't support non-composited backdrop-filter.
This CL allows a foreignObject with backdrop-filter to be composited
with CompositeSVG.

Not ready to support backdrop-filter for all SVG elements yet
because for now backdrop-filter requires a PaintLayer.

Bug: 1125307
Change-Id: I85a0dddab250d0695a6d91ba80ee4c64c45ee934
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2396655Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805026}

As mentioned, this CL set the default bitrate based on image size
instead of setting a fixed value.

Bug: None
Change-Id: I694f71f5fef64165ef15f4f8d07012485297e2e6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2389261
Commit-Queue: Thomas Guilbert <tguilbert@chromium.org>
Reviewed-by: Thomas Guilbert <tguilbert@chromium.org>
Reviewed-by: Eugene Zemtsov <eugene@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805025}

... previously broken by https://chromium-review.googlesource.com/c/chromium/src/+/2377666

Bug: 1008939
Change-Id: I5d01b09e757328c3a40836d2633e5e0526a3d8b1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2399118Reviewed-by: Lei Zhang <thestig@chromium.org>
Reviewed-by: Peter Kvitek <kvitekp@chromium.org>
Commit-Queue: Andrey Kosyakov <caseq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805024}

https://chromium.googlesource.com/catapult.git/+log/7f6cd0ad669b..9dd5f6257f3e

2020-09-08 pasko@chromium.org device_utils: Update permission denylist with QUERY_ALL_PACKAGES

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/catapult-autoroll
Please CC rmhasan@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:chromeos-kevin-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:1117184
Tbr: rmhasan@google.com
Change-Id: I725ac4e4afd54311503e418c1d13f9e9b4f66bab
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2398813Reviewed-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@{#805023}

Prior to crrev.com/804584, the code to select AVCaptureVideoDataOutput's
pixel format looked like it might select PIXEL_FORMAT_MJPEG (aka dmb1
aka kCMVideoCodecType_JPEG_OpenDML), but it actually would always select
PIXEL_FORMAT_YUY2 (aka yuv2 aka kCMPixelFormat_422YpCbCr8).

And it turns out that PIXEL_FORMAT_MJPEG doesn't work. So let's make
sure we don't select it.

There remains a hunch that MJPEG will be the most efficient capture
format, and we should evaluate doing the decode and conversion
ourselves.

Bug: 1124884
Change-Id: I04473b117c05ccadbdd3226badac20656d6241a3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2399238Reviewed-by: Miguel Casas <mcasas@chromium.org>
Commit-Queue: ccameron <ccameron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805022}

Prompt the user to grant storage permission when saving a screenshot.

http://screen/Avbsig9wehami4s.png

Bug: 1093368
Change-Id: I56e959def91f3ada843ef810bea8a2daebf259c3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2378584
Commit-Queue: Kyle Milka <kmilka@chromium.org>
Reviewed-by: Tanya Gupta <tgupta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805021}

https://android.googlesource.com/platform/external/perfetto.git/+log/0e8358a4dead..9d7944292456

2020-09-08 fmayer@google.com Merge "Add package name to list of example processes."
2020-09-08 fmayer@google.com Merge "Clarify that heap_profile needs ADB."
2020-09-08 treehugger-gerrit@google.com Merge "metrics: Expose available metrics in a builtin table"

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/perfetto-chromium-autoroll
Please CC perfetto-bugs@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Cq-Include-Trybots: luci.chromium.try:linux-perfetto-rel
Bug: None
Tbr: perfetto-bugs@google.com
Change-Id: I33d7e012eac1d352c9eebde7e62045792935c4fb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2399061Reviewed-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@{#805020}

Added two web tests:
1. Small legend large border: At this time, the legend is treated as
monolithic and the borders are not breaking as well. As a result, the
border goes past the fragmentation line in the first and last columns.
2. Large legend small border: Similarly, the legend goes past the
fragmentation line in the first column. The fieldset breaks when it
reaches the fragmentation line in the second column.

Deleted the update of the border block start value as it's no longer
useful to calculate new offsets in the fieldset. This change in the code
does not affect the two new web tests.

Bug: 829028
Change-Id: I1746c9da67372f4a42ab7ab8c4184460814f486d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2391217
Commit-Queue: Ana Sollano Kim <ansollan@microsoft.com>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Alison Maher <almaher@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#805019}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/c0ee2b2ab51b..76c7a195fd79

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll
Please CC chcunningham@google.com,zmin@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome
Bug: chromium:790886
Tbr: chcunningham@google.com,zmin@google.com
Change-Id: Idf71274c5c99611e122c2d3fe70f492fdfe71cc6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2398812Reviewed-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@{#805018}

Updates the expires_after attribute for 43 histograms that have
been used to generate alerts in the past 90 days and do not already have
a date later than or within 60 days of 2020-12-07.

TBR=chromium-metrics-reviews@google.com

Change-Id: Iabaf998e91898cddc494e2b0861c9d397e37672b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2399039Reviewed-by: Chrome Metrics Logs <chrome-metrics-team+robot@google.com>
Reviewed-by: Mark Pearson <mpearson@chromium.org>
Commit-Queue: Chrome Metrics Logs <chrome-metrics-team+robot@google.com>
Cr-Commit-Position: refs/heads/master@{#805017}

This change adds checks to the platform-specific implementations
of Read() and Write() to make sure that the file descriptor is
valid before. This makes the assumptions validated by later DCHECK
correct.

This cannot be done in the platform-independent layer because test
code depends on being able to call some SerialIoHandler methods
without an actual file descriptor.

Bug: 1121836
Change-Id: If182404cf10a2f3b445b9c80b75fed5df6b5ab4b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2393001Reviewed-by: James Hollyer <jameshollyer@chromium.org>
Commit-Queue: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805016}

BUG=1116137
TEST=Manual

Change-Id: Ifdf59fb05064b8902a3d8562f8523c2b186c6b4c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2393014
Commit-Queue: Ahmed Fakhry <afakhry@chromium.org>
Reviewed-by: Alex Newcomer <newcomer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805015}

Bug: 1125186
Change-Id: Ia64dae63a0cd53003187597aaf59a3e64c94fba8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2398951Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Commit-Queue: Aaron Leventhal <aleventhal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805014}

https://chromium-review.googlesource.com/c/chromium/src/+/2392995
removed URLRequestJobManager, its only remaining consumer.

BUG: 354158
Change-Id: Iaed0be3b2f2b05957b68045bb0e623a3c1abeba7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2392996
Commit-Queue: Matt Menke <mmenke@chromium.org>
Reviewed-by: Eric Roman <eroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805013}

This is a follow up to crrev.com/c/2376723 which adds various memory
usage metrics.

According to Apple, apps get terminated by the OS if memory usage in
background goes above 50 MBs.

This CL adds a new metric to track memory usage when app got
backgrounded to learn more about memory usage patterns.

Bug: 1122181
Change-Id: If3a5f4ebb4dcc172607b2126e84b75e018d3ac1d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2387080Reviewed-by: Brian White <bcwhite@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Erik Chen <erikchen@chromium.org>
Reviewed-by: Mark Cogan <marq@chromium.org>
Commit-Queue: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805012}

This CL changes a local variable in animation.cc to use
base::Optional<double> so that it removes a usage of
blink::NullValue.

Bug: 791086
Change-Id: Ie82180b853efefb5e0f409c8c17d855c69bd9c59
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2393072Reviewed-by: Kevin Ellis <kevers@chromium.org>
Commit-Queue: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805011}

PhoneHub will be utilizing BleScanner to understand when a device is
in proximity before attempting a connection via Nearby Connections.
Thus, the BleScanner class must support multiple observers (one for the
existing use case used by Instant Tethering and Smart Lock), and one for
the Phone Hub case).

BleScanner previously had a Delegate pattern which allowed only one
listener for when BLE scans were picked up, so this CL converts this
code to an Observer pattern which supports the new use case.

For now, BleConnectionManagerImpl is still the only observer; a future
CL will add an additional one.

Bug: 1106937
Change-Id: I0dd3cea3d0f050d8caeb82784ed6193821ff657d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2393258
Auto-Submit: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: James Vecore <vecore@google.com>
Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805010}

Replaced with use of setters everywhere in the codebase and removed.
A followup CL will remove overrides of GetWindowIcon, then have
ShouldShowWindowIcon be implied by whether a non-null icon is set and
remove calls to SetShowIcon.

Bug: 1075649
Change-Id: I39a905bb0a06b591fd35413359f31fccdceeeaf0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2392937
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Reviewed-by: Peter Boström <pbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805009}

The AutoplayMutedNotificationTest#testUnmutedPlaybackTakesAudioFocus is
flaky on Marshmallow, disable the test.

Bug: 1122185
TBR: mlamouri@chromium.org
Change-Id: I171e567262296c221c1521d1154b1d87448a3fd4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2399003Reviewed-by: Owen Min <zmin@chromium.org>
Commit-Queue: Owen Min <zmin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#805008}