GitLab

The public ios master/builders now have appropriate entries in mb_config.pyl

Bug: 951182
Change-Id: I500a3c00d47b7d5652654d14be2090c59214ed6f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1561846
Commit-Queue: Erik Chen <erikchen@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#649914}

Using wpt-import in Chromium 6f71daf3.
With Chromium commits locally applied on WPT:
0a8f3ffa "Use testdriver Action API in WPT pointerevent touch tests - Part 2"
adc34f41 "Fix web_test pointerevent_coordinates_when_locked on wpt"
8659792f "[WPT] Move wrapResult to common.js and clarify requestVia*() return values"
e525003f "Do not resume a suspended BaseAudioContext when AudioWorklet starts"


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:
foolip@chromium.org, lpz@chromium.org, robertma@chromium.org:
  external/wpt/tools

NOAUTOREVERT=true
TBR=robertma

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

TBR=caseq@chromium.org

Bug: 930717
Change-Id: I81751e805f76b1b2d570ae07aa0e598e8135b0ff
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1564871
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Auto-Submit: Elly Fong-Jones <ellyjones@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#649912}

https://webrtc.googlesource.com/src.git/+log/deb0854e685d..52caa0ef58c6


git log deb0854e685d..52caa0ef58c6 --date=short --no-merges --format='%ad %ae %s'
2019-04-11 gustaf@webrtc.org AEC3: Configuration parameter for disabling linear filter
2019-04-11 nisse@webrtc.org Reland "Delete CodecSpecificInfo argument from VideoDecoder::Decode"


Created with:
  gclient setdep -r src/third_party/webrtc@52caa0ef58c6

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.



BUG=chromium:b/130016532
TBR=webrtc-chromium-sheriffs-robots@google.com

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

Removes the EoC compatability drawing that we did a few releases ago.
The main difference is that the Peeking Bar has an up-arrow now instead
of the X that was used for EoC/GoC.

BUG=831783

Change-Id: Ia55532281d116c19df1e89054d64bf01609e0cc2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1558710
Commit-Queue: Theresa <twellington@chromium.org>
Auto-Submit: Donn Denman <donnd@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#649910}

This patch fixes a null dereference due to null paint properties.
Because this function is internals-only for testing, just rely on
clusterfuzz to verify the fix instead of adding a test.

Bug: 950928
Change-Id: I7a3ff93b62e5a28ec4b4989bc01b52ec707f5b18
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1564793
Auto-Submit: Philip Rogers <pdr@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Commit-Queue: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#649909}

This was left over when we removed pre-SPv175 code.

It was set for repeating fixed-position and table sections, but not
actually used. It had been used to force the slow path of visual rect
mapping using MapToVisualRectInAncestorSpace() before SPv175. After
SPv175 we no longer need to map rects into ancestor space.

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

This dates back to when the code was first introduced.  On consultation, both
sky@ and I think it was a typo, and the code was originally simply intending to
exclude the cases where there were no non-pinned tabs.

Bug: none
Change-Id: Ic864c4a6bb877b42baa57be17b1ab81665222d07
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1562622
Auto-Submit: Peter Kasting <pkasting@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#649907}

This Chromium implementation simply ignores it.

Bug: webrtc:10531
Change-Id: Iaee6f17ee081251775fe548a340ee7a47bd134f5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1559148
Auto-Submit: Karl Wiberg <kwiberg@chromium.org>
Reviewed-by: Henrik Grunell <grunell@chromium.org>
Commit-Queue: Karl Wiberg <kwiberg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#649906}

This provides the first step in refactoring the HintCacheStore's update
data objects. It adds the new update object without yet integrating to
the store - per merge considerations. It uses a factory method approach
to handle the two different types of constructor calls.

Bug: 932707
Change-Id: I188f68ad4f89ad866e6d37ff226cae41743c9a50
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1555422
Commit-Queue: Doug Arnett <dougarnett@chromium.org>
Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#649905}

StartupBrowserCreatorCorruptProfileTest.DeletedProfileFallbackToUserManager
TabManagerTest.UnfreezeTabOnNavigationEvent

TBR=fdoray@chromium.org

Bug: 918701, 951787
Change-Id: Id3b3b32abbd69113d7c175779fe40ece34a54159
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1564870
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Auto-Submit: Elly Fong-Jones <ellyjones@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#649904}

Broken by https://chromium-review.googlesource.com/c/chromium/src/+/1516120

Change-Id: I47760e47d125836d4719cde7998a0497bb252119
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1564814
Commit-Queue: Michael Thiessen <mthiesse@chromium.org>
Commit-Queue: Yaron Friedman <yfriedman@chromium.org>
Auto-Submit: Michael Thiessen <mthiesse@chromium.org>
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#649903}

