GitLab

This patch enables OOR-CORS by default, and remove virtual/outofblink-cors.

network_context_unittest changes:
 - error code for abort cases differs. Eventually we will use ERR_ABORTED,
   but for now we have a flag dependent expectation in two tests for platforms
   that does not support NetworkService, and OOR-CORS, i.e. cast_shell.

web_tests changes:
 - http/tests/devtools/console-xhr-logging.js:
   This test is affected because we are changing how CORS failures
   are reported to devtools. We accept this change.
 - http/tests/devtools/network-preflight-options.js:
 - http/tests/devtools/network/network-disable-cache-cors.js
   These tests are affected because a preflight request is not visible
   to devtools any more. It is expected, so we are deleting these tests.
 - http/tests/eventsource/eventsource-cors-non-http.html:
 - http/tests/eventsource/workers/eventsource-cors-non-http.html:
   These tests are affected because the console messages for some
   schemes are different. As the request is blocked in any case, it's
   not a problem.
 - http/tests/inspector-protocol/network-fetch-content-with-error-status-code.js:
   This test is affected because a preflight request is not visible
   to devtools any more. We accept this change.
 - http/tests/security/img-redirect-to-crossorigin-credentials.html:
   The current behavior is wrong, and OOR-CORS fixes that. See the TODO
   in the test.
 - http/tests/security/script-crossorigin-redirect-credentials.html:
   Some console messages change for tainted requests. We may change the
   messages in the future, but at this moment it is subtle enough to
   ignore.
 - http/tests/xmlhttprequest/cross-origin-unsupported-url.html:
 - http/tests/xmlhttprequest/workers/cross-origin-unsupported-url.html:
   Some line numbers are missing with OOR-CORS, because the check is
   now done asynchronously. It is not important.
 - http/tests/security/isolatedWorld/cross-origin-xhr.html
 - http/tests/xmlhttprequest/origin-whitelisting-all.html:
 - http/tests/xmlhttprequest/origin-whitelisting-exact-match.html:
 - http/tests/xmlhttprequest/origin-whitelisting-subdomains.html:
 - http/tests/xmlhttprequest/origin-whitelisting-ip-addresses.html:
   They are covered by content_browsertests.
 - mhtml/cid_in_html_resource.html:
   cid:xxxxxx is rejected because a font request is cors enabled.
 - virtual/cors-rfc1918/http/tests/security/cors-rfc1918/external-to-internal-fetch.html:
 - virtual/cors-rfc1918/http/tests/security/cors-rfc1918/external-to-internal-xhr.html:
   We are disabling these tests because they are experimental.

Cq-Include-Trybots: luci.chromium.try:linux_mojo
Change-Id: Ic7736b8e21e916269aefa734e50628bacddc5742
Bug: 905971
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1250563Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657628}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/3047a81d2430..2e5ef8795c06


Created with:
  gclient setdep -r src-internal@2e5ef8795c06

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=nhiroki@chromium.org,iclelland@chromium.org,dullweber@chromium.org,jrummell@chromium.org

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

XHR uses the same-originness of the request origin and the destination
URL to calculate the CORS-exposed header-name list, which leads to
wrong results with redirects. Use response tainting as specced.

Bug: 959390
Change-Id: Iec448dfe7d2b47d00f0f471391eb7918a1fe7bc4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1598949Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org>
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657626}

Change-Id: I9f239b73dac1b261e776de1e7030ebc07fd534bc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1600917Reviewed-by: Timothy Loh <timloh@chromium.org>
Commit-Queue: Nigel Tao <nigeltao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657625}

New interface will let configuring AGC1 and AGC2 both be done through
AudioProcessing::Config. Therefore, it would be betther to move the code
for configuring to one single function, to have a concentrated place to
hold the configuring logic.

config before/after the CL and enabled/disabled exp AGC, on desktop.

Bug: 953804
Test: Pass added unit test. Print out apm config, and see the exact same
Change-Id: If4d90902b960a23dd98333534fe0086079524d6a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1582969Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Reviewed-by: Armando Miraglia <armax@chromium.org>
Commit-Queue: Kehuang Li <kehuangli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657624}

This patch adds a new web test for up/down caret movement crossing blocks
with large margin and padding. This is preparation for implementing hit
test based up/down caret movements.

Bug: 870555
Change-Id: If35dc36cede007a7b2da58a03c24b7008a6364fc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1600952
Auto-Submit: Xiaocheng Hu <xiaochengh@chromium.org>
Commit-Queue: Yoshifumi Inoue <yosin@chromium.org>
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657623}

Decoders on some target cannot correctly decode VP8 bitstream generated by
ChromeOS intel HW encoder. This blocks to release VP8 HW encoder for other use
cases like WebRTC app. Fortunately, cast is the only path to feed VP8 bitstream
generated by ChromeOS devices to the targets. By disabling VP8 HW encoder only
for cast use case, we can release VP8 HW encoder for other use cases.

