GitLab

There are already some backdrop-filter-*.html, this CL picks the ones
that don't exist in wpt, and put them there.

Bug: 900581
Change-Id: Ie6cf7454fed6d3e89f31e69cbad93fdaa7bf3f55
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1760889
Commit-Queue: Xida Chen <xidachen@chromium.org>
Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688652}

Move Icon fetching logic to its own file, and re-use the Manifest Icon
selection logic to choose the best icon based on known parameters.

Bug: 973844
Change-Id: I041f8d66eda86f71be8f2201598c761cb0beb0d2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1751793
Commit-Queue: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: Richard Knoll <knollr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688651}

This check was made obsolete by crrev.com/c/1425726, but not removed
at that point. As a result, no further work is done on devices without
batteries.

Bug: 995808
Change-Id: I4a927b8f45723dccdfee198c789bed13003a0e12
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1762240Reviewed-by: Sergey Poromov <poromov@chromium.org>
Commit-Queue: Denis Kuznetsov <antrim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688650}

Bug: 924194
Change-Id: I680852165b6586dba03bd803cdc6f3d6ccd7bf34
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585142
Commit-Queue: Yun Liu <yliuyliu@google.com>
Reviewed-by: Tibor Goldschwendt <tiborg@chromium.org>
Reviewed-by: Theresa  <twellington@chromium.org>
Reviewed-by: Andrew Luo <aluo@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688649}

https://skia.googlesource.com/skia.git/+log/b081bc4a3139..bbfec9db84cf

git log b081bc4a3139..bbfec9db84cf --date=short --no-merges --format='%ad %ae %s'
2019-08-20 egdaniel@google.com Move transferFrom commands from GrOp and into GrRenderTask.
2019-08-20 halcanary@google.com SkQP: split make_apk script into create_apk and make_apk
2019-08-20 brianosman@google.com Reland "Remove old version of MakeCrossContextFromPixmap"
2019-08-20 halcanary@google.com SkBitmap: simplify setPixels()
2019-08-20 bsalomon@google.com GrRectBlurEffect: approximate piecewise cubic with quintic.

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

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=egdaniel@google.com

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

- updated patches since none applied cleanly
- deleted 0007-uninline_googleonce.patch, 0012-fixes-for-js-embed-cc.patch,
  0020-Add-support-for-libc-on-Windows.patch files since they were deleted from
  README.chromium by previous updater
- Removed 0022-proto_writer_render_bytes_override.patch (already upstreamed)
- Removed 0024-add_wire_format_lite_inl_include.patch (file being patched no
  longer in repo).
- Removed 0025-once-only.patch since comment in README.chromium mentions it is
  no longer needed.
- Added new patch 0026-json_objectwriter_override.patch
- Fixed gen_extra_chromium_files (jsembed no longer part of protobuf repo).
- Adds 4 new patches 0026-0029

TBR=trivial changes due to addition of new files


Bug: 988512
Change-Id: I07d9765d6a1a600b76d967d3cd8780170483b1dd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1752163
Commit-Queue: Mohamed Heikal <mheikal@chromium.org>
Reviewed-by: Albert J. Wong <ajwong@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688647}

If an extension has enabled displaying matched action count as its badge
text and the badge text for a tab is not being overridden with one set
by setBadgeText, then calling getBadgeText should return a placeholder
value.

Bug: 990224
Change-Id: Ic79d1fb8d666520062d1aa8de5f0c0a4b80305fc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1756719Reviewed-by: Karan Bhatia <karandeepb@chromium.org>
Commit-Queue: Kelvin Jiang <kelvinjiang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688646}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/7a6df9bfe5fd..26cade66d004


Created with:
  gclient setdep -r src-internal@26cade66d004

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
Change-Id: I5dbc633e697b5e73b6874d11e624b7709263fec2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1760119Reviewed-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@{#688645}

The stamp will be the only output declared by this script, since the
output directory is large and variable. But the modification time of the
stamp file should match the modification time of the metadata directory,
which is what the build system needs to determine whether the action
needs to be re-run.

I tested by running `$ autoninja -C out/Default third_party/blink/tools:build_wpt_metadata`
twice in a row. The first time ran the script, second time said "no work to do".

Bug: 995112
Change-Id: Id74e6e623807be604e85dd69ab95883a6ce275fc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1762590Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Luke Z <lpz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688644}

This adds the first of our new search providers for the files
ranking project, which provides zero-state local files suggestions
to the CrOS launcher. The design doc can be found here:

go/cros-zero-state-files-ranker