Simultaneous roll of Dawn, shaderc, SPIRV-Cross etc. due to API changes.

BUG=chromium:951016

Change-Id: I5daf4376bb9845b4eed478b8cb1eb439560c800d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1564753
Commit-Queue: Frank Henigman <fjhenigman@chromium.org>
Commit-Queue: Corentin Wallez <cwallez@chromium.org>
Reviewed-by: Corentin Wallez <cwallez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#649902}

Accessibility testing revealed that there are tab traps in all of the text editors including read only ones. Once keyboard users tab into the editor, they cannot tab out the editor.

This change adds a shortcut to disable/re-enable tab for indentation, which allows keyboard users continue to use tab to navigate to next UI component.

Settings Shortcuts page screenshot: https://imgur.com/a/qeOjGoB

Change-Id: I026a5a9c47407634a78c2ccf1a0bc532baa39e07
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1545200Reviewed-by: Joel Einbinder <einbinder@chromium.org>
Commit-Queue: Junyi Xiao <juxiao@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#649901}

SyzyASAN is deprecated.

Change-Id: I1c831628bc1e420b379306257a1683fc8361753f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1564752
Auto-Submit: Vlad Tsyrklevich <vtsyrklevich@chromium.org>
Reviewed-by: Chris Hamilton <chrisha@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Commit-Queue: Robert Sesek <rsesek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#649900}

This is a design tweak which also enables the back and forward buttons
to be placed separately. Existing customized Touch Bars which contain
the grouped item still work; see the code comment for details.

I used Cocoa bindings for the buttons' enabled states instead of holding
pointers to them because I initially thought that the Touch Bar might allow the
group and individual buttons to coexist. Turns out no, but I kept the KVO
implementation because I like it.

It also includes a couple of other changes that came up while writing
this patch and during code review:

- The unit tests no longer look for a hard-coded list of items in a
  specific order. Instead, they verify that BrowserWindowDefaultTouchBar
  can create the items it claims to be able to create, and that no
  known-valid identifiers have stopped working.

- BrowserWindowDefaultTouchBar returns nil if it doesn't know about an
  identifier, instead of returning an empty Touch Bar item.

Bug: 937935
Change-Id: I8cdc6347bc667b0a24fa24fe2c6a56661747ac98
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1534238
Commit-Queue: Sidney San Martín <sdy@chromium.org>
Reviewed-by: Leonard Grey <lgrey@chromium.org>
Auto-Submit: Sidney San Martín <sdy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#649899}

