GitLab

`gn format` recently changed its formatting behavior
for deps, source, and a few other elements when they
are assigned (with =) single-element lists to be consistent
with the formatting of updates (with +=) with single-element.

Now that we've rolled in a GN binary with the change,
reformat all files so that people don't get presubmit
warnings due to this.

This CL was uploaded by me.

Bug: 1041419
Change-Id: I38ec77c3b62ca279286533ab1503f347b79a567e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2005628
Commit-Queue: Nico Weber <thakis@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Auto-Submit: Nico Weber <thakis@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732629}

Bug: 1034144
Change-Id: I8f69bae933c264839a60f4ce7c9cb6ac04249895
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003391
Commit-Queue: Kurt Horimoto <kkhorimoto@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732628}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/e9730d75a005..05b001c28df8

git log e9730d75a005..05b001c28df8 --date=short --first-parent --format='%ad %ae %s'
2020-01-16 tandrii@google.com Roll bb tool to @ 9b687fbe

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

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/depot-tools-chromium-autoroll
Please CC agable@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

Bug: chromium:1041950
Tbr: agable@chromium.org
Change-Id: Ib8e4889156074b8eb0392c65d3d1abe4b84fe286
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2005672Reviewed-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@{#732627}

Add an embedding token (UnguessableToken) to FrameTreeNode that serves
to uniquely identify the relationship between an out-of-process
frame and its parent. This token is propagated into the corresponding
active renderer and its parent via RenderFrameProxyHost for use in
Blink. Within Blink this will serve as a way to identify cross process
frame-to-frame relationships. This can replace routing IDs for a number
of uses including in
- Accessibility
- Printing
- Paint Previews

Testing is only browser side ATM.

Bug: 1026322
Change-Id: Ifb4e334733a869b520b6393b9444d83f9e08be1d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1949121
Commit-Queue: Calder Kitagawa <ckitagawa@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732626}

This makes it so that even for unofficial builders you are reminded to run
./generate_perf_sharding.py update-timing --filter-only
if your timing data doesn't match with what you are actually running.

Also run ./generate_perf_sharding.py update-timing --filter-only
to fix the pixel 2 aab timing data.

R=hypan@google.com, johnchen@chromium.org

Change-Id: Idcb8600ca81acb5d81b1e614115ace84dec21376
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003789Reviewed-by: John Chen <johnchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732625}

This was done in response to feedback on my previous CL:
https://chromium-review.googlesource.com/c/chromium/src/+/1965850

Change-Id: I674063047319335e9379d9cbb1a9cd4db24b9625
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2005448Reviewed-by: Alexander Cooper <alcooper@chromium.org>
Commit-Queue: Will Cassella <cassew@google.com>
Cr-Commit-Position: refs/heads/master@{#732624}

Add Italy ("it") and Spain ("es") to the drop-down country selection list that
appears during demo mode setup. Their corresponding organisational units have
already been created in the admin console.

Bug: 1039934
Change-Id: I2341658299f3b9188cd0ad88b31b83a791915b8e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2004353Reviewed-by: Toni Baržić <tbarzic@chromium.org>
Commit-Queue: Patti <patricialor@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732623}

The DNS cache is now a per-NetworkContext cache, instead of a global,
so clearing the cache when closing incognito is no longer useful -
destroying the incognito profile will destroy its own DNS cache.

Bug: 1042354
Change-Id: Ib3fd2dc03cf48ca1ca1d1fd7fca025fccb2a4a2c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003212Reviewed-by: Eric Orth <ericorth@chromium.org>
Commit-Queue: Matt Menke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732622}

Pass unsafely-treat-insecure-origin-as-secure to renderer process. This
is useful in development to run secure context JS API on http pages.

Bug: internal b/143703467
Test: verify on device
Change-Id: I5961383044866bf3c104c7630fcb82d1bd672fe0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2001579
Auto-Submit: Yuchen Liu <yucliu@chromium.org>
Reviewed-by: Junbo Ke <juke@chromium.org>
Reviewed-by: Sean Topping <seantopping@chromium.org>
Commit-Queue: Yuchen Liu <yucliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732621}