A quick overview:

 - The ZeroStateFileProvider is a new search provider that tracks
   recently-used files to display in zero state.

 - It does this by feeding notifictions from the FileTasksObserver
   into a RecurrenceRanker (Dolphin) model.

 - It's unrelated to the LauncherSearchProvider, which provides file
   results for search queries. The LSP only provides results given a
   query, and the ZSFP only provides results without one, so these
   are mutually exclusive. Note this has been implemented separately
   from the LSP so as not to further tie the launcher to the Files
   app API and javascript.

This CL has some TODOs related to parallel CLs: the search result
icon needs to be set, DriveFS results need to be filtered out, and
UMA metrics added.

The use of the new provider is gated behind a disabled-by-default
feature flag. We'll enable this once the rest of the files ranking
code has been merged.

Bug: 959679
Change-Id: I7b9697906cf13793e34fc79097b379cbe8becb48
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1755623Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Jia Meng <jiameng@chromium.org>
Commit-Queue: Tony Yeoman <tby@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688643}

Change-Id: I0603dbbfabdad0882ad81b5f5dc897ccd10c3d2c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1757208Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Commit-Queue: Pavel Feldman <pfeldman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688642}

Increase axis deadzone for all WebXR thumbsticks from 0.1 to 0.15.

Remove deadzone for WebXR touchpads. Untouched WebXR touchpads always
have their values set to 0.0, so a deadzone should not be necessary for
them.

Bug: 990840
Change-Id: I7cd799c7b52ddbdfffb927fb2b2b93b129f31c40
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1761250
Commit-Queue: Jacob DeWitt <jacde@chromium.org>
Reviewed-by: Alexander Cooper <alcooper@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688641}

This ensures that content::ConnectToFontService() always posts binding
operations to the same SequencedTaskRunner rather than using an
arbitrary runner per call.

Bug: 995144
Change-Id: Ic6f3947f056f028cb2febec875dd26eb8b870e82
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1761555Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Commit-Queue: Ken Rockot <rockot@google.com>
Cr-Commit-Position: refs/heads/master@{#688640}

TBR=mkwst@chromium.org

Bug: 973844
Change-Id: I0d588a35947afb59bf5473c948645fe267e6b676
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1748948
Commit-Queue: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Richard Knoll <knollr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688639}

Change-Id: I1f47ae01c8bcde3693373538e050e8de4c3fcb4e
Bug: 985879
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1747379
Commit-Queue: Mei Liang <meiliang@chromium.org>
Reviewed-by: Wei-Yin Chen (陳威尹) <wychen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688638}

"Apple optimized" PNG-formatted images contain a "CgBI" chunk as the
first in the file. PNGImageReader::ParseSize() did not fail on critical
chunks that it didn't recognize, so we managed to thus parse out the
dimensions of the image and ended dispatching 'load' for it (rather than
'error').

Bug: 994740
Change-Id: I6b9ddb4290cf43e3ca2f491aa1b500dedeb0316b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1760918Reviewed-by: Leon Scroggins <scroggo@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#688637}

These histograms are useful for long-standing low-prio investigations /
improvements in some legacy sync data types. I hope we can delete them
in a year from now.

Bug: 986502
Change-Id: Icb54d69f2c3640db056d8144aaec2de2ec6c274a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1762222
Commit-Queue: Jan Krcal <jkrcal@chromium.org>
Commit-Queue: Mark Pearson <mpearson@chromium.org>
Auto-Submit: Jan Krcal <jkrcal@chromium.org>
Reviewed-by: Mark Pearson <mpearson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688636}

* This change makes dialog show/hide a two-phase animation. For showing
  dialog, card zooms out and fades out first and then dialog zooms out
  and fades in; vice versa for hiding dialog.
* Add DummyUiActivity tests for the animation to make sure the animated
  views behave correctly during animation.

Bug: 977717
Change-Id: Ic62cb1e6abd45e22909d35cb0eb915f5ef4c416b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1710724
Commit-Queue: Yue Zhang <yuezhanggg@chromium.org>
Reviewed-by: Wei-Yin Chen (陳威尹) <wychen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688635}

This change restores functionality of announcing cursor position via
accessibility to users required audible cues, that use gestures to work with
omnibox contents.

The functionality is restored by using explicitly a single source of
accessibility event announcemets for TEXT_CHANGED and
TEXT_SELECTION_CHANGED. This helps us avoid sending multiple repeated
accessibility events to AccessibilityManager, which in turn appears to
be dropping them. These repeated events are originating from both
SpannableAutocompleteEditTextModel and EditText itself, which makes it
difficult to provide consistent and predictable behavior.

This change replaces the above behavior, and introduces a single source of
accessibility events instead: SpannableAutocompleteEditTextModel.

