GitLab

URLs like `https://whatever.com:0/` have an opaque origin, as they're
rejected in the SchemeHostPort constructor (see [1] and [2]). This
means that they fail the `IsOriginSecure()` check, and crash the
renderer, which is a bit unfortunate, as they're going to fail to load
regardless.

This patch excludes URLs with opaque origins from the referrer check in
order to avoid that crash.

[1]: https://cs.chromium.org/chromium/src/url/scheme_host_port.h?rcl=90e84c7240870d52c224cb8c07b52545a2ef7cef&l=83
[2]: https://cs.chromium.org/chromium/src/url/scheme_host_port.cc?rcl=90e84c7240870d52c224cb8c07b52545a2ef7cef&l=85

Bug: 960312
Change-Id: I39a41e3148554fda36e52d1f0c9934f52a2b8dff
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1771906
Commit-Queue: Mike West <mkwst@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#691093}

The promise resolution was already wrapped in calling it inside the
right execution context, but the reject was not. Add the correct
execution context and schedule rejecting the promise if font loading for
a local() font fails when it is triggered by an implicit UA-triggered
load.

Spec reference:
https://drafts.csswg.org/css-font-loading/#font-face-load
in particular the last normative paragraph: "User agents can initiate
font loads on their own, whenever they determine that a given font face
is necessary to render something on the page. When this happens, they
must act as if they had called the corresponding FontFace’s load()
method described here."

Thanks to Roel Nieskens (pixelambacht@) for the helpful bug report and
reproduction test case.

Bug: 996687
Change-Id: Icb5d75675b8a2e0b3f100808645a1e2e550cfcd1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1771607
Commit-Queue: Dominik Röttsches <drott@chromium.org>
Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#691092}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/7096a4a9fc5b..0f0281d3e2a8


Created with:
  gclient setdep -r src-internal@0f0281d3e2a8

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll
Please CC jbudorick@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome
TBR=jbudorick@google.com

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

This patch adds logging for the dropped invalidations in Sync browser
tests. This will help investigate some flaky tests.

Invalidation are dropped if they are received before an
FCMNetworkHandler is actually assigned and listening for FCM messages.


Change-Id: I10409bfdda7b0616da6e45a6ecd5f00b3cd5bef0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1771904
Commit-Queue: Mohamed Amir Yosef <mamir@chromium.org>
Reviewed-by: Marc Treib <treib@chromium.org>
Reviewed-by: Jan Krcal <jkrcal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#691090}

A crash can sometimes happen when there the base and extent are
equal and there are no valid nodes going rightward. This fixes it
so in this situation it should have the selection on the same
leftward node.

