GitLab

Some Tast Tests need to know whether Chrome animation is running or not
because, for example, Chrome animation is applied to PIP windows when
they are moved or resized, but currently there's no way to tell if
when it's done completely.

In case we need more information in the future, this CL adds an API
that queries "window information", instead of adding more specific
APIs such as getWindowAnimationState or getWindowBounds.

BUG=b:131248000
BUG=b:135956156
BUG=b:135160409
TEST=tast -verbose dut my_crbook arc.PIP

Change-Id: Idb0cdba9110127c3b24736d18b326963b929f25b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1728513
Auto-Submit: Kazuki Takise <takise@chromium.org>
Commit-Queue: Kazuki Takise <takise@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Achuith Bhandarkar <achuith@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686692}

This CL converts implementations of idle_manager.mojom
both the browser process(IdleMonitor) and the renderer process
(IdleDetector) in idle_manager.mojom.

 - Change mojo::Binding with mojo::Receiver
 - Change IdleManagerPtr with mojo::Remote<IdleManager>

Bug: 955171
Change-Id: I5e5b33cef0ee01b86e44e0778dbb2cd5ab9ac45d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1750508
Commit-Queue: Gyuyoung Kim <gyuyoung@igalia.com>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Ken Rockot <rockot@google.com>
Cr-Commit-Position: refs/heads/master@{#686691}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/979fa780ce2f..9185e4495d6d

git log 979fa780ce2f..9185e4495d6d --date=short --no-merges --format='%ad %ae %s'
2019-08-13 ehmaldonado@chromium.org depot_tools: Make scm Python 3 compatible.

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

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

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

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


TBR=agable@chromium.org

Bug: chromium:984182
Change-Id: I3ded0e71c4bd7105874556e8b74b8138cc72761b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1753099Reviewed-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@{#686690}

The internal finch analysis checks that the field trial config exactly
matches the beta/stable experimental group including disabled features.

Bug: 892874
Change-Id: I46bba1b6eb75dd741e0bdcc299e6073ae092e912
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1752111
Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org>
Commit-Queue: Ilya Sherman <isherman@chromium.org>
Auto-Submit: Sunny Sachanandani <sunnyps@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686689}

Adds "contain: style layout size" presentational hint
(https://html.spec.whatwg.org/multipage/rendering.html#the-css-user-agent-style-sheet-and-presentational-hints)
when the rendersubtree attribute is present on an element.

This means any element with the rendersubtree attribute
will get style, layout, and size containment, unless it's
overridden by author style.

This CL also removes "contain: style layout;" from
display locking WPTs as they're not needed anymore.

Not implemented in this CL:
- Handling of elements whose containment is overridden
and thus not efficiently lockable. Non-contained
locking will be implemented in another CL.

See discussion:
https://github.com/WICG/display-locking/issues/62#issuecomment-516631887

Bug: 991095
Change-Id: I14e1fa2fe45d072ec7b251423014d7ec6ab06f5b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1746112
Commit-Queue: Rakina Zata Amni <rakina@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686688}

The library uses some static variables and singleton classes. Since this
is included by a lot of other components, this should be a shared
library.

BUG=942761

Change-Id: I3a94b31fad3f3b8e4784651b34757d83af141b0c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1752872
Commit-Queue: ssid <ssid@chromium.org>
Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686687}

Failing on Mac waterfall, suspecting:
https://chromium-review.googlesource.com/c/chromium/src/+/1749135

This test uses setTimeout(..., 500) which should be fixed.

TBR: tonikitoo@igalia.com
Bug: 993328
Change-Id: I1909991c4e7df4ca75c4b02ef1fc9b917b27b4db
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1752566Reviewed-by: Alan Cutter <alancutter@chromium.org>
Reviewed-by: Antonio Gomes <tonikitoo@igalia.com>
Commit-Queue: Alan Cutter <alancutter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686686}

Using wpt-import in Chromium e82443a8.
With Chromium commits locally applied on WPT:
329c91e5 "Attempt to make test more stable"


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

This CL adds a switch to use libvpx for opaque (no alpha transparency)
VP8. There is no change to the default behavior (using ffmpeg). The
switch will be toggled via finch to compare the performance libvpx and
ffvp8.

