GitLab

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/688dd321c9df..9779b146cdfe


git log 688dd321c9df..9779b146cdfe --date=short --no-merges --format='%ad %ae %s'
2019-05-29 jrn@google.com git-cl: Use modern environment variable name to trigger tracing
2019-05-29 iannucci@chromium.org Roll led to latest version.


Created with:
  gclient setdep -r src/third_party/depot_tools@9779b146cdfe

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

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=agable@chromium.org

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

This CL splits the CacheStorageManager into separate interface and
implementation classes.  This serves two purposes:

1. It allows us to support separate backend implementations as
   described in crbug.com/940449.
2. It will also allows us to provide a cross-sequence wrapper
   implementation for external clients accessing cache_storage from
   different threads.

This CL initially creates the Legacy implementation in the
cache_storage_manager.h and .cc files.  A follow-up CL will move the
LegacyCacheStorageManager to separate files in the legacy directory.

Bug: 940449,960012
Change-Id: I5e03ca7de5890d0984add581b6d6bf10d9338497
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1626503Reviewed-by: Daniel Murphy <dmurph@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Commit-Queue: Ben Kelly <wanderview@chromium.org>
Cr-Commit-Position: refs/heads/master@{#664605}

https://pdfium.googlesource.com/pdfium.git/+log/ca41bc48d6f6..12899533d341


git log ca41bc48d6f6..12899533d341 --date=short --no-merges --format='%ad %ae %s'
2019-05-30 tsepez@chromium.org Remove some more xfa/fwl circular includes into xfa/fxfa
2019-05-30 thestig@chromium.org Reorganize |kCMYK| constant.
2019-05-30 thestig@chromium.org Add tests for FPDF_SetPrintMode().


Created with:
  gclient setdep -r src/third_party/pdfium@12899533d341

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

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

R=mpearson@chromium.org,avi@chromium.org
BUG=953522

Change-Id: I1db3a0f648e70adece42f34a4db49eec22569790
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1627903
Commit-Queue: Dan Beam <dbeam@chromium.org>
Commit-Queue: Avi Drissman <avi@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Mark Pearson <mpearson@chromium.org>
Auto-Submit: Dan Beam <dbeam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#664603}

Future cls will use the SecureDnsMode specified in these two structs
to control host resolution behavior. This change should be a no-op.

Bug: 878582
Change-Id: I2a1434ede92ec6d9997291571e4d32e0b725ea37
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628013Reviewed-by: Paul Jensen <pauljensen@chromium.org>
Reviewed-by: Eric Orth <ericorth@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Commit-Queue: Katharine Daly <dalyk@google.com>
Cr-Commit-Position: refs/heads/master@{#664602}

Bug: 957477
Change-Id: Ica275a246afc3791cf06d32b8a67fa4587d1083b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636651Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Reviewed-by: Timothy Loh <timloh@chromium.org>
Commit-Queue: Joel Hockey <joelhockey@chromium.org>
Cr-Commit-Position: refs/heads/master@{#664601}

Find-in-Page requires |NGOffsetMapping|, which however isn't available
on every block due to layout bugs. As the layout bug is currently hard
to fix, we work around it in Find-in-Page so that in production build,
it ignores those failed blocks instead of crashing. It still hits a
DCHECK in DCHECK-enabled builds.

Bug: 955678
Change-Id: Ia5e6f45ce8f343deb6c4890de9fac4bdb2be712f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636304
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Commit-Queue: Emil A Eklund <eae@chromium.org>
Auto-Submit: Xiaocheng Hu <xiaochengh@chromium.org>
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#664600}

Change-Id: Ie2414402ecceb3d51d39a1f57a5dfc901b31300e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636454
Commit-Queue: Matthew Webb <noviv@google.com>
Commit-Queue: Kim Paulhamus <kpaulhamus@chromium.org>
Commit-Queue: Martin Kreichgauer <martinkr@google.com>
Auto-Submit: Matthew Webb <noviv@google.com>
Reviewed-by: Kim Paulhamus <kpaulhamus@chromium.org>
Reviewed-by: Martin Kreichgauer <martinkr@google.com>
Cr-Commit-Position: refs/heads/master@{#664599}

https://webrtc.googlesource.com/src.git/+log/72055b11beb9..74bebc597e25


git log 72055b11beb9..74bebc597e25 --date=short --no-merges --format='%ad %ae %s'
2019-05-29 sukhanov@webrtc.org Add OnDatagramAcked interface


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

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

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

The first two experiments with compositing priorities:

+ Always set compositing priority to VeryHigh (unless it already is set to Highest).
+ Set compositing priority to VeryHigh when compositing is fast (unless it already is set to Highest).

Bug: 966177
Change-Id: Ic871b307de5caebad34dcda66f8d1ee360411df4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1626020
Commit-Queue: Katie Dillon <kdillon@chromium.org>
Reviewed-by: Alexander Timin <altimin@chromium.org>
Reviewed-by: Scott Haseley <shaseley@chromium.org>
Cr-Commit-Position: refs/heads/master@{#664597}

Also added a DCHECK to make sure that we never
set NeedsLayout flags while in intermediate layout.

Bug: 967361
Change-Id: I078d3884025c0d659cf7a25df694e082d6dd3f1c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1633031
Commit-Queue: Aleks Totic <atotic@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#664596}

This reverts commit 2fd01309.

Reason for revert: Disabling App Management before branch point.

Original change's description:
> [App Management] Enable App Management by default.
> 
> Enable App Management by default. Current entry points are about:settings
> and about:app-management.
> 
> Bug: 906508
> Change-Id: I0118a4b51eda6e65bc72186e771fc2ede2acb45f
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1610658
> Reviewed-by: Dominick Ng <dominickn@chromium.org>
> Commit-Queue: Jeevan Shikaram <jshikaram@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#659341}

TBR=dominickn@chromium.org,jshikaram@chromium.org

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

Bug: 906508
Change-Id: I302364e6573eaf21b7a0a3a93ecf517fc473740a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636652
Commit-Queue: Jeevan Shikaram <jshikaram@chromium.org>
Commit-Queue: Dominick Ng <dominickn@chromium.org>
Auto-Submit: Jeevan Shikaram <jshikaram@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Cr-Commit-Position: refs/heads/master@{#664595}

https://skia.googlesource.com/skia.git/+log/b3f82dddfc61..eca7315109de


git log b3f82dddfc61..eca7315109de --date=short --no-merges --format='%ad %ae %s'
2019-05-29 fmalita@chromium.org [skottie] Add a Shaper line buffer
2019-05-29 brianosman@google.com Fix divide by zero in interpreter test
2019-05-29 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial).
2019-05-29 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial).


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

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

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

https://quiche.googlesource.com/quiche.git/+log/0220865bffc1..b417d60c04d8

$ git log 0220865bf..b417d60c0 --date=short --no-merges --format='%ad %ae %s'
2019-05-29 dschinazi Add a client connection ID to version negotiation packet creation
2019-05-29 dschinazi Add quic_no_framer_object_in_dispatcher to QuicVersionInitializeSupportForIetfDraft
2019-05-28 dschinazi Prepare tests and fuzzer for client connection IDs
2019-05-28 dschinazi Rename QUIC connection ID to server connection ID, part 2
2019-05-28 fayang gfe-relnote: In QUIC, only decrease cwnd gain and pacing gain when cwnd increases or allow cwnd to decrease in initial cwnd experiment. Protected by gfe2_reloadable_flag_quic_gfe_selected_initial_cwnd_experiments and ENABLED quic_fix_bbr_cwnd_in_bandwidth_resumption.
2019-05-28 wub gfe-relnote: Remove stateless reject from QUIC. This deprecates two flags in the false position: --gfe2_reloadable_flag_enable_quic_stateless_reject_support and --gfe2_reloadable_flag_quic_use_cheap_stateless_rejects.
2019-05-28 fkastenholz QuicConnection methods call CloseConnection rather than TearDownLocalConnectionState

Created with:
  roll-dep src/net/third_party/quiche/src src/third_party/quic_trace/src

Change-Id: Iebb94aea950f1b966c7b9e5765d0a97c27a0877b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636395
Commit-Queue: Ryan Hamilton <rch@chromium.org>
Auto-Submit: Ryan Hamilton <rch@chromium.org>
Reviewed-by: Zhongyi Shi <zhongyi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#664593}

https://swiftshader.googlesource.com/SwiftShader.git/+log/d5f462c6ab22..761ce8af8341


git log d5f462c6ab22..761ce8af8341 --date=short --no-merges --format='%ad %ae %s'
2019-05-29 chrisforbes@google.com Adjust llvm7 file list to include passes required for arm target


Created with:
  gclient setdep -r src/third_party/swiftshader@761ce8af8341

The AutoRoll server is located here: https://autoroll.skia.org/r/swiftshader-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: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=swiftshader-team+autoroll@google.com

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

I applied following command to renmae
$ git grep --name-only 'WebKit Linux Trusty ' testing/ infra/ | \
  xargs sed -i 's/WebKit Linux Trusty /WebKit Linux /g'

This is step 3 written in
https://chrome-internal-review.googlesource.com/c/infradata/config/+/1341927

Bug: 954450
Change-Id: Ia29366bcdb60d7b28b44964a89d0033855866b8a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1635069Reviewed-by: John Budorick <jbudorick@chromium.org>
Reviewed-by: Ben Pastene <bpastene@chromium.org>
Commit-Queue: Takuto Ikuta <tikuta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#664591}

Separate recording of extension API function calls into three groups:
- WebUI function calls
- Component extension function calls
- "Normal" (i.e., non-component) extension function calls

This makes it easier to determine whether an API is being used by
extensions "in the wild", rather than just ones built into Chrome, as
well as providing insight into function calls by WebUI.

Bug: 951556
Change-Id: I784d1a3b3debd4405f332f53701e537c5e2c7ae9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1603962Reviewed-by: Robert Kaplow (slow) <rkaplow@chromium.org>
Reviewed-by: Karan Bhatia <karandeepb@chromium.org>
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#664590}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/095baa6e3666..a694bab26bc0


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

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.

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

BUG=chromium:947531
TBR=ricea@google.com,jeffreycohen@google.com,seblalancette@google.com,mkwst@google.com

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

A WebAXObject holds  An AXObject as a WebPrivatePtr which holds a AXObjectCacheImpl Member.

In order to persist the AXObjectCacheImpl, we need to directly hold a Persistent<AXObjectCacheImpl> in ScopedActionAnnotator so that in our destructor, we can be guaranteed the AXObjectCacheImpl is still around.

Bug: 966935
Change-Id: I5c0c1322af58d5ee388e3ef448c0ccf767e50b34
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1629184
Commit-Queue: David Tseng <dtseng@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#664588}

There may be cases where TabGroupUI is constructed and then destroyed
wihtout calling initWithNative. This is a band-aid fix to address that
and not attempt to destroy members that are not assigned yet. (The
members are not individually checked to make the CL shorter, as we may
need to cherry-pick)

BUG=966769

Change-Id: I991c99c65d024e4115e327f6252810409e512951
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636456Reviewed-by: Pedro Amaral <amaralp@chromium.org>
Commit-Queue: Yusuf Ozuysal <yusufo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#664587}

This change exposes the setStreams() method of RTCRtpSender, which allows
changing the stream associations of an existing transceiver.

Intent to Implement and Ship:
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/g5Grj_VtF8Q

Drive-by: Fix minor lint issues.

Bug: 844386
Change-Id: I7fe463d6811d5cb74cb297bf81d5bc90040fe86a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1611836
Commit-Queue: Guido Urdaneta <guidou@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Reviewed-by: Henrik Boström <hbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#664586}

The build history for these bots have no builds in the last year (if
any).

Change-Id: I8f8fbdb2f25d6ab76ce07180eab7dd1f17abcf6f
Bug: 968167
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1635196Reviewed-by: Ben Pastene <bpastene@chromium.org>
Commit-Queue: Garrett Beaty <gbeaty@chromium.org>
Cr-Commit-Position: refs/heads/master@{#664585}

- Logs a user action when the user presses search+click
  combination to emulate right click.
- The action will only be counted when flags/settings are mapping
  search+click to right click. If the default alt-click
  behavior is enabled then pressing search+click won't be counted
- This is to measure the transition of users from the legacy
  alt+click behavior to the new search+click.
- Code that uses this is in a follow up CL

BUG=chromium:248762

Change-Id: Ia72520cd6dfcc0e2521c895b1e3bf298da28c95c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1603543
Commit-Queue: Zentaro Kavanagh <zentaro@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Reviewed-by: Mark Pearson <mpearson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#664584}

It's left as unimplemented because Android WM handles insets by VK for
most cases.
However, Android WM can't move the SystemTray up for inline-reply in an
Android notification because from Android WM's point of view,
notificaiton is placed at (0, 0).
This CL implements ArcImeService::EnsureCaretNotInRect to cover that
case.
This CL changes the behavior of windowed Android app with a11y keyboard.
Before this CL, a position of a window is not changed by a11y keyboard
visibility, but after this CL a position can be changed not to be
covered by a11y keyboard.

      SystemTray moves up if there is a space for it.

Bug: b/114115612
Test: manual - Focus on inline reply of an Android notificatioln and
Change-Id: Ib666b6c269a8fc36195d30affa4c7a8a805560d7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1631859Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Reviewed-by: Tetsui Ohkubo <tetsui@chromium.org>
Commit-Queue: Yuichiro Hanada <yhanada@chromium.org>
Cr-Commit-Position: refs/heads/master@{#664583}

For same-process iframes, the render throttling status gets updated
immediately after a lifecycle update, in
LocalFrameView::UpdateViewportIntersectionsForSubtree. That method
does a frame tree walk, so that all descendant frames also get
updated. However, for an OOPIF, throttling status changes happen via
IPC from the embedding page. When that happens, we need to propagate
the change to any same-process descendant frames.

BUG=962382

Change-Id: I30c2c0846d16dadccca4b02056ac696c34594fd8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1635869Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Stefan Zager <szager@chromium.org>
Cr-Commit-Position: refs/heads/master@{#664582}

Bug: 813093
Change-Id: Id7551c2b2f4bd0296203b035308aba57b0e5465e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1437895Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: David Bienvenu <davidbienvenu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#664581}

This CL:
- Adds experimental button in tablet mode toolbar layout
- Implements experimental button related functions in ToolbarLayout.

BUG=958982
R=twellington@chromium.org

Change-Id: I07f8c5fb8ed2d2cb9745bc0e64750bf2e45451ca
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1632553Reviewed-by: Theresa <twellington@chromium.org>
Commit-Queue: Pavel Yatsuk <pavely@chromium.org>
Cr-Commit-Position: refs/heads/master@{#664580}

Using wpt-import in Chromium acea1f51.
With Chromium commits locally applied on WPT:
e90c6ef0 "NG/DL: Implement size containment (and display lock) for NG fieldset algo"
abf2ac5e "webrtc wpt: avoid race conditions"
d9a6ec05 "[MediaStreamTrack] Remove tests and existing support for the 'volume' property."
0882bebe "Change ICE connection state on transceiver changes"
1bbbd106 "Add feature policy for client hints, used for third-party subresources."
2229f484 "Revert "Change ICE connection state on transceiver changes""


Note to sheriffs: This CL imports external tests and adds
expectations for those tests; if this CL is large and causes
a few new failures, please fix the failures by adding new
lines to TestExpectations rather than reverting. See:
https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md

Directory owners for changes in this CL:
chcunningham@chromium.org, wolenetz@chromium.org:
  external/wpt/media-source

NOAUTOREVERT=true
TBR=raphael.kubo.da.costa

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

This vastly simplifies the backend pipeline needed to symbolize IPC
messages, requiring a simple lookup table rather than symbolization
followed by source code parsing. It also means the raw IPC message
IDs are constant across Chrome versions/builds/platforms, which
facilitates aggregation.

The impact on binary size is roughly a nop; on some platforms slightly
better, on some slightly worse. The overall impact is still about
the same.

BUG=950668

Change-Id: I13661059db79c1b091afdf68daed14325a18f26a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1615386Reviewed-by: François Doray <fdoray@chromium.org>
Reviewed-by: Ken Rockot <rockot@google.com>
Reviewed-by: oysteine <oysteine@chromium.org>
Commit-Queue: Chris Hamilton <chrisha@chromium.org>
Cr-Commit-Position: refs/heads/master@{#664578}

DDoc: go/cups-plugin

The service should lazily start once it knows the daemon has started;
this CL adds a WaitForServiceToBeAvailable method to the CupsProxyClient
for that purpose.

This CL also adds the CupsProxyServiceManager, which is started with the
browser, waits for daemon startup, then starts the service by
connecting to it.
Note: the service maintains its own lifetime and connection with the
daemon; this manager simply starts it.

Bug: chromium:945409
Test: TBD
Change-Id: Idf08a1153493c8e7abfcd5ad291203ea12a692b6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1586540Reviewed-by: Lei Zhang <thestig@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Ken Rockot <rockot@google.com>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Dan Erat <derat@chromium.org>
Commit-Queue: Luum Habtemariam <luum@chromium.org>
Cr-Commit-Position: refs/heads/master@{#664577}

Introduction of the "none" eye missed inverting the logic for
determining which viewport to return in the XRWebGLLayer, which caused
it to return the viewport typically associated with the right eye, which
is null for inline sessions.

Bug: 966077
Change-Id: I6ca51c327f7081ea4180e8515cc076b3ed8c4de8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1635731Reviewed-by: Alexander Cooper <alcooper@chromium.org>
Reviewed-by: Klaus Weidner <klausw@chromium.org>
Commit-Queue: Brandon Jones <bajones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#664576}

And also add its trybot mb config.

R=jbudorick

Bug: 947531
Change-Id: I8e100f4b51e77984b51328cc1bded6e725b7fa7e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636478
Commit-Queue: Ben Pastene <bpastene@chromium.org>
Commit-Queue: John Budorick <jbudorick@chromium.org>
Auto-Submit: Ben Pastene <bpastene@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#664575}

In https://chromium-review.googlesource.com/c/chromium/src/+/1607149, we did:

  This CL also does some code cleanup. This involved making sure we always
  observe `PartitionAllocReturnNull` in every case where
  `MEMORY_TOOL_REPLACES_ALLOCATOR` is defined; previously we did not.

But, we missed a spot. This CL fixes that.

Bug: None
Change-Id: I408fa95ca216a7a53196f2e9dae826190eef7a0a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636709Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Chris Palmer <palmer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#664574}

This CL does a few things:
* Adds the icon for each device type.
* Adds ability to send a tab after the user selects a device.
* Enables the bottom controller when the feature is enabled.
* Adds the last active time to the device picker.
* Formatting of the device picker list.

Bug: 949223
Change-Id: Ic2d691a68f0fb7e55a375ee932b07633e5c644e3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1633330Reviewed-by: Matthew Jones <mdjones@chromium.org>
Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Reviewed-by: sebsg <sebsg@chromium.org>
Commit-Queue: Tanya Gupta <tgupta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#664573}

Bug: 914410
Change-Id: I8f56b3211ce5551f85270291e1a432f7746cd309
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1626733
Commit-Queue: Bettina Dea <bdea@chromium.org>
Reviewed-by: Varun Khaneja <vakh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#664572}

This CL disabled the test only on Android K where it's flaky.

TBR: mvanouwerkerk@chromium.org
Bug: 931198
Change-Id: I66a1b2b785773c97afd806f064b9519315039a05
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636714Reviewed-by: Shimi Zhang <ctzsm@chromium.org>
Commit-Queue: Shimi Zhang <ctzsm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#664571}

Whatever issues caused us to initially disable the fullscreen API from
fullscreen PWAs, they no longer seem to be present. In testing the
sample in issue 720304 I couldn't find any issues.

Bug: 963929
Change-Id: I6fab2f4a558c2b7fdbd61b8ed92714f671bce7db
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1627563Reviewed-by: Dominick Ng <dominickn@chromium.org>
Commit-Queue: Michael Thiessen <mthiesse@chromium.org>
Cr-Commit-Position: refs/heads/master@{#664570}

I was trying to look at some CustomTabs user action sequences and these
were obscuring the view.

Change-Id: I6b173f3964bd22692be78743d271d15043f4189a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1634562
Commit-Queue: Alexei Svitkine <asvitkine@chromium.org>
Auto-Submit: Yaron Friedman <yfriedman@chromium.org>
Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Reviewed-by: sebsg <sebsg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#664569}

Sanitizers replace the default memory allocator with a custom one.
Unit tests that depend on tcmalloc functionality should not execute in
such cases. These cases are identified by compile macro
MEMORY_TOOL_REPLACES_ALLOCATOR being defined.

While we are at it, don't instantiate the heap profiler when
tcmalloc is not used, as the collector depends on tcmalloc too and it
may result in flakiness. We can enable it for sanitizers once we
remove dependency on tcmalloc.

BUG=chromium:724399,b:70905156

Change-Id: I4ded0301e6ef190b6b45c7f01405005765f3c5e0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636611Reviewed-by: Gabriel Marin <gmx@chromium.org>
Reviewed-by: Alexei Filippov <alph@chromium.org>
Commit-Queue: Gabriel Marin <gmx@chromium.org>
Cr-Commit-Position: refs/heads/master@{#664568}

This CL adds a flag that can be used to load an extension as login
screen extension during API tests.

Bug: 957573
Change-Id: Iba6299721df654d66856c7a24a4292f82938063b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1599177
Commit-Queue: Alexander Hendrich <hendrich@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#664567}