GitLab

As part of the update, syntax for paper-icon-button-light changed, so
this CL will also update our usage of it.

R=dpapad@chromium.org

Bug: 808542
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I9ac87a515e2d07084f85ab07b66b7f2e32f3d544
Reviewed-on: https://chromium-review.googlesource.com/907856
Commit-Queue: Hector Carmona <hcarmona@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542362}

Most mojo services are simple utility processes that don't require
blink web sandbox support. However, services such as pdf compositor
would need such support to access and load fonts. This CL does the
following two major tasks:
-- Add SandboxSupportedUtilityBlinkPlatformImpl and implements it
to allow utility process to have the sandbox support when needed;
-- Move LoadFont() interprocess call on MacOS from renderer to
content/common, so it can be used by both renderer and utility
processes.

BUG=809763,813034

Change-Id: I4f8b50cc5cc31ac68dfbc2ba5b1195fb4e0748cc
Reviewed-on: https://chromium-review.googlesource.com/919968
Commit-Queue: Wei Li <weili@chromium.org>
Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542361}

Bug: 820589
Change-Id: I16c02746c61f42fafead5f96ae436b331fba4f85
Reviewed-on: https://chromium-review.googlesource.com/957587
Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542360}

This data type is useful for sending stats from the renderer to the
browser, in SubresourceResponseStarted methods.  Currently there are six
fields that are passed around, but soon there may be more in order to
get PageLoadMetrics working with the Network Service.

This reverts commit badc08ce.

This fixes the problem with the previous change by ensuring we have an
IP address before attempting to update the ClientSideDetectionHost IP
map.

BUG=816684,819916,820032

Change-Id: I24ebb230c5bd76a5d2a43b39e86aba7541386bec
Reviewed-on: https://chromium-review.googlesource.com/957802
Commit-Queue: Conley Owens <cco3@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542359}

Bug: 819044
Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: I3d7cf99b0785198c8906f4bf43d3fa072c565b4b
Reviewed-on: https://chromium-review.googlesource.com/950462
Commit-Queue: James Darpinian <jdarpinian@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542358}

This fixes a crash if the download item controller goes away while the
button is tracking the mouse and then sends its action on mouse up.

Bug: 815161
Change-Id: I4ab377ca5fe190e3d95aa81b989c13c96b46f5b4
Reviewed-on: https://chromium-review.googlesource.com/957843
Commit-Queue: Avi Drissman <avi@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542357}

When an object's fragments change, e.g.
- the object moved from one fragment to another fragment of the
  flow thread;
- the object resized and created more or less fragments
etc., we need to update paint properties of the subtree.

The new logic also covers the previous SetNeedsPaintPropertyUpdate
logic for multicols.

Bug: 817803
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: Ib641c1e5ef5af7d93b8fb8de70cdc9aae2382fc9
Reviewed-on: https://chromium-review.googlesource.com/953566Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542356}

This code has been unused since we removed the Profile menu
from the CrOS Chrome browser window.

Per suggestion by jamescook, added comments mentioning the old code
in case we decide to add back Chrome OS-specific UI in the future.

Bug: None

Change-Id: Idd63c64926f571f665a76f68b056d62c54797b05
Reviewed-on: https://chromium-review.googlesource.com/956627
Commit-Queue: Michael Giuffrida <michaelpg@chromium.org>
Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542355}

https://pdfium.googlesource.com/pdfium.git/+log/0d0d3ad30ca8..073b99d51c7a

$ git log 0d0d3ad30..073b99d51 --date=short --no-merges --format='%ad %ae %s'
2018-03-09 dsinclair Cleanup CPDF_DefaultAppearance

Created with:
  roll-dep src/third_party/pdfium


The AutoRoll server is located here: https://pdfium-roll.skia.org

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

Change-Id: I4cffbad23b210d0908ca7340bd83fea5fe1fad16
Reviewed-on: https://chromium-review.googlesource.com/958122Reviewed-by: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#542354}

We used to fire DataPipeDrainer::Client::OnDataComplete() twice
because underlying SimpleWatcher fired its client callback twice when
MOJO_RESULT_FAILED_PRECONDITION occurs after the remote end of data pipe
is closed.

Change-Id: I241aa6648dec79c2cf60e9c32de70a52d59d3412
Reviewed-on: https://chromium-review.googlesource.com/958094Reviewed-by: Ken Rockot <rockot@chromium.org>
Commit-Queue: Andrey Kosyakov <caseq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542353}