This CL modifies the mechanics of getMatchedRules to match the spec.
Rules will be recorded if the extension has either the feedback or
activeTab permission.

Calling getMatchedRules without the declarativeNetRequestFeedback
permission will only return matched rules if activeTab has been granted
for the tabID specified.

Bug: 1035106
Change-Id: I7011a93caec7737c58b7ff88bba2508bfa292f12
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1999546
Commit-Queue: Kelvin Jiang <kelvinjiang@chromium.org>
Reviewed-by: Karan Bhatia <karandeepb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732620}

TBR=futhark@chromium.org

Bug: 1042205
Change-Id: I7b6e7ff570534f05b674dc2ecb4bbd7a67ff01e0
No-Try: True
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2006270Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732619}

Optionally, when creating GATT connections, allow a service UUID to be
specified. Platforms may use this information to optimise discovery. In
practice, only WinRT does so far.

Change-Id: I5718e7dc06cf30e9d443c0677bb1ebff19b91ddf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1989498Reviewed-by: Ovidio de Jesús Ruiz-Henríquez <odejesush@chromium.org>
Commit-Queue: Adam Langley <agl@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732618}

These are still useful, increase until jan of next year.

Bug: 1037424
Change-Id: I01bfa71e039038fb614a7f50018c201474e7d0f5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1998502
Commit-Queue: Alex Newcomer <newcomer@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Auto-Submit: Alex Newcomer <newcomer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732617}

Move logic for checking visibility into its own function, centralize
logic to set the current group, and generally improve code cleanliness.

Bug: 1023035
Change-Id: Ib77a31cb11e221a1e0a3f15cc9da35b777d397ce
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1995780Reviewed-by: Akihiro Ota <akihiroota@chromium.org>
Commit-Queue: Anastasia Helfinstein <anastasi@google.com>
Cr-Commit-Position: refs/heads/master@{#732616}

Set up an API to send overlay to gpu thread. This makes use of the
newly create OverlayProcessorOnGpu class.

This is CL 3/? for sending the overlay candidate directly to gpu thread.

R=rjkroege

Bug: 979788
Change-Id: Ibf1b814c5bec02b8633e3af32698f08672b533a7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1985302
Commit-Queue: weiliangc <weiliangc@chromium.org>
Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732615}

We render them mostly like subframes: with a distinctive prefix, showing the
site URL rather than the title and favicon (which aren't otherwise visible to
the user and so could be misleading). Also like subframes, we mark the host
page as a parent task, so that the parent sorts first in the task manager UI.
Double-clicking on a portal task will activate the tab containing it.

These tags can need to change when portal activation swaps a tab and a portal
within it, so an extra hook after this has been done is added to allow the
delegate in chrome/ to do so.

Finally, tasks are given the opportunity to hold onto the WebContentsTaskManager,
which is useful so that portal tasks can look up their parent. This is somewhat
more dynamic than subframes (whose parent never changes), so looking it up
from the current WebContents relationships seems cleaner than storing a
task_manager::Task* like SubframeTask does.

Browser tests that these update correctly across portal activation, and that
they sort like subframes do are included.

Bug: 932303
Change-Id: I706eb6f8797f395d723b0d4cf0a683cb5665a172
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1998999Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Adithya Srinivasan <adithyas@chromium.org>
Commit-Queue: Jeremy Roman <jbroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732614}

The workaround was landed before a subsequent workaround to limit the
GL version to ES 2.0 with OOPR which is likely to catch any difference
in rendering code-paths in skia when OOPR is enabled. Its very likely
that the second workaround address the stability issues that disabling
this feature was supposed to address.

R=ericrk@chromium.org