Bug: 955285, 938318
Test: None
Change-Id: Ie7e158f71313f2ef6081a1c18603e5fa66f4f2fe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1578147
Commit-Queue: Hirokazu Honda <hiroh@chromium.org>
Reviewed-by: Yuri Wiitala <miu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657622}

Simple refactoring to get rid of const scoped_refptr<>&.

BUG=946265
TEST=compile chrome

Change-Id: I3dd8d69ab33cece8c93edf2cf102b38796d12cdc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1597901Reviewed-by: John Rummell <jrummell@chromium.org>
Reviewed-by: Raymes Khoury <raymes@chromium.org>
Commit-Queue: Chih-Yu Huang <akahuang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657621}

It returned a copy of the data, not the original data, which goes wrong
when the data is written to as in
FakeKerberosClient::AcquireKerberosTgt().

BUG=chromium:952237
TEST=None

Change-Id: I0f39314d0c44e31e6586963f3d60ae439b0e062a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1590095
Commit-Queue: Lutz Justen <ljusten@chromium.org>
Reviewed-by: Dan Erat <derat@chromium.org>
Reviewed-by: Kush Sinha <sinhak@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657620}

Using wpt-import in Chromium ee1963a2.
With Chromium commits locally applied on WPT:
e28269b6 "[LayoutNG/PE] Clear visual overflow for LayoutText before setting."
aff3c8fe "Add tests for crbug.com/363609 and crbug.com/954591"
c4dc3441 "[WPT] Reland Upload a test for sending mouse events with key pressed"
fec827fb "Added wpt tests for overscroll customization."
a554ea37 "Reland "[EventTiming] Round instead of ceil the |duration|""
a06bcc90 "WebXR: Rename requestSession parameter variables to match use"
eeafcaee "[sms] Introduce testing infrastructure and handle some corner cases."
c9077e39 "Restore original tail-processing for ScriptProcessor and AudioWorklet"


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:
cbiesinger@chromium.org:
  external/wpt/css/css-flexbox

NOAUTOREVERT=true
TBR=lpz

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

R=tikuta@chromium.org, ukai@chromium.org, yyanagisawa@chromium.org

Bug: 960294
Change-Id: I21f264874f2b64267acbb8b23eb52a39958a4893
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1599812Reviewed-by: Takuto Ikuta <tikuta@chromium.org>
Commit-Queue: Simon Que <sque@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657618}

The command line --all will be used in place of --also-run-disabled-tests,
which was removed in a previous CL. This CL also refactors gpu_integration_test_unittest.py
and provides documentation for pre submit checks which look for collisions
between test expectations.

Bug: chromium:937516
Change-Id: If1c3dd820da6fc72bb837a98be5f60972de1bf31
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1600612Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657617}

And fix up existing mojom files that had CRLF line endings.

Bug: 932129
Change-Id: I83585e5f43e72ebeac1bc44a05584a9b1632524e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1600672
Auto-Submit: Marijn Kruisselbrink <mek@chromium.org>
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657616}

All planes share the modifier. Thus, it makes more sense NativePixmapHandle has
the modifier variable rather than each NativePixmapPlane.

TBR=sandersd@chromium.org, yusukes@chromium.org, dcastagna@chromium.org, dcheng@chromium.org, rjkroege@chromium.org

Bug: 957381
Test: Launch ARC++ App
Test: Play video with/without HW video decoder
Test: Record video with GCA
Change-Id: I3d21d336aae149bb5028893a7c23f21a310878ef
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1601013Reviewed-by: Hirokazu Honda <hiroh@chromium.org>
Commit-Queue: Hirokazu Honda <hiroh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657615}

https://skia.googlesource.com/skia.git/+log/51e15a69ce5b..4497ac179949


git log 51e15a69ce5b..4497ac179949 --date=short --no-merges --format='%ad %ae %s'
2019-05-08 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/swiftshader b01f2559e017..d5ed0a31ce88 (10 commits)


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

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

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

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/e5e444045846..e7f0b4c62c55


git log e5e444045846..e7f0b4c62c55 --date=short --no-merges --format='%ad %ae %s'
2019-05-08 mmoss@chromium.org Revert "git-cl: Keep git push traces"


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

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.



BUG=chromium:955206
TBR=agable@chromium.org

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

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/62d707af087a..3047a81d2430


Created with:
  gclient setdep -r src-internal@3047a81d2430

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=nhiroki@chromium.org,iclelland@chromium.org,dullweber@chromium.org,jrummell@chromium.org

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

Previously, when ChromeVox encounters a change in editable text that remains within a single line, e.g. move by one character, it would compare the plain text diffs of the previous and current lines.