An alert is more suited to situations where the message is not directly related to the user's input.

Bug: None
Change-Id: I4de40267e7aab8ffd4bca5e7efa104591ea04c2b
Reviewed-on: https://chromium-review.googlesource.com/956846
Commit-Queue: Aaron Leventhal <aleventhal@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Reviewed-by: Evan Stade <estade@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542352}

Using wpt-import in Chromium 91d310c1.
With Chromium commits locally applied on WPT:
946e66a2 "Add http-state cookie tests from abart/http-state github repository"


Build: https://ci.chromium.org/buildbot/chromium.infra.cron/wpt-importer/13543

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

TBR=foolip

No-Export: true
Change-Id: I65e890f50602844b7a44538a877218713b413667
Reviewed-on: https://chromium-review.googlesource.com/957663
Commit-Queue: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org>
Reviewed-by: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542351}

BUG=762641
TBR=xdai@google.com

Change-Id: Icee681f5418f0c9e3ca1735293fcd0d72a6ec356
Reviewed-on: https://chromium-review.googlesource.com/958184Reviewed-by: ChromeOS Commit Bot <chromeos-commit-bot@chromium.org>
Commit-Queue: ChromeOS Commit Bot <chromeos-commit-bot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542350}

This change adds discovery session support to FakeCentral in order to
allow Bluetooth scanning to be simulated.

BUG=719826,719827

Change-Id: Ia5150cc14924e9e03e5361797068db6718b26595
Reviewed-on: https://chromium-review.googlesource.com/954231Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org>
Commit-Queue: Ovidio Henriquez <odejesush@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542349}

https://webrtc.googlesource.com/src.git/+log/ba907f00581e..35576ac007c8

$ git log ba907f005..35576ac00 --date=short --no-merges --format='%ad %ae %s'

Created with:
  roll-dep src/third_party/webrtc
BUG=None


The AutoRoll server is located here: https://webrtc-chromium-roll.skia.org

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=master.tryserver.chromium.linux:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng;master.tryserver.chromium.win:win-msvc-dbg
TBR=webrtc-chromium-sheriffs-robots@google.com

Change-Id: Ib357939707fe9dc5530c57f1df3bf3126b1902c9
Reviewed-on: https://chromium-review.googlesource.com/958100
Commit-Queue: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#542348}

The original CL crrev.com/c/903223 changed the GetCurosr logic
only for notification surface. Regular exo surface should do the same.

This also removes obsolete path.

Bug: 814600
Test: manual. See bug for repro step.
Change-Id: Icbdf000db30efa96aa056c1b7fe15d38822b7610
Reviewed-on: https://chromium-review.googlesource.com/956103Reviewed-by: David Reveman <reveman@chromium.org>
Commit-Queue: Mitsuru Oshima <oshima@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542347}

http://crrev.com/535822, while not enabled, accidentally broke cases
where a seek should resume the pipeline by completing the seek before
the Resume() call. This was partially documented and partially tested
behavior, but unfortunately neither was sufficient to avoid this issue
being introduced.

I've updated the tests and documentation for this functionality and
reworked how suspended start works; though it is still unlaunched on
current ToT.

This CL also adds some debugging logs to WebMediaPlayerImpl which I
find myself manually readding everytime I need to debug one of these
issues.

BUG=813573, 818554
TEST=manual, fixed existing unittest

Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: Ifa9c78726abf3e243cfeac8b983d41605c1c7bf2
Reviewed-on: https://chromium-review.googlesource.com/956326
Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
Commit-Queue: Dan Sanders <sandersd@chromium.org>
Reviewed-by: Dan Sanders <sandersd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542346}

A jumbo build error occurs since https://crrev.com/c/933867. It is
caused by the same name conflict in the anonymous namespace. Please see
the following CL and comments there.
  - https://crrev.com/c/940641

So, this patch simply resolves the name conflict by removing `using`
statement in service_worker_version.cc.

TBR=leon.han@intel.com,shimazu@chromium.org