Bug: 989162
Bug: 987702
Change-Id: I10a05125367f561ed5b4ba2b3d533907caf8b7ba
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1760303Reviewed-by: Alice Boxhall <aboxhall@chromium.org>
Commit-Queue: Jessica Tallon <jtallon@igalia.com>
Cr-Commit-Position: refs/heads/master@{#691089}

ScheduledAction::Execute is only ever called by DOMTimer::Fired which is called as a task. So the stack is simple and we should be able to add AllowedStackScope and allow cooperative scheduling.

Bug: 804661
Change-Id: Ida6d3605810469d0e95b6e72ded3f1aed05ad341
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1743236
Commit-Queue: Keishi Hattori <keishi@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#691088}

Move the logic of calculating delay for the next background
sync event to the chrome layer. This CL moves the logic to
apply cross-registration limits for the same origin to
BackgroundSyncController in the chrome layer.

It also moves a unit test to this layer, and adds additional
unit tests to BackgroundSyncController.

Bug: 949499
Change-Id: I26bdd63d376c5b0821d62ccb7293833fbadaa444
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1751250
Commit-Queue: Mugdha Lakhani <nator@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Rayan Kanso <rayankans@chromium.org>
Auto-Submit: Mugdha Lakhani <nator@chromium.org>
Cr-Commit-Position: refs/heads/master@{#691087}

Intended to enable landing of
https://webrtc-review.googlesource.com/c/src/+/53861

Bug: webrtc:8733
Change-Id: Ia0b946c51215fc7ce6f7f27541d1e788cda1a843
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1768587Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Commit-Queue: Niels Möller <nisse@chromium.org>
Cr-Commit-Position: refs/heads/master@{#691086}

Using wpt-import in Chromium 23bae0af.
With Chromium commits locally applied on WPT:
1194775a "Add ability to block same-origin access via document-access feature policy"
5546163a "Temporarily send `Sec-Fetch-*` headers via non-secure transport."
d3b97055 "Update simulateUserActivation to match webxr-test-api spec"
2d090a27 "[WPT/referrer-policy] Call getRequestURLs() for each subtest"
90789f54 "Implement fallback to element anchor"


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

NOAUTOREVERT=true
TBR=robertma

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

Update callsites.

Change-Id: I2ebaf88c479c0a8c20953f77fae00cdb77835fee
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1769212
Commit-Queue: Mike Reed <reed@google.com>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Florin Malita <fmalita@chromium.org>
Cr-Commit-Position: refs/heads/master@{#691084}

This CL adds test cases for a conversion from Dmabuf frame to Dmabuf frame. The
test cases are currently for ImageProcessor using VA-API, which will be
introduced in crrev.com/c/1367389. The ImageProcessor only supports a conversion
between Dmabuf frames.

Bug: 898423, 917951
Test: image_processor_tests on atlas
Change-Id: I69460be06c7c5a5cd5827b09f4a62d67e9148a52
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1772926
Commit-Queue: Hirokazu Honda <hiroh@chromium.org>
Reviewed-by: David Staessens <dstaessens@chromium.org>
Cr-Commit-Position: refs/heads/master@{#691083}

There are still some parts of the code that are un-tested, particularly concerning additional actions and T&C links.

Bug: b/140018932
Change-Id: Iea4a4f92dbb6f118c01e1fab1839721ebac76082
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1769447
Commit-Queue: Clemens Arbesser <arbesser@google.com>
Reviewed-by: Mathias Carlen <mcarlen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#691082}

It used to use runtimeStatsMetric but this seems broken, so move to
runtimeStatsTotalMetric instead.

Perf Sheriffs: This is expected to change all the metrics on
v8.runtime_stats.top_25 due to the change in measurements.

BUG=chromium:688342

Change-Id: I3e185fa9086e69151f4c5fa2db5fbf3d326d93fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1771611Reviewed-by: Juan Antonio Navarro Pérez <perezju@chromium.org>
Reviewed-by: Ulan Degenbaev <ulan@chromium.org>
Commit-Queue: Ross McIlroy <rmcilroy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#691081}

This patch changes |LayoutText::SetTextWithOffset()| to reduce text shaping by
reusing |ShapeResult| of before and after replaced range for improving
performance, 10% to 15% faster but 3 times slower than legacy layout.
(Profile data: http://bit.ly/33B9rfg)

From this patch, |SetTextWithOffset()| does:
 1. Get offset mapping to map DOM offsets to text content offsets for replaced
  range.
 2. Collect inlines into |text_content| and |NGInlineItem| to get newly inserted
  text.
 3. Copy before and after |ShapeResult| from current data to |NGInlineItem| list
  in step 2.
 4. Call |NGInlineNode::ShapeText()| with |NGInlineItem| list to reuse
  |ShapeResult|.

This patch gets rid of NGInlineNodeTest.InvalidateSetTextWithOffset because
new test case replaces this test and this test call |SetTextWithOffset()| with
wrong parameter. It shoulbe |SetTextWithOffset("baftere", 1, 4)| as result of
|"before".replaceData(1, 4, "after")|.

Bug: 707656
Change-Id: I078b19615d6f7e31362c1e6398aac88fb17b29c1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1729330
Commit-Queue: Yoshifumi Inoue <yosin@chromium.org>
Auto-Submit: Yoshifumi Inoue <yosin@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#691080}

The macro EXPECT_EQ_UNIQUE_ID() has been defined in a way that expects
variables with exact names `expected' and `actual' defined in a dynamic
scope, i.e. in the scope of C++ code that actually uses either
EXPECT_EQ_UNIQUE_ID() or EXPECT_FORM_FIELD_DATA_EQUALS() macros.

It seems the original intent was to use argument expressions passed to
EXPECT_FORM_FIELD_DATA_EQUALS(), not necessarily bound to exact names.

BUG=896689

Change-Id: I4f782afc1c8ab7c55b77ee111dcbbe64002a4d6b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1757823
Auto-Submit: Andrei Polushin <anpol@yandex-team.ru>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Dominic Battré <battre@chromium.org>
Commit-Queue: Dominic Battré <battre@chromium.org>
Cr-Commit-Position: refs/heads/master@{#691079}

Fix the code in results_processor that detects whether output options
should be processed or not.

Add a test in scripts_smoke_test to make sure the "run_benchmark list"
command is kept working.

And add more tests on the current behaviour for output option
processing. These would have avoided crbug.com/997284.

Bug: 996493
Change-Id: I1476a32eb3b48b7c1ebbaae60b47dba9b17ca23c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1771603
Commit-Queue: Juan Antonio Navarro Pérez <perezju@chromium.org>
Reviewed-by: Caleb Rouleau <crouleau@chromium.org>
Cr-Commit-Position: refs/heads/master@{#691078}

Not taking the new woff2 support right now, since Chromium already has
woff2 support (which already depends on brotli) and Chromium needs to
roll FreeType past this commit while evaluating what to do.

https://chromium.googlesource.com/chromium/src/third_party/freetype2.git/+log/9adc3b35f1a6..cbee985a2bc1

git log 9adc3b35f1a6..cbee985a2bc1 --date=short --no-merges --format='%ad %ae %s'
2019-08-27 drott@chromium.org [woff2] Don't use `FT_UInt64' (#56815).
2019-08-27 wl@gnu.org [truetype] Prevent crash in `TT_Set_Named_Instance' (#56813).
2019-08-27 wl@gnu.org CHANGES: Updated.
2019-08-27 wl@gnu.org [woff2] Fix compiler warnings.
2019-08-27 wl@gnu.org [woff2] Formatting; some comments.
2019-08-27 ramakrishnan.nikhil@gmail.com [woff2] Check whether known tag is in array bounds.
2019-08-27 ramakrishnan.nikhil@gmail.com [woff2] More formatting and documentation.
2019-08-27 ramakrishnan.nikhil@gmail.com * src/sfnt/sfwoff2.c: Improve trace comments.
2019-08-27 ramakrishnan.nikhil@gmail.com [woff2] Formatting.
2019-08-27 ramakrishnan.nikhil@gmail.com [woff2] Support `hmtx' reconstruction when `glyf' is untransformed.
2019-08-27 ramakrishnan.nikhil@gmail.com [sfnt] Support `face->num_faces' for WOFF2 fonts.
2019-08-27 ramakrishnan.nikhil@gmail.com [woff2] Improve memory and error handling.
2019-08-27 ramakrishnan.nikhil@gmail.com [woff2] Avoid too many calls to `FT_REALLOC'.
2019-08-27 ramakrishnan.nikhil@gmail.com [woff2] Reconstruct `loca', `hmtx', and swap out stream.
2019-08-27 ramakrishnan.nikhil@gmail.com [woff2] Reconstruct transformed `glyf' table.
2019-08-27 ramakrishnan.nikhil@gmail.com [woff2] Copy un-transformed tables to sfnt stream.
2019-08-27 ramakrishnan.nikhil@gmail.com [woff2] Create stream for uncompressed buffer.
2019-08-27 ramakrishnan.nikhil@gmail.com [woff2] Handle TTCs and start reconstructing font.
2019-08-27 ramakrishnan.nikhil@gmail.com [woff2] Get known tags from function.
2019-08-27 ramakrishnan.nikhil@gmail.com [woff2] Minor.
2019-08-27 ramakrishnan.nikhil@gmail.com [woff2] Uncompress Brotli streams and `face_index' support.
2019-08-27 ramakrishnan.nikhil@gmail.com * builds/unix/configure.raw: Change argument name to `brotli'.
2019-08-27 ramakrishnan.nikhil@gmail.com Add Brotli dependency and required checks.
2019-08-27 ramakrishnan.nikhil@gmail.com [woff2] Write SFNT Offset table.
2019-08-27 ramakrishnan.nikhil@gmail.com * src/sfnt/sfwoff2.c: #undef macros.
2019-08-27 ramakrishnan.nikhil@gmail.com [woff2] Read table and collection directory.
2019-08-27 ramakrishnan.nikhil@gmail.com [sfnt] Include `woff2tags.c' for building.
2019-08-27 ramakrishnan.nikhil@gmail.com [sfnt] Add WOFF2 constants.
2019-08-27 ramakrishnan.nikhil@gmail.com [sfnt] Read WOFF 2 header.
2019-08-27 ramakrishnan.nikhil@gmail.com Add structures for WOFF2.

Created with:
  gclient setdep -r src/third_party/freetype/src@cbee985a2bc1

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/freetype-chromium
Please CC bungeman@google.com,drott@google.com,thestig@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_chromium_msan_rel_ng;luci.chromium.try:linux-blink-rel;luci.chromium.try:mac10.12-blink-rel;luci.chromium.try:mac10.13_retina-blink-rel;luci.chromium.try:win10-blink-rel;luci.chromium.try:win7-blink-rel
Bug: 998083
TBR=bungeman@google.com,drott@google.com,thestig@google.com

Change-Id: Ia8406de15aeb9b5593c9e1f8ae579fe2baf8bf9b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1773439
Commit-Queue: Dominik Röttsches <drott@chromium.org>
Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#691077}

Bug: 978136
Change-Id: Id7026f3132f38398f1a0e9fc8cf2413a30095979
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1771402Reviewed-by: Aaron Leventhal <aleventhal@chromium.org>
Commit-Queue: Jessica Tallon <jtallon@igalia.com>
Cr-Commit-Position: refs/heads/master@{#691076}

Because of the typo, not only the test name is wrong but also it actually tests
conversion from memory based frame to dmabuf based one. This CL fixes the typo
and begins to test a conversion from dmabuf based frame to memory based frame.
This also renames ImageProcessorSimpleParamTest to ImageProcessorParamTest as
the "Simple" is unnecessary.

Bug: 917951
Test: image_processor_test on atlas
Change-Id: I1ec4f1d8cac776292aef4f8e07b7d7999a81fba4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1773076
Commit-Queue: Hirokazu Honda <hiroh@chromium.org>
Reviewed-by: David Staessens <dstaessens@chromium.org>
Cr-Commit-Position: refs/heads/master@{#691075}

Fixes flakiness in unit testing due to DWriteFontLookupTableBuilder
spuriously trying to index fonts when it should not.

In order to test DWriteFontLookupTableBuilder a cache directory is
configured for persisting the built table. The same happens when a full
browser runs with a profile - in which case a subdirectory of the
USER_DATA directory is used. Do not scan fonts if a directory is not
configured.

This situation happens in unit tests in tests other than the
DWriteFontLookupTableBuilder unit tests, as ContentClient and
BrowserClient do not return a path for GetFontLookupTableCacheDir() in
testing. It is sufficient to test DWriteFontLookupTableBuilder in its
own unittests. If local unique font matching on Windows 7 is required in
a unit test, a cache directory can be configured using
DWriteFontLookupTableBuilder::GetInstance()->
    SetCacheDirectoryForTesting(...)

Thanks to etienneb@ for spotting this problem and initial fix proposals.

Bug: 996167
Change-Id: Iccac27225d7be7fc464a645e7e7689eba3680efa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1769437Reviewed-by: Etienne Bergeron <etienneb@chromium.org>
Commit-Queue: Dominik Röttsches <drott@chromium.org>
Auto-Submit: Dominik Röttsches <drott@chromium.org>
Cr-Commit-Position: refs/heads/master@{#691074}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/7d2e5f8ebe67..7096a4a9fc5b


Created with:
  gclient setdep -r src-internal@7096a4a9fc5b

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll
Please CC jbudorick@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome
TBR=jbudorick@google.com

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

Because we're using mojo data pipe, which has own quota control,
to transfer received data, we don't have manual one, or
mojom::WebSocket.AddReceiveFlowControlQuota().
This CL does a sort of work removing the function.

mojom::WebSocket.AddReceiveFlowControlQuota(quota) did 5 tasks:
browser side(mainly on WebSocketChannel)
 1. Trigger the first ReadFrame if renderer gets not throttled.
For #1, this patch moves the trigger to mojo WebSocket.StartReceiving.

 2. Trigger next ReadFrame if there is enough quota.
 3. Send pending dataframes based on added quota.
This patch moves task #2 and #3 to websocket.cc and datapipe itself.

 4. Dropchannel if all pending frames are received by renderer when closed.
Because we can care #4 w/o renderer ping back, this patch move
RespondToClosingHandshake()to WebSocketChannel::ReadFrames().

renderer side(mainly on WebSocketChannelImpl)
 5. Ping browser that backpressure is turned off.
For task #5, this patch changes not to call the mojo but throttle
datapipe reading with WebSocketHandleImpl::ConsumePendingDataFrames().

receive-arraybuffer-1MBx100.htmll?iteration=100 measurement on local build:
ToT:            144 MB/s (stdev: 4.56 MB/s)
Patch:          208 MB/s (stdev: 6.15 MB/s)
  (+44% to ToT, +41% to ReadOnlyBuffer)
ReadOnlyBuffer: 147 MB/s

Change-Id: I61feab06f0e3719520e6a47eea61e0322e4da01f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1763507
Commit-Queue: Yoichi Osato <yoichio@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Karan Bhatia <karandeepb@chromium.org>
Reviewed-by: Adam Rice <ricea@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#691072}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/568f3984..d190ff4e

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

The chip view needs to react to certain state changes with changed text
colors. Since the secondary label is added lazily, it needs to check for
these states explicitly.

Once views that are part of the hierarchy they will receive most of the
state changes (e.g. a setSelected on ChipView will apply to both
TextViews).
For some reason, setEnabled wasn't applied to children by default but it
is strictly necessary in order to automatically select the correct text
appearance.

Additional fix: ensure there is an appropriate disabled state color.
Screenshots are in the linked bug.

Bug: 989960
Change-Id: Ic63d09f22c22af485d060d03d6ba6c20ef233bf1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1771613
Commit-Queue: Friedrich [CET] <fhorschig@chromium.org>
Reviewed-by: Theresa  <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#691070}

Bug: 244755
Change-Id: Ib1ecb888e82d99393cd15d867cae7c0f0d7ca9a2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1769446Reviewed-by: Max Moroz <mmoroz@chromium.org>
Commit-Queue: Michael Starzinger <mstarzinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#691069}

TBR=meacer@chromium.org

Change-Id: Ifd4d32cefcc3e3c98720d20a3227a1d42af403b5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1774262
Commit-Queue: Krishna Govind <govind@chromium.org>
Reviewed-by: Krishna Govind <govind@chromium.org>
Cr-Commit-Position: refs/heads/master@{#691068}

We now first strip the path data and then check if it's an
empty string. This allows white space at the end of the
string. This follows the spec.
https://www.w3.org/TR/SVG11/animate.html#ValuesAttribute

Bug: 429301
Change-Id: Ie77731cb0ec17b489b439953e73230650a16bcd9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1768771Reviewed-by: Fredrik Söderquist <fs@opera.com>
Commit-Queue: Edvard Thörnros <edvardt@opera.com>
Auto-Submit: Edvard Thörnros <edvardt@opera.com>
Cr-Commit-Position: refs/heads/master@{#691067}

https://swiftshader.googlesource.com/SwiftShader.git/+log/a9da772f0587..04e148570dbb

git log a9da772f0587..04e148570dbb --date=short --no-merges --format='%ad %ae %s'
2019-08-28 capn@google.com Make round-robin task enqueue index thread safe
2019-08-27 bclayton@google.com Device: Migrate Renderer to Yarn
2019-08-27 bclayton@google.com Device: Don't use a global for the cluster count.
2019-08-27 bclayton@google.com Some minor code tidying.
2019-08-27 bclayton@google.com Pipeline: Use Yarn to make compute multi-threaded.
2019-08-27 bclayton@google.com Vulkan: Build a yarn::Scheduler and pass it down to the vk::Queue.
2019-08-27 bclayton@google.com vk::Queue: Lazily construct Renderers
2019-08-27 bclayton@google.com Yarn: Don't zero-initialize data in Pool<T>::Item::construct()

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

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/swiftshader-chromium-autoroll
Please CC swiftshader-team+autoroll@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

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

Bug: chromium:b/139010488,chromium:b/139142453,chromium:b/139142453,chromium:b/139142453,chromium:b/139142453,chromium:b/139010488,chromium:b/139142453
Change-Id: Iceb60a95f44801f390732a1506641ace01c4e131
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1774264Reviewed-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@{#691066}

Bug: chromium:997148
Change-Id: I1d02c0b9d8ba61f0f99457b87b5e65c0efafaad8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1768637Reviewed-by: Robert Sesek <rsesek@chromium.org>
Reviewed-by: Sylvain Defresne <sdefresne@chromium.org>
Reviewed-by: Ken Rockot <rockot@google.com>
Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Niels Möller <nisse@chromium.org>
Cr-Commit-Position: refs/heads/master@{#691065}

BUG: The problem was that when the content was entirely contained with
the bounds, VisiblilityManager.#findElementBounds would return
EMPTY_ELEMENT_BOUNDS (because neither the low nor high bounds
intersected the content).

FIX: Change the logic so that when any of the content is within the
bounds we return a pair of low/high elements, snapping to the
lowest/highest when the content doesn't is too small to reach the bound.

Re-enabled the failing part.html test.

Bug: 998356
Change-Id: I60c4f0a4e49bf9aca0d1671b61d35c1dd1da5922
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1772785Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Fergal Daly <fergal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#691064}

TBR=engedy

No-Presubmit: True
No-Try: True
Bug: 998405
Change-Id: I48efc4b83b9f525f641d4f290930c206c58fca89
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1772787Reviewed-by: Darren Shen <shend@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#691063}

This CL fixes a known race condition. It can happen when eviction and
unfreezing happen at the same time.

The race condition can be resolved by reloading the page from the browser
side when the page being unfrozen is not in the back-forward cache.

This solution is not perfect since the user would see a flashing screen
when the page is reloaded. This solution is temporary for experiments.

Design Doc:
https://docs.google.com/document/d/1E6efB594SqODZX5_PRxmv8eZ9YsmheqhKFg3KoDh3vs/edit?usp=sharing

Bug: 980111, 989392
Change-Id: I8f3f85c8d6c87b0f071c4e8f821460cda25bff06
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1687878
Commit-Queue: Hajime Hoshi <hajimehoshi@chromium.org>
Reviewed-by: Lowell Manners <lowell@chromium.org>
Reviewed-by: Nasko Oskov <nasko@chromium.org>
Reviewed-by: Alexander Timin <altimin@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#691062}

This CL adds additional devices to the import mode blacklist used by the
video_decode_accelerator(_perf)_tests. The blacklist makes sure all tests are
run in allocate mode for devices not supporting import mode. The blacklist is
expanded with buddy, guado and rikku.

These devices support import mode for h264 and VP9, in which case the Vaapi is
used. But when decoding a VP8 video V4L2 is used, and only allocate mode is
supported.

TEST=./video_decode_accelerator_tests test-25fps.vp8 on rikku

BUG=chromium:988916

Change-Id: I5e60221b42d4746816665cb87ba8a8190942c9c3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1772902
Commit-Queue: David Staessens <dstaessens@chromium.org>
Reviewed-by: Hirokazu Honda <hiroh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#691061}

TBR=mlamouri@chromium.org

Bug: 520736
Change-Id: I0cb62d0313926cea9728896123b35bb0c52d2cbc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1773006Reviewed-by: Darren Shen <shend@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#691060}

https://chromium.googlesource.com/catapult.git/+log/c9fdf2610a1d..b6bdad04c621

git log c9fdf2610a1d..b6bdad04c621 --date=short --no-merges --format='%ad %ae %s'
2019-08-28 rmhasan@google.com [Telemetry] Avoid searching for actual browsers in browser test case unit tests

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

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/catapult-autoroll
Please CC oysteine@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

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

Bug: chromium:992260
Change-Id: Ia299609d6ff2f108f14316ebe596051fc0455858
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1774251Reviewed-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@{#691059}

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll
Please CC cr-fuchsia+bot@chromium.org on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

CQ_INCLUDE_TRYBOTS=luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast
TBR=cr-fuchsia+bot@chromium.org

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

It was already disabled for flakiness on Mac and Windows.

TBR=kelvinjiang@chromium.org

Bug: 299393
Change-Id: I2d888b18a24b361891cc6789ca3230c71b9308f8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1772784Reviewed-by: Darren Shen <shend@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#691057}

This CL reduces estimated pre-processed size of animatable.h
from 3.52MB to 1.97MB.

This CL avoids unnecessary copy of a
UnrestrictedDoubleOrKeyframeAnimationOptions object on animate().

Bug: 242216
Change-Id: I066c1b6e92a0fbbdd1ee141403d134a97258978b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1774001
Commit-Queue: Kent Tamura <tkent@chromium.org>
Reviewed-by: Takuto Ikuta <tikuta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#691056}

This CL converts TrustedURLLoaderHeaderClientRequest,
TrustedURLLoaderHeaderClientPtrInfo and
TrustedURLLoaderHeaderClientPtr to new Mojo types.

Bug: 955171, 978694
Change-Id: I282ceb552522adc42e8b03d64d26b1bf1c2dd5be
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1768841
Commit-Queue: Julie Kim <jkim@igalia.com>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Bo <boliu@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Ken Rockot <rockot@google.com>
Cr-Commit-Position: refs/heads/master@{#691055}

https://skia.googlesource.com/skia.git/+log/e36b85f34d27..cd3216543d0a

git log e36b85f34d27..cd3216543d0a --date=short --no-merges --format='%ad %ae %s'
2019-08-28 skia-recreate-skps@skia-swarming-bots.iam.gserviceaccount.com Update Go deps
2019-08-28 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/angle2 57ad1e1287dd..886698bc3fdd (7 commits)
2019-08-28 skia-autoroll@skia-public.iam.gserviceaccount.com Roll ../src 31c682b2..c96d445d (397 commits)

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

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/skia-autoroll
Please CC stani@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

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

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