This would miss the rich structure of automation including images.

The logic prior to this change would sometimes emit output accidentally when the move within line was detected as a move across lines.

This change makes it so whenever either side of the selection (while within a single line) is not on a text node, ChromeVox will describe the entire DOM selection.

Test: browser_tests --gtest_filter=ChromeVoxEditing*.*ImageByCharacter
Change-Id: I53f7d9e15edfaa13c90fb4cc498d83f140cbdf35
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1596194
Commit-Queue: David Tseng <dtseng@chromium.org>
Reviewed-by: Nektarios Paisios <nektar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657611}

This CL simplify the code.
This CL has no behavior changes.

Change-Id: Ia9f966124edeed790db2e9dfc4b6162ad66a69fb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1600734Reviewed-by: Abhijeet Kandalkar <abhijeet@igalia.com>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657610}

Previously, this code path was never executed, which is how the bug
wasn't discovered.

Bug: 829689
Change-Id: I636536914ca24ba4872c275d705c8f75f2f9b9bf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1597934
Commit-Queue: Jay Harris <harrisjay@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657609}

Bug: chromedriver:2899
Change-Id: I2643802d5b9f9a2f2e91b512414631c12521d2fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1600377Reviewed-by: John Chen <johnchen@chromium.org>
Commit-Queue: Artur Khachatryan <khachatryan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657608}

# This is an automated release commit.
# Do not revert without consulting chrome-pmo@google.com.
NOAUTOREVERT=true
TBR=benmason@chromium.org

Change-Id: Ia09502ebaca1bbdeda116acf4ac76db247a93c25
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1600389Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657607}

The Kerberos daemon exposes a D-Bus method to get the list of all
existing Kerberos accounts. This CL adds support for this method on the
Chrome side.

BUG=chromium:952237
TEST=None.

Change-Id: I28d953e926a97c4506ea8388ec13cd19b8da96f8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1588254
Commit-Queue: Lutz Justen <ljusten@chromium.org>
Reviewed-by: Dan Erat <derat@chromium.org>
Reviewed-by: A Olsen <olsen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657606}

This is in preparation of making --ignore-certificate-errors-spki-list
also ignore the SignedExchange certificate requirements.

SignedExchangeCertificateChain::ShouldIgnoreErrors() returns true iff
errors for its main certificate should be ignored.

This is pure refactoring; no behavior changes.

Bug: 956471
Change-Id: I94770fa4428e3dd560f0a126dc7e746c6716207c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1583027
Commit-Queue: Kunihiko Sakamoto <ksakamoto@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Tsuyoshi Horo <horo@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657605}

The PDF viewer is the only user of paper-fab. Changing it to use
cr-icon-button instead will allow paper-fab to be removed from the
repository.

Bug: 959483
Change-Id: Idc73f270d65b4ed25d05bdca2006f0ec4e20d455
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1586354Reviewed-by: Esmael El-Moslimany <aee@chromium.org>
Commit-Queue: Rebekah Potter <rbpotter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657604}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/75362025a46a..52e432e7d136


git log 75362025a46a..52e432e7d136 --date=short --no-merges --format='%ad %ae %s'
2019-05-08 jclinton@chromium.org README: Run mdformat on file


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

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

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

This CL adds plumbing so that clicking the Plugin VM launcher icon will
launch it once everything else is set up, although this can not yet be
triggered as we require the pref indicating installation is complete
does not yet get set.

Bug: 904853
Change-Id: Ie52c2bc58ba3801cf6df8f465f0d885d15be43df
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1594379
Commit-Queue: Timothy Loh <timloh@chromium.org>
Reviewed-by: Ryo Hashimoto <hashimoto@chromium.org>
Reviewed-by: Alex Oldemeier <aoldemeier@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657602}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/f6bb591e..c6d66c4d

Please follow these instructions for assigning/CC'ing issues:
https://v8.dev/docs/triage-issues

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com

Change-Id: I8062ca9f0050d7fafe1888278d70a1f0bd242e6c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1599311Reviewed-by: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#657601}

Bug: 88072
Change-Id: Ia11f4f6b874065319771df524e3347b3a6ea2839
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1584852Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Commit-Queue: Akihiro Ota <akihiroota@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657600}

https://swiftshader.googlesource.com/SwiftShader.git/+log/81404f2d6e94..d5ed0a31ce88


git log 81404f2d6e94..d5ed0a31ce88 --date=short --no-merges --format='%ad %ae %s'
2019-05-08 sugoi@google.com External Memory Host tests should be unsupported


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

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

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/b2db64812c02..62d707af087a


Created with:
  gclient setdep -r src-internal@62d707af087a

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=nhiroki@chromium.org,iclelland@chromium.org,dullweber@chromium.org,jrummell@chromium.org

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

