GitLab

The side-nav tabs are "full bleed" to the edge of the widget, so the
border should not have a left edge. This is most obvious in the
keyboard focus state, which has a blue ring.

Focused not selected: http://screen/3OzUMv6ur8q

Focused and selected: http://screen/8nubuJyhvUF

Bug: 967923
Change-Id: I86acf99f279c03f63e525f4a626d4cf1d393b4d4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726830
Auto-Submit: James Cook <jamescook@chromium.org>
Reviewed-by: May Lippert <maybelle@chromium.org>
Commit-Queue: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682485}

Bug: 988673
Change-Id: Ib42f894182ff78fe48f9c10eb874e3da78f60ea4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726654
Commit-Queue: Anastasia Helfinstein <anastasi@google.com>
Commit-Queue: Brian White <bcwhite@chromium.org>
Auto-Submit: Anastasia Helfinstein <anastasi@google.com>
Reviewed-by: Brian White <bcwhite@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682484}

Only affects the NetworkService code path. This implements MIME type
sniffing when the app provides a null MIME type in any of the following
cases:

 - shouldInterceptRequest() callback API
 - ContentProvider (loaded from content:// URL)
 - file:///android_{asset,res} URL (when we can't already guess the MIME
   type from the path name).

This is done to accommodate legacy apps, which relied on this internal
detail of the legacy network path.

This implementation is behind a feature flag (enabled by default) as an
extra precaution, in case it causes unexpected problems.

Bug: 985491
Test: manual - verify this fixes the GoldenDict application
Test: run_android_webview_unittests -f AndroidStreamReaderURLLoaderTest.*
Test: run_webview_instrumentation_test_apk -f AwContentsClientFullScreenTest.*
Change-Id: I4f81657206c218e4835f3d0a59ce5f5ce65932c6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1721878
Commit-Queue: Nate Fischer <ntfschr@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682483}

Bug: 979422

Change-Id: I45a0b877eb9c30fd4aa12b4c21f85e08cf58c5ea
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1724868Reviewed-by: vmpstr <vmpstr@chromium.org>
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Auto-Submit: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682482}

https://webrtc.googlesource.com/src.git/+log/425d6aaa4ce2..4ed5b087f57f


git log 425d6aaa4ce2..4ed5b087f57f --date=short --no-merges --format='%ad %ae %s'
2019-07-30 noahric@chromium.org Skip empty strings in ToUtf(8|16).
2019-07-30 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 0959b866..394c077f (682230:682353)
2019-07-30 mbonadei@webrtc.org Revert "Reporting of decoding_codec_plc events"
2019-07-30 nisse@webrtc.org Mark the audio_generator_factory target as testonly
2019-07-30 mbonadei@webrtc.org Make it possible to reuse RTCEventLog conversion functions.
2019-07-30 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 3c3851d3..0959b866 (681486:682230)
2019-07-30 titovartem@webrtc.org Update documentation on VideoConfig.simulcast_config.
2019-07-30 mbonadei@webrtc.org Disable -Wunguarded-availability for apprtc_signaling.
2019-07-29 mellem@webrtc.org Revert "Only include payload in bytes sent/received."
2019-07-29 alexnarest@google.com Reporting of decoding_codec_plc events


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

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.



TBR=webrtc-chromium-sheriffs-robots@google.com

Bug: chromium:None,chromium:None,chromium:None,chromium:None,chromium:None
Change-Id: I5ccefaa856645dd2e89bf89c62f076120b985564
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1727237Reviewed-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@{#682481}

This reverts commit f900f94d.

Reason for revert: 989059

Original change's description:
> Roll r8 1.6.11 -> 1.6.17
> 
> Change-Id: I984ce23ea9494151e309aa69d7e0a9c27111a4a8
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1721021
> Reviewed-by: Andrew Grieve <agrieve@chromium.org>
> Commit-Queue: Sam Maier <smaier@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#681786}

TBR=agrieve@chromium.org,smaier@chromium.org

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

Change-Id: I1856a88f53bb446e9b0c7533fb56f00db0e1c3c8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1727349Reviewed-by: Sam Maier <smaier@chromium.org>
Commit-Queue: Sam Maier <smaier@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682480}