Bug: 935785
Change-Id: I7358d268cc7f21e5a7ed28d9adc26f8e0adf31fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1717783Reviewed-by: Theresa  <twellington@chromium.org>
Reviewed-by: Changwan Ryu <changwan@chromium.org>
Commit-Queue: Ender <ender@google.com>
Cr-Commit-Position: refs/heads/master@{#688634}

The macro does not work on Chrome OS.

Bug: 805766
Change-Id: I503f095b2fb80032102782cb3e4ce5cffe4a2795
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1762308Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Commit-Queue: Alexei Svitkine <asvitkine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688633}

Bug: 995845
Change-Id: I830f5c9b1eac21b37f4ac534b0c862b8265265e7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1761437
Commit-Queue: Jacob DeWitt <jacde@chromium.org>
Commit-Queue: Alexander Cooper <alcooper@chromium.org>
Auto-Submit: Jacob DeWitt <jacde@chromium.org>
Reviewed-by: Alexander Cooper <alcooper@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688632}

This patch flips the PaintNonFastScrollableRegions flag to be enabled by
default. For more information about PaintNonFastScrollableRegions, see:
https://docs.google.com/document/d/1IyYJ6bVF7KZq96b_s5NrAzGtVoBXn_LQnya9y4yT3iw/view

The expectation has changed for compositor-touch-hit-rects-global.html
which is now correct and was incorrect due to https://crbug.com/992708.
The underlying bug has not been fixed.

Some expectations have new invalidations because going from scrollable
to non-scrollable (or vice versa) causes a scroll hit test display item
to disappear (or appear). paint/invalidation/resize-iframe-text.html and
paint/invalidation/compositing/iframe-inside-squashed-layer.html are
examples of tests changed due to this.

Some expectations have larger invalidations because the
resizer's scroll hit test display item uses the entire box as the
display item client. destroy-overlay-scrollbar.html and
destroy-scrollbar.html are examples of tests changed due to this.

Bug: 864567
Change-Id: Ia83de472ac2df10df09dd4476449dd6329848d11
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1734214Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Commit-Queue: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688631}

Introduce CWVCreditCardSaver for clients to interface with saving api.
This also adds support for saving cards to gpay if needed.

Bug: 993130
Change-Id: I7bc0acfe6553428f03f0e3f8c22a0824508f015b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1752560
Commit-Queue: John Wu <jzw@chromium.org>
Reviewed-by: Hiroshi Ichikawa <ichikawa@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688630}

It was already marked flaky in desktop_common but needs to be marked as
such in desktop_memory as well.

TBR=monicaciocea@chromium.org,eyaich@chromium.org

Bug: 859500, 995813
Change-Id: I2d93395a23d987ec11a2e3cd6d231d952ff50b23
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1762488Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688629}

This makes the field show up in the protocol log in sync-internals.

Bug: none
Change-Id: I04b4fec941ab5d1dae76b03d5b0aed27c55a82a0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1762241
Commit-Queue: Marc Treib <treib@chromium.org>
Commit-Queue: Jan Krcal <jkrcal@chromium.org>
Auto-Submit: Marc Treib <treib@chromium.org>
Reviewed-by: Jan Krcal <jkrcal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688628}

It does not flake under ASAN in local tests, anyway. Let's see!

Bug: 674475
Change-Id: Id1f9f960610cca08e860e45af3d5f5a3821f7519
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1762352
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Commit-Queue: Avi Drissman <avi@chromium.org>
Auto-Submit: Elly Fong-Jones <ellyjones@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688627}

TBR=estade@chromium.org

Bug: 995851
Change-Id: I3598ab3248f8bf93701107e56a31ae4757c9358c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1762328Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688626}

Submatches normally have the same relevance as their parents
and are thus sorted positionally with them. However, if
there are demote-by-type rules in effect, a parent (or a
submatch) can have an altered relevance and thus be
sorted away from their family.

This CL records within each submatch the type of its parent
so that it can be sorted identically.

Change-Id: I396dba33ba8808a2bae62b79352962f611feb23e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1721041
Commit-Queue: Kevin Bailey <krb@chromium.org>
Reviewed-by: Tommy Li <tommycli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688625}

