GitLab

r652224 added initial support for removing headers through the Declarative Net
Request API. This CL fixes an existing TODO by preventing web request extensions
from adding back headers removed by DNR.

BUG=947591

Change-Id: I8a6eb4bd3ae8d9bdd556feefb454cbd30944aa74
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1565613
Commit-Queue: Karan Bhatia <karandeepb@chromium.org>
Auto-Submit: Karan Bhatia <karandeepb@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#652646}

https://chromium.googlesource.com/catapult.git/+log/1ff0422ebea4..cc0161223605


git log 1ff0422ebea4..cc0161223605 --date=short --no-merges --format='%ad %ae %s'
2019-04-19 benjhayden@chromium.org Migrate ExistingBugRequest, NewBugRequest to es6 module
2019-04-19 benjhayden@chromium.org Migrate cp-radio-group to es6 module
2019-04-19 benjhayden@chromium.org Migrate chart-legend to es6 module
2019-04-19 benjhayden@chromium.org Migrate cp-textarea to es6 module
2019-04-19 benjhayden@chromium.org Migrate sparkline-compound to es6 module.
2019-04-19 benjhayden@chromium.org Migrate ConfigRequest, ReportRequest to es6 modules.


Created with:
  gclient setdep -r src/third_party/catapult@cc0161223605

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

BUG=chromium:950011,chromium:950011,chromium:950011,chromium:950011,chromium:950011,chromium:950011
TBR=charliea@chromium.org

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

Continues the refactor of ComponentUpdateData out of the HintCacheStore
by using the new HintUpdateData. HintUpdateData can be constructed with
either component or fetched hints.