Based on crbug/986046 there is a performance issue on bots,
when 3 simulators are running in parallel.
Changed a script to check how many test cases need to re-run
and if number is less(or equal to) 20, tests will re run on
1 simulator.
Also:
- added `clear all simulator` command to run before each attempt
- removed verbose logging of screenshots.

Bug: 979267,986046
Change-Id: I7ee12df6b1b5b3b46484b3e5089d16cb577cd821
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1686953
Commit-Queue: Maksym Onufriienko <monufriienko@chromium.org>
Reviewed-by: Justin Cohen <justincohen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682479}

Change-Id: Idc3c13d0437ab07098034d250d21325d95cce8ac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726951Reviewed-by: Theresa <twellington@chromium.org>
Commit-Queue: Becky Zhou <huayinz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682478}

xrWebGLLayer_framebuffer was a recently added test that both duplicated
and was at odds with parts of xrWebGLLayer_opaque_framebuffer. This
change deletes xrWebGLLayer_framebuffer and ports the new requirements
from that file that are spec compliant to the opaque_framebuffer file.

Bug: 986672
Change-Id: I0f649297f2d4f93f2d17cb396185436e7cb7c6bb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1727329
Commit-Queue: Alexander Cooper <alcooper@chromium.org>
Commit-Queue: Brandon Jones <bajones@chromium.org>
Auto-Submit: Alexander Cooper <alcooper@chromium.org>
Reviewed-by: Brandon Jones <bajones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682477}

Bug: 934009
Change-Id: I1d47193fe8ac8f19f4d96f7d53dd938b2aeb129b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726650Reviewed-by: Clark DuVall <cduvall@chromium.org>
Commit-Queue: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682476}

As discussed this CL will add a WorkingSetTrimmer policy. The default
policy as implemented in working_set_trimmer_policy is identical to the
previous behavior on Windows in which we will always trim on frozen.

The Windows implementation uses that same default behavior but uses
PlatformSupportsWorkingSetTrim to check if it's flag enabled.

The ChromeOS implementation uses the same default plus it adds working
set trim on Moderate memory pressure. There are a number of flags used
to control this behavior.

Bug: 973963
Change-Id: I2dfd4a8e7e45497725cb905bc1254beb8fda3ae3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1706450
Commit-Queue: Brian Geffon <bgeffon@chromium.org>
Reviewed-by: Marc Treib <treib@chromium.org>
Reviewed-by: Chris Hamilton <chrisha@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682475}

This allows better tracking of crashes coming from test environments.

Change-Id: Ic9bdc9bced430a420cd3c984a4b186e29f4fd9da
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726955Reviewed-by: Joe Mason <joenotcharles@google.com>
Commit-Queue: proberge <proberge@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682474}

https://skia.googlesource.com/skia.git/+log/95d8ceb955cc..6e86c1b05eee


git log 95d8ceb955cc..6e86c1b05eee --date=short --no-merges --format='%ad %ae %s'
2019-07-30 michaelludwig@google.com Remove bad SK_API tag from internal class
2019-07-30 reed@google.com move all picture version crap into single header
2019-07-30 brianosman@google.com Explicitly fetch "main" in the runtime color filter
2019-07-30 mtklein@google.com test a (the) zero-arg program
2019-07-30 jvanverth@google.com Revert "Use shared mode for Metal texture upload buffers."
2019-07-30 bsalomon@google.com Always use sized internal formats when creating GL render buffers.
2019-07-30 egdaniel@google.com Dump GrGLCaps format table in json dump.
2019-07-30 mtklein@google.com add vmovdqa(ymm,ymm)
2019-07-30 michaelludwig@google.com Hide SkImageFilter subclasses in CPP files


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

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-blink-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

TBR=benjaminwagner@google.com

Bug: None
Change-Id: I5c1d011c88ec0fb7daa72ecd3c1a5fb1cd8571e3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726973Reviewed-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@{#682473}

- android.view.View#getRootWindowInsets requires API level 23
- android.view.WindowInsets requires API level 20
- android.view.View#setOnApplyWindowInsetsListener requires API level 20

I am adding @TargetApi(Build.VERSION_CODES.O) for these places, assuming
that this file is added for Android Q and above, but our lint tool
doesn't recognize Build.VERSION_CODES higher than O...


Bug: None
Change-Id: Ib276a793706a3e1bf2231a6aa451d4b1a2ff7180
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1725212Reviewed-by: Jinsuk Kim <jinsukkim@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Commit-Queue: Shimi Zhang <ctzsm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682472}