Bug: none
Change-Id: Iebb3ecc7f0295ff48fdf724429edd538da465249
Reviewed-on: https://chromium-review.googlesource.com/957568
Commit-Queue: Jinho Bang <jinho.bang@samsung.com>
Reviewed-by: Jinho Bang <jinho.bang@samsung.com>
Cr-Commit-Position: refs/heads/master@{#542345}

Adds a Mojo typemap to properly handle the UUID strings in
the service_data field of ScanRecord. The typemap allows the
service_data field to map to a device::BluetoothDevice::ServiceDataMap
object in C++.

BUG=817603

Change-Id: Ie4d5785e8b04098fda76ca8bc99c58141c9b5b82
Reviewed-on: https://chromium-review.googlesource.com/942307
Commit-Queue: Ovidio Henriquez <odejesush@chromium.org>
Reviewed-by: Ken Rockot <rockot@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542344}

This gn arg should only be enabled when component updated CDM is
supported, which is only the case on Windows and Mac for now.

Bug: 663554
Change-Id: I8d6e6dfdfba8b53bef80d84f376f1ebd36fb4605
Reviewed-on: https://chromium-review.googlesource.com/957707Reviewed-by: John Rummell <jrummell@chromium.org>
Commit-Queue: Xiaohan Wang <xhwang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542343}

This CL may cause a small binary size increase, roughly proportional
to how long it's been since our last AFDO profile roll. For larger
increases (around or exceeding 100KB), please file a bug against
gbiv@chromium.org. Additional context: https://crbug.com/805539

The AutoRoll server is located here: https://afdo-chromium-roll.skia.org

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

Change-Id: I61e462bd1cb5d92f74fd619e4d9142418ebfcf55
Reviewed-on: https://chromium-review.googlesource.com/958228
Commit-Queue: afdo-chromium-autoroll <afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: afdo-chromium-autoroll <afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#542342}

https://skia.googlesource.com/skia.git/+log/8c4cbf4cfb6d..0c51eeada6a9

$ git log 8c4cbf4cf..0c51eeada --date=short --no-merges --format='%ad %ae %s'
2018-03-09 bsalomon Add GrMockRenderTarget and mock backend render targets

Created with:
  roll-dep src/third_party/skia


The AutoRoll server is located here: https://autoroll.skia.org

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=master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
TBR=fmalita@chromium.org

Change-Id: I9ff039a3a2f7441ebe9d70ad8f5e365356bace5f
Reviewed-on: https://chromium-review.googlesource.com/957965
Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#542341}

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

Change-Id: I8e7f69af46113860c077f2d1811d442d7c914bdd
Reviewed-on: https://chromium-review.googlesource.com/958182Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542340}

This reverts commit b513507c.

Reason for revert:

Findit (https://goo.gl/kROfz5) identified CL at revision 542315 as the
culprit for failures in the build cycles as shown on:
https://findit-for-me.appspot.com/waterfall/culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyRAsSDVdmU3VzcGVjdGVkQ0wiMWNocm9taXVtL2I1MTM1MDdjZTQ5ZDhjMWU2ZWYwNThmNDUwODJmOGQyMzMxYzk4MzMM

Sample Failed Build: https://ci.chromium.org/buildbot/chromium.chromiumos/linux-chromeos-dbg/4635

Sample Failed Step: compile

Original change's description:
> tablet: Remove minimum time between taps for quick switch.
> 
> Previously relied on using tap_count in GestureEvent which has a minimum
> time between taps of 40ms for consecutive taps to have tap_count of 2.
> Remove that and track double taps in overview button tray.cc. Allows
> double tap from mice now.
> 
> Test: ash_unittests OverviewButtonTrayTest.*
> Bug: 817883
> Change-Id: Icce2e668223f938a7f8194c5f0a03279abff9907
> Reviewed-on: https://chromium-review.googlesource.com/956769
> Commit-Queue: Sammie Quon <sammiequon@chromium.org>
> Reviewed-by: James Cook <jamescook@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#542315}

Change-Id: If15964ea1fab006fc7420d708dc08f0f6b5ca03f
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 817883
Reviewed-on: https://chromium-review.googlesource.com/958132
Cr-Commit-Position: refs/heads/master@{#542339}

If a message is read from a port and then re-transmitted over another
port, it currently retains its previous sequence number. This is
problematic and can trivially lead to the message being lost (or rather,
queued invisibly forever).

This CL resets a message object's sequence number immediately before
passing it out to the user reading the port.

Bug: None
Change-Id: I31604b341c55eee0c7ad6e1fd21e385fb945cf60
Reviewed-on: https://chromium-review.googlesource.com/955555Reviewed-by: Jay Civelli <jcivelli@chromium.org>
Commit-Queue: Ken Rockot <rockot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542338}

Bug: 817982
Change-Id: I823b9203db0f549c19f9de7f5ac742ba358b8858
Reviewed-on: https://chromium-review.googlesource.com/952187
Commit-Queue: Chris Palmer <palmer@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542337}