Bug: 995652
Change-Id: I86b5c45f7ac1274d12f1c088fac7b0e97e085ba7
Tbr: kbr@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1761639Reviewed-by: Shrek Shao <shrekshao@google.com>
Commit-Queue: Shrek Shao <shrekshao@google.com>
Cr-Commit-Position: refs/heads/master@{#688624}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/0be80f8179c5..f878992e96bd

git log 0be80f8179c5..f878992e96bd --date=short --no-merges --format='%ad %ae %s'
2019-08-20 saklein@chromium.org AndroidService: Refactor uprev and unpin endpoints.
2019-08-20 saklein@chromium.org cros_sdk_lib: Improve run chroot version hook call.
2019-08-20 saklein@chromium.org cros_workon: Improve error message for invalid ebuilds.

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

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: Ic6d5e196ef8404b7857be0a872cad83beec33637
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1762271Reviewed-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@{#688623}

Otherwise, if it's destroyed through TLS, it can hang forever waiting
for a signal from the StackSamplingThread which never occurs.

This is going back to the behavior prior to
https://chromium-review.googlesource.com/c/chromium/src/+/1638578

R=ssid@chromium.org

Bug: 995323
Change-Id: I08863f5ee8ccd01c70b95bbce5fc28922dc06d1f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1761291Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: ssid <ssid@chromium.org>
Commit-Queue: oysteine <oysteine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688622}

Bug: 992597
Change-Id: Id18b03656b8cacac0d4a815d0602dfb4ec51a5ed
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1761427Reviewed-by: Theresa  <twellington@chromium.org>
Commit-Queue: Ender <ender@google.com>
Cr-Commit-Position: refs/heads/master@{#688621}

Allows to import from the core module in tools/perf without bringing
the whole of Telemetry as a dependency.

This will be particularly needed by the results_processor, to be able
to run it on a separate swarming task from where Telemetry ran.

Should be safe to land after all impacted scripts have been updated in:
https://chromium-review.googlesource.com/c/chromium/src/+/1760218

Bug: 981349
Change-Id: I75898455c3f261859ec2fe3d2cba2248c8b3ef17
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1762070
Auto-Submit: Juan Antonio Navarro Pérez <perezju@chromium.org>
Commit-Queue: John Budorick <jbudorick@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688620}

- Changes SerializedData return type to base::span<const uint8_t>. The
  old type, Vector<const uint8_t>, forces a copy. Changing to span will
  enable us to avoid copying cached code as it's passed from the browser
  via a mojo_base::BigBuffer. Eventually, we'll be able to move the
  BigBuffer to CachedMetadata.

Bug: chromium:992991
Change-Id: Ic4ac00282f3e0346649a1266e33cb57e1b40551a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1758727Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Commit-Queue: Bill Budge <bbudge@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688619}

This is an attempt to reduce heap usage in merges.

BUG: 982452
Change-Id: If17dad64ab8adde29384765720c210e7f5e72601
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1762083Reviewed-by: Owen Min <zmin@chromium.org>
Commit-Queue: Greg Thompson <grt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688618}

Bug: 927957
Change-Id: I5919885840a41ffec4e458382158aa40747bd64c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1760420Reviewed-by: Roger Tawa <rogerta@chromium.org>
Reviewed-by: Michael Giuffrida <michaelpg@chromium.org>
Commit-Queue: Felipe Cerqueira <cerqueira@google.com>
Cr-Commit-Position: refs/heads/master@{#688617}

This service is run in the GPU process and its interfaces are bound only
by the browser, brokering unfiltered requests from renderers. Logic is
simplified by removing all dependencies on Service Manager APIs, in
favor of the browser's brokering logic talking directly to
GpuProcessHost and maintaining a persistent connection to the service.

Bug: 977637
Change-Id: I9047889de659b8ff61df4bae40867d3b81d8127f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1761689
Commit-Queue: Ken Rockot <rockot@google.com>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688616}

These events got moved to the "fonts" category.
They are currently dropped and not visible in slow-report traces.

R=oysteine@chromium.org

Bug: 867931
Change-Id: I8940165b5196f074cac9735057ff60b129015cef
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1758340Reviewed-by: oysteine <oysteine@chromium.org>
Commit-Queue: Etienne Bergeron <etienneb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688615}

This is a reland of https://crrev.com/c/1648886

It was reverted due to a crash in a non-cq bot, see https://crbug.com/976331.

Patchset 1 shows the original patch and the specific non-CQ bots that failed on them are red.

Patchset 3 has the fix, and shows that the bots are now green.

I believe the bug is related to oilpan memory management in the custom struct I created. So instead I used a simpler std::pair to hold the callback and AsyncTaskId.

TBR: pfeldman@chromium.org
Bug: 851531
Change-Id: I625dacd61ea663097605df1f10e26baa58ce07c0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1761289
Commit-Queue: Josh Karlin <jkarlin@chromium.org>
Reviewed-by: Brandon Jones <bajones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688614}

Existing print_job_unittest doesn't need print_preview and add
a trivial unittest for PrintViewManagerBasic to exercise the code.

Bug: 993255
Change-Id: I2897c4cf9e46fbfc893a5868a544c5757efd6295
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1757022Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Joel Klinghed <the_jk@opera.com>
Cr-Commit-Position: refs/heads/master@{#688613}