Using wpt-import in Chromium f4402540.
With Chromium commits locally applied on WPT:
250461b3 "Worker: Register a service worker just once for worker subresource interception tests"
bf4ad57e "Experimental CookieStore API: some additional browser-side validation"


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=lpz

No-Export: true
Change-Id: I113dd7db935259751011d3b6dfd9ef53616cedec
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726794Reviewed-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@{#682471}

This patch fixes hit-testing list markers to include when the
marker content was hit.

In legacy, markers are LayoutBox with special painters, but
LayoutNG creates an anonymous box with an anonymous text or
an anonymous image, and that hit-testing may find the content
inside the marker. This patch checks parent of the object.

Bug: 988414
Change-Id: Ifff61452a791e88f45d44bc45f00ead31070df0c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726571Reviewed-by: Emil A Eklund <eae@chromium.org>
Commit-Queue: Emil A Eklund <eae@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682470}

This is CL is generated by a script. Data is pulled from
review conducted in Q2 2019. See https://tinyurl.com/yxau5sc4
for context.

Bug: 977050
Change-Id: I4b6acbe475ce6338cfc4510820a2a2703cc34416
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1700941Reviewed-by: John Budorick <jbudorick@chromium.org>
Reviewed-by: Georges Khalil <georgesak@chromium.org>
Reviewed-by: Mark Cogan <marq@chromium.org>
Commit-Queue: John Budorick <jbudorick@chromium.org>
Auto-Submit: Eric Foo <efoo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682469}

Added automated testing to text navigation manager test file. This tests the selection functions by themselves and their interaction with the navigation methods. These tests are currently disabled due to flakiness.

Test: Use --gtest_filter="*SwitchAccessTextNavigationManagerTest*" --gtest_also_run_disabled_tests to run these tests.


Bug: 982004
Change-Id: I21331d7173643a0a4c78323c7068da34b2aeb8c9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1717568Reviewed-by: Anastasia Helfinstein <anastasi@google.com>
Commit-Queue: Rose Garcia <rosalindag@google.com>
Cr-Commit-Position: refs/heads/master@{#682468}

This change the PPB_Buffer_Impl and associated buffer alloc to use
base::UnsafeSharedMemoryRegion instead of the legacy SharedMemoryHandle.
The affected IPCs are PpapiHostMsg_PPBBuffer_Create and
PpapiPluginMsg_VideoCapture_OnDeviceInfo.

Bug: 795291
Change-Id: Ia07e2d2e8c0eea43b898de6f8b33e706226c87b2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1724084Reviewed-by: Bill Budge <bbudge@chromium.org>
Commit-Queue: Matthew Cary (CET) <mattcary@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682467}

Now we have eslint 5.16.0 and babel-eslint 10.0.2 in
third_party/node/node_modules.

This CL also resolves existing eslint errors.

Bug: 976575
Change-Id: Ifea782746f2ba9ce0a27c5bd5b76d2744f0737ee
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1722270Reviewed-by: Fergal Daly <fergal@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682466}

Bug: 986926
Change-Id: I5e6c0880162a0f064fe0104d9ea4cc6a8c0c3d8a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1715667
Commit-Queue: Patrick Monette <pmonette@chromium.org>
Reviewed-by: Chris Sharp <csharp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682465}

where appropriate. GpuServiceWebView is split out of
DeferredGpuCommandService to handle binding initialization and holding
global GPU objects. Most call sites should now be using
GpuServiceWebView directly instead of going through
DeferredGpuCommandService.

Bug: 987265
Change-Id: I1eb31a9f142d32bc2a4596a077c2bb2832d87891
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1724500Reviewed-by: weiliangc <weiliangc@chromium.org>
Commit-Queue: Bo <boliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682464}

Reduce the size of pdfium_engine.cc by moving a chunk of code into
pdfium_font_linux.cc. Fix a couple of comments and make a small tweak
along the way.