The AutoRoll server is located here: https://autoroll.skia.org/r/fuchsia-sdk-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:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast
TBR=cr-fuchsia+bot@chromium.org

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

This reverts commit a4c5377b.

Reason for revert: Tests still seem flaky on Mac 10.13 bot, see
https://ci.chromium.org/p/chromium/builders/ci/Mac10.13%20Tests/13116

Original change's description:
> Extensions Web UI: Restore polyfill test
> 
> Fix the test to pass on Mac 10.13.
> 
> Bug: 925517
> Change-Id: Ifc630605dfd8de124a3d4af77d35f4374ca0c316
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1597910
> Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
> Commit-Queue: Rebekah Potter <rbpotter@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#657433}

TBR=dpapad@chromium.org,rbpotter@chromium.org

Change-Id: Ie0eb5498d810abf674bb3ea86ab10e6d4119f01a
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 925517
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1600953Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Commit-Queue: Rebekah Potter <rbpotter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657596}

This CL allows mobile clients to use FtlSignalStrategy once the FTL ID
is set.

Bug: 954594
Change-Id: I18c51391f1c767c08480414a9867746197e3a54f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1597961
Commit-Queue: Joe Downing <joedow@chromium.org>
Reviewed-by: Joe Downing <joedow@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657595}

The 'title' for each SW section at Application>Service Worker is the
scope URL, and scopes are sensitive to port numbers.

Bug: 601286
Change-Id: Ib718652a9132dc17ef5adfc4828f0c43e439d1c2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1595124Reviewed-by: Erik Luo <luoe@chromium.org>
Commit-Queue: Haihong Li (Harley) <hhli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657594}

1. Changes the Cursor class in ChromeVox to allow tree positions on richly editable nodes
Due to bugs in the old selection code in Blink, a ChromeVox Cursor
could not be set on a content editable root or any of its descendant nodes, other
than a text node.
The new selection code does return selection endpoints that are tree positions on
richly editable nodes, and so ChromeVox should both handle as well as set such endpoints.

2. Completely eliminates the use of anchor and focus objects in ChromeVox editing handler.
This patch uses the newly added attributes selectionStart/End which are
guaranteed to be in document order.
To determine if selection has been altered from the start vs. the end, which is
important for determining what needs to be spoken or brailled,
this patch relies on a boolean "isSelectionBackward" that is sent
directly from Blink, instead of relying on checking which endpoint has been modified.
3. Modifies Select to Speak based on a patch provided by katie@
and augmented by me.
Uses "isSelectionBackward" to switch anchor and focus around so that they will always
be in document order.

R=dmazzoni@chromium.org, dtseng@chromium.org

Bug: 639340
Change-Id: I072f9c9dfff5b6c9a107e66207fb9cc80f8d4cad
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1572523
Commit-Queue: Nektarios Paisios <nektar@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Katie Dektar <katie@chromium.org>
Reviewed-by: Ben Wells <benwells@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Reviewed-by: David Tseng <dtseng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657593}

This CL implements a MessageTracker that tracks message IDs and makes
FtlmessagingClient drop messages with duplicated IDs.

Bug: 952376
Change-Id: I3b03be0953a1178128835fba96c9ac139db5cb77
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1595426
Commit-Queue: Joe Downing <joedow@chromium.org>
Reviewed-by: Joe Downing <joedow@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657592}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/a41b430df52b..75362025a46a


git log a41b430df52b..75362025a46a --date=short --no-merges --format='%ad %ae %s'
2019-05-08 gbiv@google.com afdo: format sources


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

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

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

This metric is to measure the time spent for looking up a matching registration.
Perhaps this is mostly measuring the time for disk access to read registration
info. We want to analyze this to see if putting registration in memory could
improve performance.

Bug: 953598
Change-Id: Icef0444ccec3ae3701073ff96afb0d8b3769e6f8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1583177
Commit-Queue: Makoto Shimazu <shimazu@chromium.org>
Reviewed-by: Jesse Doherty <jwd@chromium.org>
Reviewed-by: Kenichi Ishibashi <bashi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657590}

This is a future proofing bug fix. BookmarkAppRegistrar was not filtering
its extensions for only bookmark app extensions and would fire for any
extension install.

This wasn't an issue because the only listener at the moment
(WebAppTabHelperBase::OnWebAppInstalled) already filters to PWAs only via
FindAppIdInScopeOfUrl().

This change ensures we don't over signal for any future listeners.

Bug: 891172
Change-Id: Id8bcf275326a03819658eca8d36d5cbffec2ba5a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1600534
Commit-Queue: Alan Cutter <alancutter@chromium.org>
Auto-Submit: Alan Cutter <alancutter@chromium.org>
Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657589}