Bug: 932707
Change-Id: Ib84208df9922028f99854339202e1896ffe75604
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1572870Reviewed-by: Doug Arnett <dougarnett@chromium.org>
Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Commit-Queue: Michael Crouse <mcrouse@chromium.org>
Cr-Commit-Position: refs/heads/master@{#652644}

Attempting to deflake Windows 10 bot.
According to the flakiness dashboard,
external/wpt/fullscreen/api/element-ready-check-containing-iframe-manual.html
now passes consistently. Therefore, removing it from TestExpectations.

TBR=mustaq@chromium.org

Bug: 908841, 954586
Change-Id: Ia51a032a5470454527eefab570c61d57caa73d88
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1575165
Commit-Queue: Bret Sepulveda <bsep@chromium.org>
Reviewed-by: Bret Sepulveda <bsep@chromium.org>
Cr-Commit-Position: refs/heads/master@{#652643}

Similar to http://crrev/c/1266611, this dumps WebView's CommandLine
state (including the "--enable-features" and "--disable-features"
switches) to the log when the "dummy app"
("org.chromium.webview_log_verbosifier") is present.

Notably, this will give us an idea of whether the NetworkService is
enabled or not (FieldTrialList + CommandLine state + knowledge of
whether it is enabled-or-disabled-by-default should be sufficient).

This also adds a usage guide for the webview verbosifier app, including
the new commandline stuff.

Skipping presubmit for LOG(INFO).

NOPRESUBMIT=true

Bug: 929886, 918221
Test: Manual (following the steps in the new docs)
Test: Upload to gerrit > open file > click "gitiles"
Change-Id: I4c698d661c340f760e2a90da20439b44a56ea38b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1573087
Commit-Queue: Nate Fischer <ntfschr@chromium.org>
Reviewed-by: Richard Coles <torne@chromium.org>
Reviewed-by: Paul Miller <paulmiller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#652642}

Attempting to deflake Windows 10 bot.
external/wpt/css/css-text/white-space/control-chars-08E.html now passes
consistently on Windows 10, so marking it Failure only on Windows 7.

TBR=eae@chromium.org

Bug: 893490, 954586
Change-Id: Id82597d887e8579d50c3a0d73530c07657a0658c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574592Reviewed-by: Emil A Eklund <eae@chromium.org>
Reviewed-by: Bret Sepulveda <bsep@chromium.org>
Commit-Queue: Bret Sepulveda <bsep@chromium.org>
Cr-Commit-Position: refs/heads/master@{#652641}

Most of this file is awkwardly tied up with prtime.cc or
StringTokenizer, but convert some boring ones.

Bug: 820198
Change-Id: I339911e7cfbe6136a82d71ec1d1cd000ccc7b91a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1575873
Auto-Submit: David Benjamin <davidben@chromium.org>
Reviewed-by: Eric Roman <eroman@chromium.org>
Commit-Queue: David Benjamin <davidben@chromium.org>
Cr-Commit-Position: refs/heads/master@{#652640}

The BacktraceStorage object livespan is local to ConnectionManager::HeapProfileRetrieved
and accessed from a single thread.

BUG=923459

Change-Id: I97dfa2642d5efd06461ea69cb833d4a6aba1083d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574942
Commit-Queue: Alexei Filippov <alph@chromium.org>
Reviewed-by: Erik Chen <erikchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#652639}

Deleted in https://chromium.googlesource.com/chromium/src.git/+/ba49d00fddeb39c0816090dad7d359df0dce9a1a
Bug: 74848

Change-Id: Ia3d5c796ad34857f4e84fdb3a6f53fce3f00d63b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574829Reviewed-by: Egor Pasko <pasko@chromium.org>
Reviewed-by: Bill Budge <bbudge@chromium.org>
Commit-Queue: Anthony Steinhauser <asteinhauser@google.com>
Cr-Commit-Position: refs/heads/master@{#652638}

This code was accidentally removed in an earlier commit (*).
It seems fixed-position elements with compositing descendants
need to be promoted for the existing compositing system to work.

(*) https://chromium-review.googlesource.com/c/chromium/src/+/1407922

Bug: 950418

Change-Id: Iec04435bb1a20a17c54ce4f5ff35f4e00704e6b5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574686
Commit-Queue: Mason Freed <masonfreed@chromium.org>
Reviewed-by: Mason Freed <masonfreed@chromium.org>
Cr-Commit-Position: refs/heads/master@{#652637}

Adds minor API features and fixes some bugs in the Remote/Receiver types
to support further conversion of code away from InterfacePtr etc.

Bug: 875030
Change-Id: Ia001195c8fd0feed669d3cd65f501ace55de3015
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574896Reviewed-by: Oksana Zhuravlova <oksamyt@chromium.org>
Commit-Queue: Ken Rockot <rockot@google.com>
Cr-Commit-Position: refs/heads/master@{#652636}

This moves decoding of AV1 content via dav1d to a task pool instead of
sharing the media thread -- which was apparently leading to underflow
of the audio.

This probably only fixes pausing and audio drop outs, if a video frame
is taking more than 200ms (audio buffer size) to return, we've probably
exhausted the video frame buffer too. This would result in video
apprearing frozen for a moment, but would not trigger underflow since
we have a 3 second threshold for underflow on video.

Unlike the VP9 offloading, we offload for all resolutions of AV1
content, since we seem to be getting these issues even with 360p
content.

This removes an unnecessary BindToCurrentLoop for the OutputCB in
the non-offloaded case for clarity.

BUG=940686
TEST=all existing tests pass with offloading decoder.

Change-Id: I7426a0353249646600c12019f868aa058c40e456
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574830
Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
Auto-Submit: Dale Curtis <dalecurtis@chromium.org>
Reviewed-by: Chrome Cunningham <chcunningham@chromium.org>
Cr-Commit-Position: refs/heads/master@{#652635}

Bug: 945564,945565,945566,945567,945568,945570
Test: None
Change-Id: I49a379e125084600b85cc721d0bfaac27b1d8417
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574361Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Prashant Malani <pmalani@chromium.org>
Auto-Submit: Prashant Malani <pmalani@chromium.org>
Cr-Commit-Position: refs/heads/master@{#652634}

This is needed so Buttons can be not a subclass of MenuButton but still
install a MenuButtonController for the same behavior.

Bug: 901183, 819854
Change-Id: Iccd82dab68ba243f86a8784916332030a295b9ff
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1503349Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Michael Wasserman <msw@chromium.org>
Reviewed-by: Taylor Bergquist <tbergquist@chromium.org>
Commit-Queue: Charlene Yan <cyan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#652633}

https://skia.googlesource.com/skia.git/+log/377befab7175..ba1602896d72


git log 377befab7175..ba1602896d72 --date=short --no-merges --format='%ad %ae %s'
2019-04-19 halcanary@google.com SkQP: new docker test code
2019-04-19 ethannicholas@google.com fixed Metal code generation for recursive functions
2019-04-19 michaelludwig@google.com Don't batch across domain modes in GrTextureOp
2019-04-19 brianosman@google.com Convexity checker: Wait for significant x-product when walking edges


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

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=herb@chromium.org

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

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/40beee366962..7be19dbfabac


Created with:
  gclient setdep -r src-internal@7be19dbfabac

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=fdoray@chromium.org,bsep@chromium.org,keishi@chromium.org,chanli@chromium.org

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

- KioskEnableScreenView
- MarketingOptInScreenView
- WrongHwidScreenView
- SyncConsentScreenView

Also remove the Delegate classes on the moved views where applicable.

Bug: 928555
Change-Id: Ia833a286b49dda8af7c93f7b5aacebe239f021d6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1572539
Commit-Queue: Jacob Dufault <jdufault@chromium.org>
Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Cr-Commit-Position: refs/heads/master@{#652630}

This change allows a target process or anything outside of the context of a
source tree to request that its source tree be invalidated.

We make use of this new action in the Automation Internal browser side api, when
a client extension's automation bindings requests an enable frame. Typically,
chrome.automationInternal.enableFrame gets called whenever the extension process
encounters a new child tree. This, in turn, resets state within the tree source
and triggers a re-send of all tree data and node data on the next event.

The action is hooked up to one tree source (ARC++).

TBR=dominickn
Bug: 929522
Test: toggle on ChromeVox, interact with Play Store. Toggle off and then back on
ChromeVox, interact with Play Store. Repeat this several times. ChromeVox should
work throughout.

Change-Id: I8e2a729f079f932d06a615bb5fcca9ebbe7365f2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1573859
Commit-Queue: David Tseng <dtseng@chromium.org>
Reviewed-by: Katie Dektar <katie@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#652629}

Test is flaky on Android CFI bot.

TBR=changwan@chromium.org

Bug: 954578
Change-Id: I325856bd34a5f86c47c9370fb32f718aeb45923a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1575161Reviewed-by: Bret Sepulveda <bsep@chromium.org>
Commit-Queue: Bret Sepulveda <bsep@chromium.org>
Cr-Commit-Position: refs/heads/master@{#652628}

Work around bug b/120099466 in Android < Q in which faild reflection
causes disk reads.

BUG=948308

Change-Id: I38ab4c55a9e11f2bb2a5153740894f9f4f6c88d7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574940Reviewed-by: Matthew Jones <mdjones@chromium.org>
Commit-Queue: Paul Miller <paulmiller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#652627}

Bug: 945438
Change-Id: I314f5aecb5e12fa17fc033b51af0305c80039b47
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1568310Reviewed-by: Toni Baržić <tbarzic@chromium.org>
Reviewed-by: Aga Wronska <agawronska@chromium.org>
Commit-Queue: Michael Giuffrida <michaelpg@chromium.org>
Auto-Submit: Michael Giuffrida <michaelpg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#652626}

Change-Id: I78a34f2375794dae7aa7b6fb9f8ae0a45c193b1b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574953Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Commit-Queue: Johannes Henkel <johannes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#652625}

The prefs are all browser-settings-specific and are registered in
SettingsUI::RegisterProfilePrefs().

Bug: none
Test: compiles
Change-Id: I6fc2610b834a66f5ae502963aac19c93e19de61b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574962
Auto-Submit: James Cook <jamescook@chromium.org>
Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#652624}

Instead of using custom dir/like/things, let's use the more standard:

  ?param1=val1&param2=val2

Because it allows us to use URLSearchParams[1] in JS:

  url.searchParams.set('param1', 'val1');

And net::QueryIterator in C++:

  for (net::QueryIterator it(url); !it.IsAtEnd(); it.Advance()) {
    // use it.GetKey() and it.GetValue()
  }

R=kristipark@chromium.org
BUG=953962

[1] https://developer.mozilla.org/en-US/docs/Web/API/URLSearchParams

Change-Id: I8159e0f6d70b35bc803e9e1064c67ee27a93244b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574690
Auto-Submit: Dan Beam <dbeam@chromium.org>
Reviewed-by: Kristi Park <kristipark@chromium.org>
Commit-Queue: Dan Beam <dbeam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#652623}

https://chromium.googlesource.com/catapult.git/+log/b60ce313b947..1ff0422ebea4


git log b60ce313b947..1ff0422ebea4 --date=short --no-merges --format='%ad %ae %s'
2019-04-19 crouleau@chromium.org [Telemetry] Provide full error for metrics calculation failure.


Created with:
  gclient setdep -r src/third_party/catapult@1ff0422ebea4

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

BUG=chromium:953365
TBR=charliea@chromium.org

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

https://swiftshader.googlesource.com/SwiftShader.git/+log/97035bde89e6..c9ca99eecf1d


git log 97035bde89e6..c9ca99eecf1d --date=short --no-merges --format='%ad %ae %s'
2019-04-19 chrisforbes@google.com Fix comment describing compare/exchange behavior


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

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@chromium.org

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

With this CL, "trivial" transforms, which only produce at most a 2d
translation, will be de-composited if possible (see below). They will be
replaced by an offset that is set on the cc::Layer in
offset_to_transform_parent. With this change, the layer offset will be
stored in ForeignLayerDisplayItem, so that it can be used to update the
cc::Layer, and cc::Layer::SetOffsetToTransformParent() will be used in
many fewer cases directly.

The conditions required to de-composite a transform are:
 1. It is not the root transform node.
 2. It is a 2d translation only.
 3. The transform is not used for scrolling - its ScrollNode() is nullptr.
 4. It has no direct compositing reasons, other than k3DTransform. Note
    that if it has a k3DTransform reason, check #2 above ensures that it
    isn't really 3D.
 5. It has FlattensInheritedTransform matching that of its direct parent.
 6. It has backface visibility matching its direct parent.
 7. No clips have local_transform_space referring to this transform node.
 8. No effects have local_transform_space referring to this transform node.
 9. All child transform nodes are also able to be de-composited.


Bug: 952386,938563
Change-Id: I666e1609b48046372196c3864912a59e462bea77
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1568195
Commit-Queue: Mason Freed <masonfreed@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Auto-Submit: Mason Freed <masonfreed@chromium.org>
Cr-Commit-Position: refs/heads/master@{#652620}

This CL fixes a bug where a tinted drawable would preserve its tint
when the same drawable is used in a different dialog. This is
fixed by making the drawable mutable.

Bug: 954127
Change-Id: I66578ffc409d0e160d238b62680676a322bd8e3c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574251Reviewed-by: Theresa <twellington@chromium.org>
Commit-Queue: Sinan Sahin <sinansahin@google.com>
Cr-Commit-Position: refs/heads/master@{#652619}

This removes the confusing behavior where a user clicks a button,
expecting an action to happen, but there is no associated action so we
would instead spawn a context menu.

This now does not look like a clickable button (no hover state) and the
three-dot menu is used to access the context menu for extensions without
actions.

Bug: chromium:943702
Change-Id: I9ae6fe7d549dd2dac2d003fb6f1fecdab66e9c83
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1575859Reviewed-by: Collin Baker <collinbaker@chromium.org>
Commit-Queue: Peter Boström <pbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#652618}

Change-Id: I735de5c7f56cad4fec89dd3033ad6748a875ebee
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1575360
Commit-Queue: Piotr Bialecki <bialpio@chromium.org>
Auto-Submit: Piotr Bialecki <bialpio@chromium.org>
Reviewed-by: David Dorwin <ddorwin@chromium.org>
Reviewed-by: Bill Orr <billorr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#652617}

The default_integration policy should be used when no exp= is otherwise
specified to make sure that the GFE cache is not used.

Bug: 950734
Change-Id: I6129845bed78f84175fb440003575f626431ccbd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1560454Reviewed-by: Robert Ogden <robertogden@chromium.org>
Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Commit-Queue: Simon Pelchat <spelchat@chromium.org>
Cr-Commit-Position: refs/heads/master@{#652616}

BUG=762641
TBR=agawronska@google.com

Change-Id: I26b7b542d8172a9743da9a2fc5bf404be25f3c06
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574262Reviewed-by: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com>
Reviewed-by: Aga Wronska <agawronska@chromium.org>
Commit-Queue: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#652615}

Improve the doc comment for the GN arg "system_webview_package_name" to
mention that it controls TrichromeWebView as well as SystemWebView, and
to explain more about why you might want to use it.

Change-Id: I4c4c6e003416c9e2f39ab2492078baaa049237b6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1575732
Commit-Queue: Richard Coles <torne@chromium.org>
Reviewed-by: Nate Fischer <ntfschr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#652614}

TBR=xiyuan@chromium.org
CQ-DEPEND=CL:1570024

Bug: 952855
Change-Id: I783e41a3c810764d8118dda3643f2a1964186966
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1572405Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Roman Sorokin [CET] <rsorokin@chromium.org>
Reviewed-by: Toni Baržić <tbarzic@chromium.org>
Commit-Queue: Roman Sorokin [CET] <rsorokin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#652613}

https://boringssl.googlesource.com/boringssl/+log/4a8c05ffe826c61d50fdf13483b35097168faa5c..e55c64fdd3f47413e17eaa8e4f4d2a62622a01eb

Bug: none
Change-Id: I0f0220cfd3cd3288281d85808645eca3dc7fefb8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574296
Auto-Submit: David Benjamin <davidben@chromium.org>
Commit-Queue: Adam Langley <agl@chromium.org>
Reviewed-by: Adam Langley <agl@chromium.org>
Cr-Commit-Position: refs/heads/master@{#652612}

Bug: 953893
Change-Id: Ic30e369768a6c154209ef7fdd9b881374b3f8f30
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1572534
Commit-Queue: Brandon Wylie <wylieb@chromium.org>
Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Reviewed-by: Tommy Li <tommycli@chromium.org>
Reviewed-by: Filip Gorski <fgorski@chromium.org>
Cr-Commit-Position: refs/heads/master@{#652611}

Affects folders in the bookmark folder as well as subfolders.

We could also log this at the event source using the existing
BookmarkBar_ContextMenu_OpenAll event, but since it's a click/gesture
rather than a context menu action I created a new event type for it.

Bug: 954254
Change-Id: I4ae18d9f2dbdda5448fdc3993e06b6ef76159570
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574147
Commit-Queue: Dana Fried <dfried@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Mark Pearson <mpearson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#652610}

https://chromium.googlesource.com/angle/angle.git/+log/fcc3ec31b83b..c467f7b54188


git log fcc3ec31b83b..c467f7b54188 --date=short --no-merges --format='%ad %ae %s'
2019-04-19 spang@chromium.org Compute usage from format properties cache in glTexStorageMem2DEXT


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

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=cwallez@chromium.org

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

* Implement a MuxingSignalStrategy to be used exclusively by
  JingleSessionManager to handle messages from both signal strategies.
* Integrate all the signaling stuff into remoting_me2me_host, which can
  be enabled by passing a `--enable-ftl-signaling` flag.

This has been tested with ftl_signaling_playground and I'm able to
finish candidate exchange for ~99% of the attempt. I did see one DCHECK
failure when JingleSession receives a duplicated message, but that will
be tracked and fixed in a different bug/CL.

Bug: 947337
Change-Id: Id6a6a183041a2668a0dd31deb735b01ceb4c4aec
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1565537
Commit-Queue: Yuwei Huang <yuweih@chromium.org>
Reviewed-by: Joe Downing <joedow@chromium.org>
Cr-Commit-Position: refs/heads/master@{#652608}

TBR=xiyuan@chromium.org
TBR=rsorokin@chromium.org

Bug: 928555
Change-Id: Iae26e383c7fe81cbd5a0bf638c432bf1947f77da
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1572234
Commit-Queue: Jacob Dufault <jdufault@chromium.org>
Reviewed-by: Toni Baržić <tbarzic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#652607}