Switching to libvpx would workaround a bug we're hitting decoding
vp8 streams from intel hw encoders (bug believed to be in ffmpeg, filed
https://trac.ffmpeg.org/ticket/8069). FFvp8 has better performance
than libvpx, but these gains may not matter on modern systems. Vp8 is
also very uncommon and generally low-resolution on today's web.

FFmpeg and libVPX have different behaviors around mid-stream frame-size
changes. LibVPX simply trusts the container metadata and we scale any
deviation from that is simply scaled. This is also true for hardware
decoders (for other codecs) and VP9 (which already uses libvpx). In
contrast, FFmpeg trusts the frames themselves and changes the size of
the video dynamically. This motivated a re-write of the
video-frame-size-change.html, which is focused on rendered size
changes rather than nuance of a specific codec. Folks desiring a size
change should use MSE to append a new init segment to explicitly signal
the new size. Given very limited use of VP8 today, we expect this
does not break folks (and hope the finch experiment will confirm that).

(https://simpl.info/videoalpha/)

Bug: 992235, 963740, b:138840822
Test: media_unittests and manually verified alpha still works with vpx
Change-Id: I48cec468946eb5a769fb2966da6b92ba28b43d8b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1745711
Commit-Queue: Chrome Cunningham <chcunningham@chromium.org>
Reviewed-by: Dan Sanders <sandersd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686684}

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

Change-Id: Id6210ee797928b79e6fd3a64b94f6e48fa00b37e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1753582Reviewed-by: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#686683}

This change will make it easier for screen reader users to select the JavaScript Context
in the Console and the audio context in the Web Audio tool by moving focus to the menu on
activation and reading the selected position of the item.

Summary of changes:
- Decorated markup with appropriate ARIA properties.
- Moved focus from button to menu following active-descendant pattern [1].
- Dropdown selection is now only finalized by clicking an item, or pressing Enter, Space, or Tab.

Scope of impact:
The SoftDropDown is currently used as the JavaScript context selector in
the Console tool and audio context in the Web Audio tool.

[1] https://w3c.github.io/aria-practices/examples/menu-button/menu-button-actions-active-descendant.html
[2] https://cs.chromium.org/search/?q=UI.SoftDropDown+-f:out+f:.js+f:front_end&sq=package:chromium&type=cs

Screenshot: https://i.imgur.com/jIpsRYP.png
Gif: https://i.imgur.com/V4FoqKn.gifv

Bug: 963183
Change-Id: Iaf44f50639626fe22ef55862ae3a8b93962a4efe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1626643
Commit-Queue: John Emau <johnemau@microsoft.com>
Reviewed-by: Erik Luo <luoe@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686682}

All users have been switched to using the variant of PostCrossThreadTask
and PostDelayedCrossThreadTask that operate on WTF's once-callbacks
(aka CrossThreadOnceFunction).

BUG=963574
R=haraken@chromium.org, hiroshige@chromium.org

Change-Id: I2ff3732924192f910ae26b810353efa84eafaf0f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1626489
Commit-Queue: Antonio Gomes <tonikitoo@igalia.com>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686681}

The new video_decode_accelerator_perf_tests collect various performance metrics
while decoding a video. To give an idea of the relative amount of frames dropped
the 'frame drop rate' is calculated, which is the ratio between frames dropped
and frames not-dropped. This metric is unfortunately rather confusing to
interpret (e.g. 50% of frames dropped is a frame drop rate of 1). The drop rate
was initially used rather than drop percentage to keep in sync with the old
video_decode_accelerator_unittest.

This CL changes the 'frame drop rate' metric to the more readable 'frame drop
percentage', which is also the metric collected by various other tests such as
the Tast playback_perf_* tests.

TEST=new vda performance tests on eve

BUG=None

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

This CL replaces all remained uses of GetDataResourceAsASCIIString
as well as the implementation of GetDataResourceAsASCIIString
in data_resource_helper.

Bug: 983396
Change-Id: Ic388ac0c72162ae6c081797d23245b5b1f3d41e7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1746213
Commit-Queue: Gyuyoung Kim <gyuyoung@igalia.com>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686679}

This CL converts implementations of nfc.mojom in the renderer process.
Major changes are as below,

 - Change the argument of SetClient from NFCClient to pending_remote<NFCClient>
   in nfc.mojom
 - Change mojo::Binding with mojo::Receiver
 - Change NFCClientPtr with mojo::Remote<NFCClient>