Bug: 817779
Change-Id: Ie45ebfb14d2bdeeb80724ec94d1fce74cc64b8a8
Reviewed-on: https://chromium-review.googlesource.com/957648Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Benjamin Pastene <bpastene@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542336}

This updates the filtering preferences (AuthenticatorSelectionCriteria,
AttestationConveyancePreference, UserVerificationRequirement) in blink
and plumbs the options through authenticator.mojom,
along with typeconverters.

These preferences are used to determine the types of authenticators
the relying party wants/needs to use.

Bug: 803832
Change-Id: I070ec4bc04de81ad955e878df45a716e3f9083b9
Reviewed-on: https://chromium-review.googlesource.com/947038
Commit-Queue: Kim Paulhamus <kpaulhamus@chromium.org>
Reviewed-by: Balazs Engedy <engedy@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542335}

This fixes a bug related to the implementation of
AwContentsIoThreadClient::FromID(frame_tree_node_id). This function is
implemented using a map to keep track of the AwContentsIoThreadClient
for a particular FrameTreeNode.

Before this change, we would remove a map entry for a frame_tree_node_id
whenever we destroy an associated RenderFrameHost. This is incorrect in
multiprocess mode however, because a FrameTreeNode may have multiple
associated RenderFrameHosts in its lifetime (such as swapping
RenderFrameHosts for cross-site navigations). When we swap, we would
first overwrite the map entry for the new RenderFrameHost, then erase
the map entry when we destroy the old RenderFrameHost.

The issue manifests most visibly for Safe Browsing, because FromID()
returns nullptr, and Safe Browsing logic defaults to disabling the
feature. However, this issue is not specific to Safe Browsing, and this
would bug would cause a bad state whenever we trigger multiple
cross-site browser-initiated navigations.

With this change, we keep track of live RenderFrameHosts for a given
FrameTreeNode, and only remove an entry from the map if we've destroyed
the last associated RenderFrameHost.

Bug: 818025
Test: manual - see bug for repro steps
Change-Id: I2ae81fdb5338084cdf253582206144b4f45704b1
Reviewed-on: https://chromium-review.googlesource.com/956411Reviewed-by: Bo <boliu@chromium.org>
Commit-Queue: Nate Fischer <ntfschr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542334}

If a paint invalidation container returns true from IsPaintInvalidationContainer(),
that means it is composited, which in turn must mean the containing LayoutView is composited.

This allows us to simplify the code and avoid a call to View(), which may be expensive
because it has to first dereference the document.

Bug: 814251
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: I79cc37ee79271c2030a9f5c832ba5640ca8445c9
Reviewed-on: https://chromium-review.googlesource.com/957962Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542333}

Should prevent crashes due to the matrix info not being sent properly.

Bug: 820377
Change-Id: I36ee0af1f60333e55b3a076e72123fe4f5f3099f
Reviewed-on: https://chromium-review.googlesource.com/957808Reviewed-by: Brian Sheedy <bsheedy@chromium.org>
Commit-Queue: Brian Sheedy <bsheedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542332}

Bug: 800588, 800997
Change-Id: I8312deae3c1e4d1f3a16169e4b875538c5cb610d
Reviewed-on: https://chromium-review.googlesource.com/956682
Commit-Queue: Jared Saul <jsaul@google.com>
Reviewed-by: Mathieu Perreault <mathp@chromium.org>
Reviewed-by: anthonyvd <anthonyvd@chromium.org>
Reviewed-by: Evan Stade <estade@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542331}

R=hinoka@chromium.org, iannucci@chromium.org, jchinlee@chromium.org, smut@google.com, vadimsh@chromium.org

Change-Id: Iaf3c26162afbd8cdefcf49073f3c8900bc23911e
Reviewed-on: https://chromium-review.googlesource.com/957964Reviewed-by: smut <smut@google.com>
Reviewed-by: Ryan Tseng <hinoka@chromium.org>
Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
Reviewed-by: Jao-ke Chin-Lee <jchinlee@chromium.org>
Commit-Queue: Andrii Shyshkalov <tandrii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542330}