Change-Id: I503ec6fbf6ebb312bcbd23c9f575ad72c95900d0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1725332Reviewed-by: Henrique Nakashima <hnakashima@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682463}

Bug: 931032
Change-Id: I2dfc5ee4e865b7ee1f71f2414ca6a317b6417067
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1716002
Commit-Queue: Jesse Doherty <jwd@chromium.org>
Auto-Submit: Glen Robertson <glenrob@chromium.org>
Reviewed-by: Jesse Doherty <jwd@chromium.org>
Reviewed-by: Alan Cutter <alancutter@chromium.org>
Reviewed-by: Jay Harris <harrisjay@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682462}

Bug: 981900
Change-Id: I67cce1c95a32bc4f09bdd3dcc9e914ac0c36f4a5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1719325
Auto-Submit: George Steel <gtsteel@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Commit-Queue: Robert Flack <flackr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682461}

This is a preliminary step to Onion souping
//content/renderer/media/video_capture.

Given that it needed its own adaptations on unrelated code, it was
decided to upload a CL of its own.

BUG=704136
R=guidou@chromium.org, haraken@chromium.org

Change-Id: I5f0465e0747296980b072a68fe6070ccb0381aa9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1718467
Commit-Queue: Antonio Gomes <tonikitoo@igalia.com>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682460}

This test should not be flaky anymore now that we're sorting tracks by
id, as required by the spec and as exposed by the test.

Therefore, remove from TestExpectations.

Bug: 983790
Test: mediastreamaudiosourcenode-routing.html
Change-Id: I76733a7b5d60757bfca066b5eab0a62c6f90babd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726275Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682459}

CrosNetworkConfigTestHelper was intended as a convenience class for
tests that require specific network configuration setup. It relies
on running the message loop to ensure complete setup before tests run.

For ShellBrowserMainParts, we just need a CorsNetworkConfig instance.
The easiest way to provide this is to initialize the fake shill clients
and NetworkHandler, then create an owned CrosNetworkConfig instance,
without the additional complexity in the test helper.

Bug: 980951
Change-Id: I4b4a72ec7258f5010e0e24750e2f37f6bd884138
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726932
Commit-Queue: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682458}

https://pdfium.googlesource.com/pdfium.git/+log/e858d1fb244d..12bc1c4dae87


git log e858d1fb244d..12bc1c4dae87 --date=short --no-merges --format='%ad %ae %s'
2019-07-30 tsepez@chromium.org Use RetainableTreeNode for LayoutItems.
2019-07-30 vmiklos@collabora.co.uk Add FPDFPageObj_GetClipPath() API


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

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

Bug: None
Change-Id: I2ecd3d39dcd0bca7bf9dd4e67e09da04cfee8a66
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1726902Reviewed-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@{#682457}

Mostly focused on some cups_util cleanups and expanded testing suite.

Also the sequencing model for the main service handler, landing in following CL,
has changed, forcing the internal managers to be both created and accessed from
a sequenced context. This change updates their sequence_checkers to reflect that.

Bug: chromium:945409
Test: updated tests pass
Change-Id: I6f9b987a56ec18d07f907035476c4e2549fe66f9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1721850Reviewed-by: Sean Kau <skau@chromium.org>
Commit-Queue: Luum Habtemariam <luum@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682456}

Removes all dependences from patch service onto Service Manager in favor
of the simplified service model and direct mojom interface acquisition.

This CL mirrors what was done for the Unzipper service, providing a
Content library in components/services/patch for launching a sandboxed
process, and an in-process helper for tests and iOS.