Bug: 955171
Change-Id: Ibfc900f35dc22736e8af3753705e55fadd5ac76a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1750517
Commit-Queue: Gyuyoung Kim <gyuyoung@igalia.com>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Ken Rockot <rockot@google.com>
Cr-Commit-Position: refs/heads/master@{#686678}

When the video_decode_accelerator_(perf_)tests are build for ChromeOS the video
test code expects at least the 'use_v4l2_codec' or 'use_vaapi' flag to be set.
This CL ensures the build works if none of these flags are set. The test won't
work, but the build will not be broken.

BUG=993467

TEST=Built for ChromeOS without 'use_v4l2_codec' or 'use_vaapi' set

Change-Id: Ic7b543907ed1b37bcac2b9f2bc3dc006109a8166
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1752268Reviewed-by: Manu Cornet <manucornet@chromium.org>
Reviewed-by: Hirokazu Honda <hiroh@chromium.org>
Reviewed-by: Chih-Yu Huang <akahuang@chromium.org>
Commit-Queue: David Staessens <dstaessens@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686677}

We allow downgrades by default when installing APKs. We should apply the
same setting for App Bundles. There's no good reason to not allow
downgrades by default for local development, since it's just annoying
when installation fails because a previous install had a higher version.

Note: this does not allow downgrades on user builds, but
"allow_downgrade" is otherwise harmless to pass (the install acts as if
allow_downgrade was not specified).

This is a follow-up to https://crrev.com/c/1383575.

Bug: 915431
Test: manual
Change-Id: I7392d9a4656f702266f5790bee9a7fec395190f0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1746642Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Auto-Submit: Nate Fischer <ntfschr@chromium.org>
Commit-Queue: Nate Fischer <ntfschr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686676}

Disabling to unblock the CQ.

BUG=993604

Change-Id: I6a129e8ae3d8b48b155bfec3ce3bff0ff7657f79
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1753204
Commit-Queue: Rohit Rao <rohitrao@chromium.org>
Reviewed-by: Justin Cohen <justincohen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686675}

... when posting tasks. A task posted runs once, so
CrossThreadBindRepeating is not strictly correct.

This is now possible, after [1].

[1] crrev.com/c/1750043

BUG=964922
R=jbroman@chromium.org

Change-Id: Ic1937f017ec6cd5a532b99a1f270f2ce2a99b8dd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1752078
Commit-Queue: Antonio Gomes <tonikitoo@igalia.com>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686674}

Implement https://github.com/whatwg/xhr/issues/248. We haven't sorted
the headers, so there is no compatibility issue.

Bug: 993271, 651750
Change-Id: Ie69fb45a90795ea303324358312b16b7e6e227aa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1750476Reviewed-by: Yoichi Osato <yoichio@chromium.org>
Reviewed-by: Adam Rice <ricea@chromium.org>
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686673}

This color samples the edges of the dse logo and creates a background
that the logo is then laid on top of.

Bug: 993416
Change-Id: I64ccd7358165334914eff54563f71f141dd4d4db
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1737331
Commit-Queue: Brandon Wylie <wylieb@chromium.org>
Reviewed-by: Theresa  <twellington@chromium.org>
Reviewed-by: Ender <ender@google.com>
Cr-Commit-Position: refs/heads/master@{#686672}

Removes remaining KioskNext code and references.

Bug: 977019
Change-Id: Ic1d554d9771996f87e85ee2d335cbf82da2ec19d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1750264
Auto-Submit: Michael Giuffrida <michaelpg@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Reviewed-by: Ben Wells <benwells@chromium.org>
Commit-Queue: Michael Giuffrida <michaelpg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686671}

If the only tab in a group is added to another group in a way that
causes that tab to move (e.g. there is an intervening ungrouped tab)
then we will crash. This is caused by TabStripModel setting the new
group on WebContentsData and then sending the kMoved notification before
the kGroupChanged notification. TabStripLayoutHelper::MoveTab expects
the group of the tab being moved is not empty according to the model.

This patch fixes the bug by sending kGroupChanged immediately after
setting the group on WebContentsData, so TabStrip will delete the old
group immediately.

Bug: 983961
Change-Id: Ib214a1b7a82f5958e48310477ba9c63d832e3095
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1753059
Commit-Queue: Bret Sepulveda <bsep@chromium.org>
Reviewed-by: Peter Boström <pbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686670}