BUG=762641
TBR=xdai@google.com

Change-Id: I229e43c8818b6ae91e26074dd1e617456f544404
Reviewed-on: https://chromium-review.googlesource.com/958142
Commit-Queue: ChromeOS Commit Bot <chromeos-commit-bot@chromium.org>
Reviewed-by: ChromeOS Commit Bot <chromeos-commit-bot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542329}

This allows the dialog to use Harmony defaults.

Bug: 820619
Change-Id: I814012b85324f27cd8b95346513f1b3d630aae24
Reviewed-on: https://chromium-review.googlesource.com/957818Reviewed-by: Evan Stade <estade@chromium.org>
Commit-Queue: Jared Saul <jsaul@google.com>
Cr-Commit-Position: refs/heads/master@{#542328}

https://chromium.googlesource.com/angle/angle.git/+log/33140409810f..e2995cce7161

$ git log 331404098..e2995cce7 --date=short --no-merges --format='%ad %ae %s'
2018-03-09 jmadill Vulkan: Fix layers not being enabled on the bots.
2018-03-09 geofflang Use full type names instead of auto for simple structs.
2018-03-09 geofflang Rename syncRendererState methods to syncImplementationState.
2018-03-09 cwallez cq.cfg: Add equivalent_to to ramp-up during LUCI migration
2018-03-09 ynovikov Skip TransformFeedbackLifetimeTest.DeletedBuffer on Win Intel GL
2018-03-09 jmadill Vulkan: Add Vk format overrides table.
2018-03-09 jmadill Vulkan: Use free descriptor set bits in pool.
2018-03-09 lucferron Vulkan: Fix issue in blending factor conversions
2018-03-08 jmadill Nuke ValidationContext.
2017-09-22 geofflang Reorder state synchronization for resource init.

Created with:
  roll-dep src/third_party/angle
BUG=815092


The AutoRoll server is located here: https://angle-chromium-roll.skia.org

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=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
TBR=ynovikov@chromium.org

Change-Id: I6a77383ed0bda7bb90494f0af30d7bf39b620819
Reviewed-on: https://chromium-review.googlesource.com/957884Reviewed-by: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#542327}

Currently snapshots in DevTools are letterboxed if the renderer is resized multiple
times. Although this might be desirable for other usages of FrameSinkVideoCapturer,
we definitely don't want this for DevTools, so add a method to configure resize
throttling period.

Bug: 813929
Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel
Change-Id: I12807e57a0b9a4a2131c46a97c004fb2d577ea2f
Reviewed-on: https://chromium-review.googlesource.com/954012Reviewed-by: Yuri Wiitala <miu@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Commit-Queue: Saman Sami <samans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542326}

This will be needed to start loading the variations seed earlier. Also
clean up the places where we were passing the package name around.

BUG=954058

Change-Id: Ia5345688cc6e1cac6451f1ddeda248d1f504d81d
Reviewed-on: https://chromium-review.googlesource.com/957862Reviewed-by: Bo <boliu@chromium.org>
Commit-Queue: Paul Miller <paulmiller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542325}

And instead changes GetRootWindowForEventDispatch() to return null if
not in a valid hierarchy for event dispatch.

BUG=none
TEST=none

Change-Id: I9e8d23d3607fb600d2cf0c80ff1086688a4b6c13
Reviewed-on: https://chromium-review.googlesource.com/956849Reviewed-by: James Cook <jamescook@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542324}

This removes the hardcoded setup of the decrypting audio
and video decoders out of the DecoderSelector and into the
standard decoder list.

This functions similarly to the old behavior, but instead of
knowing except for the following differences:
- All decoders are checked for encrypted support first now.
- If no decoder succeeds in initialization with an encrypted
configuration, we'll try creating a DecryptingDemuxerStream,
if this succeeds we'll check the decoder list again, if it
fails, we'll abort as before.

Mainly this implies that falling back to decrypt-only will
take slightly longer than before. This also adds back support
for EME to use GpuMemoryBuffers.

BUG=801245
TEST=updated lots of unittests...

Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: I578809aeebaa59d81f65a5be2f2f1f76713d0f68
Reviewed-on: https://chromium-review.googlesource.com/952207Reviewed-by: Xiaohan Wang <xhwang@chromium.org>
Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#542323}