Bug: 977637
Change-Id: I54f3339551a374538902d94a6051f78c3778c08e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1721463Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Joshua Pawlicki <waffles@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Commit-Queue: Ken Rockot <rockot@google.com>
Cr-Commit-Position: refs/heads/master@{#682455}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/3b361d1e1281..019109290b69


git log 3b361d1e1281..019109290b69 --date=short --no-merges --format='%ad %ae %s'
2019-07-30 mmortensen@google.com Refactor service/lib to use artifacts.BundleImageZip


Created with:
  gclient setdep -r src/third_party/chromite@019109290b69

The AutoRoll server is located here: https://autoroll.skia.org/r/chromite-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:chromeos-kevin-rel

TBR=chrome-os-gardeners@google.com

Bug: None
Change-Id: I87a9059054152e0e2b86fcd71975ce61584a98be
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1727143Reviewed-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@{#682454}

Adding the buttons and messages for the Switch Access cut, copy, and paste
functionality. This includes adding the image files for the icons, added
strings and translation screenshots, and adding the buttons into the menu
manager so they appear in the menu.

Bug: 982004
Change-Id: I35e9b3b3dfe48b1730c23317115ee96be89141bd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1719292Reviewed-by: Anastasia Helfinstein <anastasi@google.com>
Commit-Queue: Rose Garcia <rosalindag@google.com>
Cr-Commit-Position: refs/heads/master@{#682453}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/cde7deb536fa..b63730a701a4


Created with:
  gclient setdep -r src-internal@b63730a701a4

The AutoRoll server is located here: https://skia-autoroll.corp.goog/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.

CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome

TBR=jbudorick@google.com

Bug: chromium:None,chromium:None
Change-Id: I2c32cf87f00ace93476ce15604192e0af99b07ed
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1727250Reviewed-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@{#682452}

We no longer validate specific attribute groupings within operations.
Instead we validate at the per-attribute level only, confirming the same
information as before, and leaving any higher-logic validating to
CUPS.

Bug: chromium:945409
Test: manually confirmed valid attribute/opcode set
Change-Id: I8c2541a8b7a1957239c2468526b75b2a77450646
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1704696Reviewed-by: Sean Kau <skau@chromium.org>
Commit-Queue: Luum Habtemariam <luum@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682451}

Avoid a namespace conflict with the CFNetwork framework.

Change-Id: If596cfb14d118fc7bc08bf2ae732c6e347ab049e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1724835
Commit-Queue: Justin Cohen <justincohen@chromium.org>
Auto-Submit: Justin Cohen <justincohen@chromium.org>
Reviewed-by: Rohit Rao <rohitrao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682450}

This metric was intended to help identify potential issues in case the render
path selection logic wasn't working as intended, for example a hypothetical
Andoid O device that's expected to support AHardwareBuffer but where this
wasn't working. So far, there haven't been reports of such issues, hence
retiring the metric.

Bug: 988691
Change-Id: I92d001fd17b2c5ef4d8a650be636ac7aecb4cb72
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1725094
Commit-Queue: Klaus Weidner <klausw@chromium.org>
Reviewed-by: Brian White <bcwhite@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682449}

The MediaDeviceListener interface is no longer exposed by the renderer
process. Long ago the approach for this interface was changed so
that no interface is explicitly exposed.

Bug: 987582
Change-Id: I429ce4b259c5a5c97c1bb08c16e0607da63acb5e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1715077Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Commit-Queue: Guido Urdaneta <guidou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682448}

ReportingScheduler now call real report generator and report uploader.

Reporting will stop if we can't generate any report or report uploading
returns a persistent error. There will be no future reports until Chrome
relaunch or pref change notification is received.

Bug: 956237
Change-Id: If19bb773ab0b29d810169c9454991e4947e4249e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1721629
Commit-Queue: Owen Min <zmin@chromium.org>
Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682447}

There are existing POSIX implementations for these methods in
stack_sampler_posix.cc. We now use stack_sampler_android.cc on Android
and stack_sampler_posix.cc on all other POSIX platforms.

Note that there's an existing StackSamplerAndroid that exists in the
tracing namespace. However, that implementation is only used for the
"cpu_profiler" tracing category, whereas this implementation will be
used for stack sampled metrics. Once this new Android profiler is
sufficiently complete, it will also be used for tracing.
This stack_sampler_android.cc defers to StackSamplerImpl for its core
logic (also used by the Windows and Mac sampling profiler
implementations), whereas tracing's stack_sampler_android doesn't use
StackSamplerImpl and implements its own core logic.

R=wittman@chromium.org,gab@chromium.org

Bug: 988574
Change-Id: Ia1f20a22ac1421ff02d4beecff4beb6b7a0e065f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1727230Reviewed-by: Gabriel Charette <gab@chromium.org>
Reviewed-by: Mike Wittman <wittman@chromium.org>
Commit-Queue: Charlie Andrews <charliea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#682446}