The removes Service Manager dependencies from the Mirroring Service and
its singular client in Chrome.  CastMirroringServiceHost now manages its
own service process instead of using Service Manager.

This service was also the only service asking to bind the viz.mojom.Gpu
interface through a Connector to the browser (supported by
common_browser_interfaces.cc), so that support code has been removed and
CastMirroringServiceHost instead pushes a Gpu interface to the service,
acquired directly from content::CreateGpuClient(). This should be
functionally equivalent to what was done before but with fewer round-
trips.

Bug: 977637
Change-Id: I2ac8addac4a4e67c8ad35856ec70052530990dcf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1743313
Commit-Queue: Ken Rockot <rockot@google.com>
Reviewed-by: Yuri Wiitala <miu@chromium.org>
Reviewed-by: Takumi Fujimoto <takumif@chromium.org>
Reviewed-by: Eric Karl <ericrk@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686669}

This CL updates an old comment class name to the current name.

Change-Id: I38ef92fab6a26ed1143b3a226d8cf008a2b4352c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1751102
Auto-Submit: Alan Cutter <alancutter@chromium.org>
Reviewed-by: Alexey Baskakov <loyso@chromium.org>
Commit-Queue: Alexey Baskakov <loyso@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686668}

The coverage dump in TerminateCurrentProcessImmediately is currently
blocking us from gathering coverage for sandboxed processes, because
it corrupts the data from those processes.

This is a temporary workaround, until we implement a proper solution
for the data corruption.

Bug: 993537
Change-Id: Idd4669f3d41b349247161e9611e52ca00a9e75ac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1752926
Commit-Queue: Sajjad Mirza <sajjadm@chromium.org>
Reviewed-by: Yuke Liao <liaoyuke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686667}

According to guide[1], it is acceptable to be also named
like macro instead of constants. but it is old way.
so change it to keep consistency with others.

[1] https://google.github.io/styleguide/cppguide.html#Enumerator_Names

Bug: 940736
Change-Id: I8c158f230cea7d68b358b8ff7bd0aeff6df78697
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1600387Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Hwanseung Lee <hs1217.lee@samsung.com>
Cr-Commit-Position: refs/heads/master@{#686666}

Without this the 2D canvas demo https://codepen.io/miguelao/full/ZjJNNw
janks a lot since it enqueues too many presents which introduce implicit
synchronization without the DXGI_PRESENT_ALLOW_TEARING flag.  This moves
the swap chain tearing feature detection to a central place, and makes
shared image swap chain dependent on swap chain tearing.

Bug: 939657, 939659
Change-Id: Ic8a423a4e2742056dcbb8d3d4af473180e246a58
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1750199
Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686665}

No intended behavior change.

TBR=rdevlin

Bug: 961769
Change-Id: I478dea8583b6cf8870812197f61a43207ef9e587
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1752626
Commit-Queue: Nico Weber <thakis@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Auto-Submit: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686664}

Bug: 922145
Change-Id: I568cda76f19e1813b5f8cf8a46775c92b30c272c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1753183
Auto-Submit: John Budorick <jbudorick@chromium.org>
Commit-Queue: Stephen Martinis <martiniss@chromium.org>
Reviewed-by: Stephen Martinis <martiniss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686663}

Change-Id: Idd4f601db27ee27306f3dd159fb5b4ef5a992c4b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1743062Reviewed-by: mark a. foltz <mfoltz@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Clifford Cheng <cliffordcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686662}

After http://crrev.com/3d3751dc8d7a7797939d05f99d5c051b185315be,
the software encoders were being run on the main (network) thread
instead of the dedicated encoder thread. The member
WebrtcVideoScheduler::encode_task_runner_
and the WebrtcVideoEncoderProxy class were unused.

This CL puts the software encoders back on the encoder thread. The
hardware (H264) encoder is not affected, as that runs asynchronously
already.

Change-Id: I8346247dde0ee5bdc0f10578937b8c89a56d3d0f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1752179
Commit-Queue: Lambros Lambrou <lambroslambrou@chromium.org>
Commit-Queue: Jamie Walch <jamiewalch@chromium.org>
Auto-Submit: Lambros Lambrou <lambroslambrou@chromium.org>
Reviewed-by: Jamie Walch <jamiewalch@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686661}