Bug: 1042067
Change-Id: I31652f7895efeb9a84df9074bd52e4f9c61b9ae8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2001746
Commit-Queue: Khushal <khushalsagar@chromium.org>
Commit-Queue: Eric Karl <ericrk@chromium.org>
Reviewed-by: Eric Karl <ericrk@chromium.org>
Auto-Submit: Khushal <khushalsagar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732613}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/c06633ee..90449951

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

Change-Id: I4ef5f38e116520a501b8a32a2b5fe6ce85d87237
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1999105Reviewed-by: Ben Smith <binji@chromium.org>
Reviewed-by: Stefan Zager <szager@chromium.org>
Commit-Queue: Deepti Gandluri <gdeepti@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732611}

We need the graph lock to secure the panner backend because
BaseAudioContext::Handle{Pre,Post}RenderTasks() from the audio thread
can touch it.

Test: ran two repro cases from the report over 1 hour and TSAN survived.
Bug: 1042254
Change-Id: Ic394311e72fed51f9df1a961aba0f84b79aed8f1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003564
Commit-Queue: Hongchan Choi <hongchan@chromium.org>
Reviewed-by: Raymond Toy <rtoy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732610}

This test will report the size-on-disk of various system partitions,
including the one that hosts the chrome installation.

Bug: 537081
Change-Id: Ibaa14023c45bf890d1bd5d93a5213eb9263fa439
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1994044Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Ben Pastene <bpastene@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732609}

Add a PIECEWISE_HDR transfer function that is sRGB scaled to hit 1 at
the the specified "SDR joint" in the domain, and then grows linearly
to the specified "HDR level" at 1.

Add the math for this transfer function. Add tests to hit all segments
of the function, for a handful of parameter values.

Add GLSL for this transfer function. Add it transfer function as the
source and target for GL pixel tests.

Bug: 958166
Change-Id: If53dc04777dbf105c465f121bcbcc1dabc1c1ee9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003811
Commit-Queue: ccameron <ccameron@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Miguel Casas <mcasas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732608}

The function checks a deleted element. I switched to checking enrollment
step.

Bug: 1042594
Test: manual call of the function in devtools
Change-Id: I3f0cdc0336bc6be431e68a798aee95d8447052a3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2002513Reviewed-by: Achuith Bhandarkar <achuith@chromium.org>
Commit-Queue: Roman Sorokin [CET] <rsorokin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732607}

This removes the MediaController knob panel below the video
player, and replaces it with controls that are overlaid on
top of the video (and fade away after a small amount of time).

Also introduces a Mute button.

Bug: 895776, 656015
Change-Id: If89fa712c70b62eeda550be87478562c1a118914
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992436Reviewed-by: Theresa  <twellington@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Commit-Queue: Finnur Thorarinsson <finnur@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732606}

A minor cleanup to reduce diff noise on more substantive CLs.

Updates //fuchsia GN files to incorporate recent updates
in how "gn format"'s formats lists with single items.

All changes in this CL were produced by running "git cl format".

Change-Id: I5229dfe9c6989a3ec8b258a9abc06c33c68e5c29
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2006108
Commit-Queue: Kevin Marshall <kmarshall@chromium.org>
Commit-Queue: Fabrice de Gans-Riberi <fdegans@chromium.org>
Reviewed-by: Fabrice de Gans-Riberi <fdegans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732605}

Bug: 1012776, 1012819
Change-Id: Iecf5ce14ec8150e69ac852a818263e5598049817
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003193
Commit-Queue: Haiyang Pan <hypan@google.com>
Reviewed-by: Peter Wen <wnwen@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732604}

The resident size recorded from the metrics show it is never 0. The
devcies in the lab might get a 0 value if some code tries to override
mallinfo. So, remove this unnecessary check. If the metrics go wrong in
future, we can detect that from the UMA.

BUG=843843

Change-Id: Ie9a2e9f5e3f18b1572e45ef8db291f155dbe7c7a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2004903
Auto-Submit: ssid <ssid@chromium.org>
Commit-Queue: Erik Chen <erikchen@chromium.org>
Reviewed-by: Erik Chen <erikchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732603}