Bug: chromedriver:2835, chromedriver:2854, chromedriver:2855
Bug: chromedriver:2856, chromedriver:2858
Change-Id: Ifce142ecca58b4f2583c8456b42e8d2a063182d9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1562499Reviewed-by: John Chen <johnchen@chromium.org>
Commit-Queue: Tatiana Buldina <buldina@chromium.org>
Cr-Commit-Position: refs/heads/master@{#649898}

This is pure refactoring, is replacing
using FormPredictions = std::map<uint32_t, PasswordFieldPrediction>;
with
using FormPredictions = std::vector<PasswordFieldPrediction>.

It simplifies code a little bit, and anyway the access is done with
range based loop.

The main point of this refactoring is that struct PasswordFieldPrediction
will be extended with names for iOS in the following CL.

Bug: 831123
Change-Id: I3cab46155ef4280ef0c413bfae740445f16f0ce1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1564159Reviewed-by: Maxim Kolosovskiy <kolos@chromium.org>
Commit-Queue: Vadym Doroshenko <dvadym@chromium.org>
Cr-Commit-Position: refs/heads/master@{#649897}

This CL adds the TPM force update logic with user aknowledgment for the
device wide policy TPMForceUpdateSRKVulnerable introduced in CL:1469462.

Bug: 875266
Change-Id: I8b25aa5f3218b6754b8439afdf8ec8bd47b53ec3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1554495
Commit-Queue: Andreea-Elena Costinas <acostinas@google.com>
Reviewed-by: Pavol Marko <pmarko@chromium.org>
Reviewed-by: Dominic Battré <battre@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#649896}

When receiving a blob and an onComplete callback occurs,
read any remaining bytes.

This avoids attempts to read bytes after the connection
has closed.

BUG=951763

Change-Id: I7cf19c7e8d5d63c89e9b3116fbf28ad731815290
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1564002Reviewed-by: Ted Choc <tedchoc@chromium.org>
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Commit-Queue: Eric Willigers <ericwilligers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#649895}

Currently, search suggestions' descriptions (e.g. the 'Google Search'
suffix) are classified DIM. However, document suggestions' descriptions
(e.g. the 'Apr 3 - Google Docs' suffix) are classified NONE.

Bug: 366623
Change-Id: I14ea6d9e9342e5793cfa73762e0efc233fe3df23
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1555353Reviewed-by: Justin Donnelly <jdonnelly@chromium.org>
Commit-Queue: manuk hovanesian <manukh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#649894}

Adds new flag.

Bug: 951422
Change-Id: If04dc0f33071474359b8ee8b95d5ffb59eb70afd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1564117
Auto-Submit: Nazerke Kalidolda <nazerke@google.com>
Reviewed-by: Mark Cogan <marq@chromium.org>
Commit-Queue: Nazerke Kalidolda <nazerke@google.com>
Cr-Commit-Position: refs/heads/master@{#649893}

- Creates an UpdatePasswordFormUsernameAndPassword util function
which updates the FormManager Username and password.
- It should be used when editing these values on the Bubble in
desktop and on the Modal Infobar on Mobile.

Bug: 945478
Change-Id: I990c5983a34e33a67c75a1db662226a2a7e3b10f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1560448Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org>
Commit-Queue: Sergio Collazos <sczs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#649892}

Bug: 911864
Change-Id: Icdc85ddf13f82992b4b20a1b9f17b7aaff501a54
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1559354Reviewed-by: Mark Cogan <marq@chromium.org>
Commit-Queue: Sergio Collazos <sczs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#649891}

Initialize TabGrid LayoutManager with proper span count based on
initial orientation.

Bug: 945740
Change-Id: Ifd50eee201f9087e376f3a3237fe727ed3658d42
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1561951Reviewed-by: Wei-Yin Chen (陳威尹) <wychen@chromium.org>
Reviewed-by: Yusuf Ozuysal <yusufo@chromium.org>
Commit-Queue: Yue Zhang <yuezhanggg@google.com>
Cr-Commit-Position: refs/heads/master@{#649890}

https://chromium.googlesource.com/angle/angle.git/+log/e6b23e45b380..d581f918e90d


git log e6b23e45b380..d581f918e90d --date=short --no-merges --format='%ad %ae %s'
2019-04-11 syoussefi@chromium.org Vulkan: few more EGL dEQP suppressions on Android


Created with:
  gclient setdep -r src/third_party/angle@d581f918e90d

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

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

According docs the LOAD_ONLY_FROM_CACHE flag guarantees that
any navigation with it will fail if it cannot serve the
resource from the cache (or some equivalent local store).
However, this flag is used only by http_cache_transaction
which isn't created if we are using network context without
http cache at all.
Without cache there is only a http_network_transaction which
completely ignore LOAD_ONLY_FROM_CACHE flag and doesn't fail
requests with it.

Also, this CL fixes `setBlockNetworkLoads` for android webview
without cache.
https://cs.chromium.org/chromium/src/third_party/android_tools/sdk/sources/android-25/android/webkit/WebSettings.java?type=cs&q=setBlockNetworkLoads&g=0&l=887

Change-Id: I04c027fe671f83020cba580fa5c763b09fb00886
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1556775
Commit-Queue: Maks Orlovich <morlovich@chromium.org>
Reviewed-by: Maks Orlovich <morlovich@chromium.org>
Cr-Commit-Position: refs/heads/master@{#649888}

Bug: 951774
Change-Id: I7988f56b462c3138037a165e920a8f462d469e29
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1564652
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Commit-Queue: John Budorick <jbudorick@chromium.org>
Auto-Submit: Elly Fong-Jones <ellyjones@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#649887}

This patch makes sure the FirstSetupComplete flag is only set when
the user turn Sync on for the first time (either during sign-in
or later using Google services settings).

FSC flag on & Sync on => Sync is on and working
FSC flag on & Sync off => Sync is off, the user turned Sync on
                          at least once
FSC flag off & Sync on => Sign-in is still in progress
FSC flag off & Sync off => The user doesn't want Sync

Changes in this patch:
* FSC flag should not be set when opening the advanced sign-in settings.

* The advanced sign-in settings set FSC flag on, only when the user taps
on "Confirm" with Sync on.

* Sync toggle is off, when FSC flag is off, and Sync on

* In Google services settings (in settings mode) FSC flag is turned on
as soon as the user turns Sync on.

* When closing the Google services settings (in settings mode), if FSC
flag is still off, Sync is turned off since the user doesn't want Sync
(otherwise FSC flag would have been on, by turning Sync on).

Bug: 948681
Change-Id: I86e7b74374e20e71fd069421733a300a187c777a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1556790
Commit-Queue: Jérôme Lebel <jlebel@chromium.org>
Reviewed-by: Jérôme Lebel <jlebel@chromium.org>
Reviewed-by: Mihai Sardarescu <msarda@chromium.org>
Reviewed-by: Gauthier Ambard <gambard@chromium.org>
Cr-Commit-Position: refs/heads/master@{#649886}

Bug: 951390
Change-Id: I049b51ba7c0b6021d2f293bb4ce91bae27745415
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1564114Reviewed-by: Vadym Doroshenko <dvadym@chromium.org>
Commit-Queue: Maxim Kolosovskiy <kolos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#649885}

They're never read.

Bug: 948148
Change-Id: I4a11ed4508c28b3b81342e256f62432173d0ce64
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1564116
Auto-Submit: Marc Treib <treib@chromium.org>
Commit-Queue: Mohamed Amir Yosef <mamir@chromium.org>
Reviewed-by: Mohamed Amir Yosef <mamir@chromium.org>
Cr-Commit-Position: refs/heads/master@{#649884}

I've double checked with UX/PM that this is okay to remove.

Bug: 924761
Change-Id: I9aa33479c8c738f40c61e6b9a31b236a8c31d739
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1563598Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Manu Cornet <manucornet@chromium.org>
Cr-Commit-Position: refs/heads/master@{#649883}

According to the kill manpage:

     If  sig is  0, then  no signal  is sent,  but existence  and
     permission checks are  still performed; this can  be used to
     check for the existence of a  process ID or process group ID
     that the caller is permitted to signal.

This seems to be tripping up at least ESET anti-virus, causing an
unnecessary crash in the audio process.

Bug: 904787
Change-Id: Ibdfe5db69fa494e4a0438ae0244f20820a0220af
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1559088
Auto-Submit: Oskar Sundbom <ossu@chromium.org>
Commit-Queue: Robert Sesek <rsesek@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#649882}

Lack of data_model for AutofillDataModelChanges of type REMOVE caused
hacky code for the sync bridges for AUTOFILL_PROFILE and for
WALLET_METADATA. They could not distinguish deletions of local profiles
from deletions of server profiles.

This CL fixes it by adding data_model also for removals. It has minimal
overhead in the database and simplifies (sync) code.

Bug: 950419
Change-Id: If4f9462efa73ad2b5d89df4051104b19fff306c5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1559326
Commit-Queue: Parastoo Geranmayeh <parastoog@google.com>
Reviewed-by: Parastoo Geranmayeh <parastoog@google.com>
Cr-Commit-Position: refs/heads/master@{#649881}

https://android.googlesource.com/platform/external/perfetto.git/+log/de4e8874ae82..6a80f56a7690


git log de4e8874ae82..6a80f56a7690 --date=short --no-merges --format='%ad %ae %s'
2019-04-11 lalitm@google.com Merge "perfetto: add dump_ftrace_stats tool"


Created with:
  gclient setdep -r src/third_party/perfetto@6a80f56a7690

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

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

TBR=pmarko@chromium.org
BUG=None

Change-Id: I76636c02a65c06286ddbadbc2c7ff292ded8e674
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1563999Reviewed-by: Lutz Justen <ljusten@chromium.org>
Commit-Queue: Lutz Justen <ljusten@chromium.org>
Cr-Commit-Position: refs/heads/master@{#649879}

BUG=496832

Change-Id: Id6c4ca6629a88334cc9c5e4eb5d761663148106a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1562758Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Toni Baržić <tbarzic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#649878}

https://webrtc.googlesource.com/src.git/+log/7ddef1af8859..deb0854e685d


git log 7ddef1af8859..deb0854e685d --date=short --no-merges --format='%ad %ae %s'
2019-04-11 yinwa@webrtc.org Minor fix, rename method name to setNetworkStatePredictorFactoryFactory().
2019-04-11 nisse@webrtc.org Delete unused class RTCMediaConstraints (JSON)
2019-04-11 nisse@webrtc.org Delete unused class MockVCMFrameTypeCallback
2019-04-11 ilnik@webrtc.org Disable padding for paused encoders even on reconfiguration
2019-04-11 jonasolsson@webrtc.org Add support for lists to the FieldTrialParser.


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

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.



BUG=chromium:None,chromium:None,chromium:None
TBR=webrtc-chromium-sheriffs-robots@google.com

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

Move initialization from the constructor initializer list to the class
declaration. Keep only the ones depending on the constructor's
input arguments.

Bug: 950969
Change-Id: Ia8872089b0a0c323e49219ac05e433edff83d181
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1564078Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#649876}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/3ec1a396fb79..389fd9db15e8


Created with:
  gclient setdep -r src-internal@389fd9db15e8

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
TBR=harrisjay@chromium.org,ellyjones@chromium.org,btolsch@chromium.org

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