This CL finishes the move from the AppSearchResultRanker to the
RecurrenceRanker. A follow-up will delete the unused ASRR code.

Bug: 989350
Change-Id: I4e5fc82dcc2ab5e33f33da3e9eb134a6f5226118
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1737361
Commit-Queue: Tony Yeoman <tby@chromium.org>
Reviewed-by: Jia Meng <jiameng@chromium.org>
Reviewed-by: Charles . <charleszhao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686660}

This reflects https://github.com/WICG/webpackage/pull/484.

Bug: 969596
Change-Id: I3484b6e76f51a76e507667499dddc37024cc0af7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1750528Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Commit-Queue: Kunihiko Sakamoto <ksakamoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686659}

https://chromium.googlesource.com/external/github.com/google/shaderc/+log/b3b228c60d63..90c00916229f

git log b3b228c60d63..90c00916229f --date=short --no-merges --format='%ad %ae %s'
2019-08-13 zoddicus@users.noreply.github.com Rolling 3 dependencies (#777)

Created with:
  gclient setdep -r src/third_party/shaderc/src@90c00916229f

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

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

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


TBR=radial-bots+chrome-roll@google.com

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

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/6bb29da82994..979fa780ce2f

git log 6bb29da82994..979fa780ce2f --date=short --no-merges --format='%ad %ae %s'
2019-08-13 ehmaldonado@chromium.org depot_tools: Make gclient_scm Python 3 compatible.
2019-08-13 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial).

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

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

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

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


TBR=agable@chromium.org

Bug: chromium:984182
Change-Id: I2373657fba8cb586e78c4e389a90f128601cd6b2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1753084Reviewed-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@{#686657}

Transition to the fully-qualified names has rolled in the SDK, so remove
the legacy accommodation.

Bug: 988195
Change-Id: I41bf4c655526c6ef8fd8d41976c879c4f78ce4ab
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1746760
Auto-Submit: Wez <wez@chromium.org>
Reviewed-by: Kevin Marshall <kmarshall@chromium.org>
Commit-Queue: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686656}

Changes for how gl syncs with Skia was landed: https://chromium-review.googlesource.com/c/chromium/src/+/1738441

This change updates the current SkiaRenderer expectation files to re-enable tests which are now working.

TBR=cblume@chromium.org
TEST=skia_renderer_gl_blink_web_tests,
skia_renderer_vulkan_blink_web_tests
vulkan_swiftshader_blink_web_tests

Change-Id: I4701eacb107f3c3800c209411cb4036951721e0f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1742986Reviewed-by: Jonathan Ross <jonross@chromium.org>
Commit-Queue: Jonathan Ross <jonross@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686655}

https://chromium.googlesource.com/angle/angle.git/+log/225110211231..b3eeb2a40354

git log 225110211231..b3eeb2a40354 --date=short --no-merges --format='%ad %ae %s'
2019-08-13 geofflang@chromium.org Emulate RGB textures using BGRX IOSurfaces.

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

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

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

Issue: Selection APIs can expose ignored nodes.
AXSelections are built using AXPositions (which can be ignored). The
selection is then serialized into AXTreeData. This is read and exposed
directly without any additional logic regarding the ignored state of the
node, allowing for ignored nodes to be exposed to ATs.

Solution:
Add GetUnignoredSelection API to the AXTree to 'fix' positions to be
unignored before exposing them to ATs

Added new APIs
* AXTree::GetUnignoredSelection
* AXPosition::AsUnignoredTextPosition
* AXNode::GetDeepestFirstUnignoredChild
* AXNode::GetDeepestLastUnignoredChild
* AXNode::GetNextUnignoredSibling
* AXNode::GetPreviousUnignoredSibling
* AXNode::GetNextUnignoredInTreeOrder
* AXNode::GetPreviousUnignoredInTreeOrder


Added unit test in ax_tree_unittests
Added Dumptests

Bug: 982414, 985965
Change-Id: Ic889df8edd93140ae7e93dfff6a6def6993e79ab
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1691559
Commit-Queue: Jacques Newman <janewman@microsoft.com>
Reviewed-by: Nektarios Paisios <nektar@chromium.org>
Reviewed-by: Kurt Catti-Schmidt <kschmi@microsoft.com>
Reviewed-by: Kevin Babbitt <kbabbitt@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#686653}