Following from https://chromium-review.googlesource.com/1984792, this CL
removes a further redundant call to WebLaunchFilesHelper::SetLaunchPaths,
this time in OpenApplicationWindow.

Bug: 1007621
Change-Id: I79732f93499b209fce42db9a758969bc8b8d8c7c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003159Reviewed-by: Michael Wasserman <msw@chromium.org>
Commit-Queue: Robert Woods <robertwoods@google.com>
Cr-Commit-Position: refs/heads/master@{#732602}

Currently the BinaryUploadService tracks authorization by checking the DM
token with the server. For Advanced Protection users, we will not have a
DM token, so we need to authorize the upload another way. This CL adds a check
for whether the user is truly enrolled in APP as the authorization.

Bug: 1020418
Change-Id: Ie9d61906aeed1fbb68fb68d455a5c24c9d5d31fb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2001107
Commit-Queue: Daniel Rubery <drubery@chromium.org>
Reviewed-by: Bettina Dea <bdea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732601}

This CL checks the existing setting for predictive operations to ensure
users are comfortable with predictively connecting to the search engine
without them explicitly searching.

This also cleans up the code a little bit to move the call to loading
predictor.

Bug: 1036489
Change-Id: Ibe4672cf2f7a2fcc5c678a09833a2ee4df300f21
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992589
Commit-Queue: Ryan Sturm <ryansturm@chromium.org>
Reviewed-by: Alex Ilin <alexilin@chromium.org>
Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732600}

Change-Id: I6b866e83eba6beb749d9cae58323a6b3988771f9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1982920
Commit-Queue: Nasko Oskov <nasko@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732599}

This interaction handler implements logic shared amongst all infobar
modal implementations.  This class encompasses the model-layer updates
possible from the InfobarModalDelegate protocol.  These handlers will
be subclassed to handle interaction events for other protocols that
conform to InfobarModalDelegate.

InfobarModalOverlayRequestCallbackInstaller installs callbacks that
execute the main action for an infobar modal for dispatched
InfobarModalMainActionResponses.  As with the interaction handlers,
subclasses will be created to handle responses corresponding with
InfobarModalDelegate protocols.

Bug: 1030357
Change-Id: I896299166f982bf842e938e325b4318786f759e7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1999453
Commit-Queue: Kurt Horimoto <kkhorimoto@chromium.org>
Reviewed-by: Sergio Collazos <sczs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732598}

Idrefs encountered in <svg:use/> instance trees now referenced the
originating scope as per the spec (and firefox). Introduces a new
node::GetSourceTreeScope() method to facilitate this which can also be
used for bringing style resolution up to the current spec.
(see https://svgwg.org/svg2-draft/struct.html#UseStyleInheritance)

Stop flattening shadow trees of nested <svg:use/> elements as this
is not to spec and was a workaround for the fact that use elements
couldn't resolve their targets from inside a use shadow tree.

Fix instance leak when removing use elements
(removal now tears down instance references).

Fix interaction between SVG relative lengths and shadow dom.

This does not change any webexposed behavior (svg:use has closed shadow dom).
DevTools APIs (invalidation, etc.) and the `internals` testing hook are affected
(hence the rebaselined tests).

Bug: 785246
Change-Id: Ie2429c0cf9ab6aa6bc7851269cf286d3ecb200ac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1986325Reviewed-by: Fredrik Söderquist <fs@opera.com>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Commit-Queue: George Steel <gtsteel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732597}

This reverts commit 4af59255.

Reason for revert: broken linux-archive-rel build

Build error is 

Build failure is: ENOENT: no such file or directory, open '/b/s/w/ir/cache/builder/src/out/Release/gen/ui/webui/resources/cr_elements/cr_splitter/cr_splitter.m.js'

Build is here:
https://ci.chromium.org/p/chromium/builders/ci/linux-archive-rel/19235

Original change's description:
> WebUI: Stop auto-generating Polymer 3 version of cr-splitter.
> 
> The Polymer 2 version is not used anymore, therefore no auto-generation
> is necessary and the v3 version can be directly checked in.
> 
> Fixed: 1042545
> Change-Id: I5054477c0b7427f4ec6b760e5da3eac904af2320
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003114
> Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org>
> Auto-Submit: Demetrios Papadopoulos <dpapad@chromium.org>
> Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#732590}

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

Change-Id: I363a778967e7be5fafc11fb1a72cebdd5c8dac16
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2006214Reviewed-by: Aleks Totic <atotic@chromium.org>
Commit-Queue: Aleks Totic <atotic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732596}

With OOP-D on all platforms, HostFrameSinkManager will never be in the
same process as FrameSinkManagerImpl, so HostFrameSinkManagerLocalTest
no longer makes much sense. Merge it with HostFrameSinkManagerRemoteTest
into HostFrameSinkManagerTest, and refactor the tests to work on remote.

CommunicateFrameToken and HitTestAggregatorQuery require access to
CompositorFrameSinkSupport, but they test things out of scope of this
class, so they can be removed.

Bug: 1033683
Change-Id: I32e1150d7f7858c24f7733b8ad5e62ac242a6fac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1972895Reviewed-by: kylechar <kylechar@chromium.org>
Commit-Queue: Sean Gilhuly <sgilhuly@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732595}

1. Add Begin and End functions to the GL command buffer for
accessing a batch of shared images instead of a single shared
image.

2. Add a new class SharedImageBatchAccessManager to manage the
batch access to the shared images.

3. Add a ScopedBatchReadAccess class in DisplayResourceProvider
to do begin/end read access to a batch of shared images.

4. Update DisplayResourceProvider to do batch read access.

5. Update SharedImageBackingEGL and SharedImageManager to support
batch read access.

Change-Id: I4089ab2e81dc61e5a3c78b860fe96e477dea754a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1999066Reviewed-by: Eric Karl <ericrk@chromium.org>
Commit-Queue: vikas soni <vikassoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732594}

Change-Id: Iff07fe6dc3ba057c38364ea0eba8ae7741083b96
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003641
Commit-Queue: vikas soni <vikassoni@chromium.org>
Reviewed-by: Frank Liberato <liberato@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732593}

Enables scroll to text by default for M81. Note we plan to launch via
Finch for M80.

Intent to ship with LGTMs:
https://groups.google.com/a/chromium.org/d/msg/blink-dev/zlLSxQ9BA8Y/t-_3pAiSAwAJ

This patch also updates web platform test expectations:
- scroll-to-text-fragment.html now passes; it just needed an extra rAF
  for the fallback to element anchor behavior.
- scroll-to-text-fragment-security.html has two expected failures, as
  they need to be updated to test cross-origin navigations. I'll make
  this change in a follow-up patch to close bug 1042311.

Bug: 919204
Change-Id: Ic2d563934cd9406fb335904a94c390bba789e0b4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1838701Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Commit-Queue: Nick Burris <nburris@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732592}

This is a revert of
https://chromium-review.googlesource.com/c/chromium/src/+/1986342
now that the root cause was fixed by
https://chromium-review.googlesource.com/c/chromium/src/+/1987297


Bug: 1039019
Change-Id: I865d0e256e00d1cf615b6d2fe7c006f303aee0ea
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2002944
Commit-Queue: Caleb Rouleau <crouleau@chromium.org>
Auto-Submit: Caleb Rouleau <crouleau@chromium.org>
Reviewed-by: Brian Sheedy <bsheedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732591}

The Polymer 2 version is not used anymore, therefore no auto-generation
is necessary and the v3 version can be directly checked in.

Fixed: 1042545
Change-Id: I5054477c0b7427f4ec6b760e5da3eac904af2320
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003114
Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org>
Auto-Submit: Demetrios Papadopoulos <dpapad@chromium.org>
Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#732590}