GitLab

All asserts need to be in a step func. Unfortunately this makes the
tests more verbose.

Found in https://github.com/web-platform-tests/wpt/pull/8748#issuecomment-398954260.

Change-Id: Ib15270d6093ea094b0f8c387cc4370f5154cf5dd
Reviewed-on: https://chromium-review.googlesource.com/1109689
Commit-Queue: Robert Ma <robertma@chromium.org>
Reviewed-by: Robert Ma <robertma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569401}

This makes the fyi bots run viz_gtests instead of viz_fyi_gtests which removes
a few test binaries, but since those weren't run on any other desktop bot,
it probably wasn't intentional that they run on mac anyways.

Bug: 843511
Change-Id: Ieb132304f3e6b3869c1c2238ec509ed5a95174ab
Reviewed-on: https://chromium-review.googlesource.com/1108360Reviewed-by: Jonathan Ross <jonross@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569400}

https://pdfium.googlesource.com/pdfium.git/+log/bcd66f54de12..3d8131535e6b


git log bcd66f54de12..3d8131535e6b --date=short --no-merges --format='%ad %ae %s'
2018-06-21 tsepez@chromium.org Pass output parameters as pointers in ijs_event_context
2018-06-21 tsepez@chromium.org Remove WideString::c_str() calls where possible.
2018-06-21 tsepez@chromium.org Avoid const-refs to implicitly constructed strings.


Created with:
  gclient setdep -r src/third_party/pdfium@3d8131535e6b

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: Ic8232f5102b620e309927cb2b89866ff19f7251b
Reviewed-on: https://chromium-review.googlesource.com/1110457Reviewed-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@{#569399}

Test: ChromeVox menus (Search+.) works again. It was breaking the page due to this missing message id.
Cq-Include-Trybots: luci.chromium.try:closure_compilation
Change-Id: Id2a5539d29d46343472829b5e4b5d8deefe06e94
Reviewed-on: https://chromium-review.googlesource.com/1107165Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Commit-Queue: David Tseng <dtseng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569398}

- Add two more screens for the flow.
- Update proto definitions

Bug: b/78190629
Test: Manual
Cq-Include-Trybots: luci.chromium.try:closure_compilation
Change-Id: Ic9a849e3184ea5b09e0f0f338a018caf2193d829
Reviewed-on: https://chromium-review.googlesource.com/1105469
Commit-Queue: Yue Li <updowndota@chromium.org>
Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569397}

TBR=jbroman@chromium.org

Bug: 817445
Change-Id: I2336b16d2e10a524c176997b75471b8bc8310460
Reviewed-on: https://chromium-review.googlesource.com/1097482
Commit-Queue: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569396}

BUG=854109

Change-Id: Iac8a8b5c947d890a17b187f1cded75332b3dba27
Reviewed-on: https://chromium-review.googlesource.com/1110517Reviewed-by: Matthew Jones <mdjones@chromium.org>
Commit-Queue: Ted Choc <tedchoc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569395}

BUG=854866

Change-Id: Iff9021221210078e2d013b4c54628b6667323eee
Reviewed-on: https://chromium-review.googlesource.com/1110676Reviewed-by: Becky Zhou <huayinz@chromium.org>
Commit-Queue: Theresa <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569394}

1. Enforce our lack of support for a custom remote-debugging-port
by throwing an error if someone uses it.

2. If we can't parse a devtools port from the file, then check
to see if Chrome has crashed and use that information to improve
the error message. Do this right away instead of waiting 60 seconds.

3. Write tests for these errors!

Bug: chromedriver:2474
Change-Id: Ie649f980745e5241ec462e7527a24d58ced9af02
Reviewed-on: https://chromium-review.googlesource.com/1106769
Commit-Queue: Caleb Rouleau <crouleau@chromium.org>
Reviewed-by: John Chen <johnchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569393}

minijail0 security policy was updated to support new features.
New components that use these new syscalls must use this new
higher env version.

Bug: 850956
Change-Id: I53252a4c25bc1b037b89e81960b9a0f164aab351
Reviewed-on: https://chromium-review.googlesource.com/1106007Reviewed-by: Joshua Pawlicki <waffles@chromium.org>
Commit-Queue: Luke Sorenson <lasoren@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569392}

It was passing in the FrameSinkId, when it should have passed in the window
id.

BUG=837686
TEST=covered by test

Change-Id: I2f6920528403452696d358110605aa85519a0b2d
Reviewed-on: https://chromium-review.googlesource.com/1110748Reviewed-by: Michael Wasserman <msw@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569391}

Detail: In order to get finer resolution when recording metrics,
the program multiples the area/distance metrics by 100 before sending
to UMA, which can cause overflow.

Fix: For area metric, the result is limited to 1.0; for distance
metric, the result is limited to the maximum expected value (10000)
by UMA before sending.

Bug: 853435
Change-Id: Ie8d9751c86bd64f38bd79c3e12d502f71a551522
Reviewed-on: https://chromium-review.googlesource.com/1105506
Commit-Queue: Lu Chen <chelu@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569390}

This is a stepping stone to implement a platform-specific scheduler.

Bug: 801229
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I9da94fc261a0834265e846069a0a6e3c4e51cebf
Reviewed-on: https://chromium-review.googlesource.com/1097838Reviewed-by: Joshua Pawlicki <waffles@chromium.org>
Reviewed-by: Sorin Jianu <sorin@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569389}

This patch replaces the use of cr-link-row polymer element with a simple
div element similar to what the touch calibration button is using. The
cr-link-row element is meant for non indented DOM sections which the
display page is not. The cr-link-row element comes with its own left
padding which is not required in an already indented DOM.

Bug: 844205
Cq-Include-Trybots: luci.chromium.try:closure_compilation
Change-Id: Ic4ecc5bf7388384cb403fa7783a53a18963305d6
Component: Display settings UI, overscan
Reviewed-on: https://chromium-review.googlesource.com/1109205
Commit-Queue: Malay Keshav <malaykeshav@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569388}

Add testing for font service to test methods on FontLoader. FontLoader
will be extended to carry additional FontConfig IPC methods for font
fallback, querying render style for strike, and performing PPAPI
specific font functions. (See "FontService replacing Fonts Sandbox IPC"
design doc [1] and issue [2]).

Before doing that, let's ensure we have a framework to test these
methods. As the font service runs in a child utility process, we need a
way to ensure that it is set up for loading the custom FontConfig
configuration that we use for consistent font access in testing. To that
end, pass a command line feature enabled flag to the child process, and
adding while setting up the TestSuite.

Test basic matching, test failed matching, and test matching the
empty font name.

[1] https://docs.google.com/document/d/1dLBekS3RlcQFldeYZlzFGkuLyX53GBr_7Hbf4cUz1OE/
[2] crbug.com/839344

Bug: 849923
Change-Id: Ib3118d4a53b075725cbdc7fa89ba4f2b9eec8d5e
Reviewed-on: https://chromium-review.googlesource.com/1091754Reviewed-by: Robert Sesek <rsesek@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
Commit-Queue: Dominik Röttsches <drott@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569387}

The simulated clicks are now executed in the containing frame (vs the
container frame).

Bug: 805015
Change-Id: I706b73ab4bad3fc3e1784106829df6db5a1eba30
Reviewed-on: https://chromium-review.googlesource.com/1110341Reviewed-by: Jialiu Lin <jialiul@chromium.org>
Commit-Queue: Mustaq Ahmed <mustaq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569386}

Since page scale factor should never be non-1.f for OOPIFs, and since
we're seeing this happen anyways, this CL inserts some diagnostic checks
to try and determine where in the page-scale-factor pathways the non-1.f
values are originating.

Bug: 845097
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I1d87e3a618d2fd71aa14cc5149084b08ddb7bf14
Reviewed-on: https://chromium-review.googlesource.com/1110345
Commit-Queue: James MacLean <wjmaclean@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569385}

When Night Light doesn't require software cursor, it should
respect other accessibility settings that need the software
cursor.

BUG=854697
TEST=Expanded test.

Change-Id: I6fe29a762265e7319f83af2a1eabe6b608b818c6
Reviewed-on: https://chromium-review.googlesource.com/1109457
Commit-Queue: Ahmed Fakhry <afakhry@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569384}

This follows the discussion which happened on platform-architecture-dev:
https://groups.google.com/a/chromium.org/forum/#!topic/platform-architecture-dev/wuLAMcSvVqs/discussion

Change-Id: I1b65537eadb3ddd5dd3e1a981a3ae5b3e9432e34
Reviewed-on: https://chromium-review.googlesource.com/1094478
Commit-Queue: Dmitry Gozman <dgozman@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569383}

Add expiry to histograms that are not used last 6 months
but report data in stable. More on how the histograms are selected
go/uma-unused-histograms-cleanup

Bug: 850539
Change-Id: I30eee223d5ee1a9d0a421e5ab79a207ea420b651
Reviewed-on: https://chromium-review.googlesource.com/1110021Reviewed-by: Ilya Sherman <isherman@chromium.org>
Commit-Queue: Gayane Petrosyan <gayane@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569382}

TBR=alexander.shalamov@intel.com

Bug: 855222
Change-Id: I5174582d08f61e9133849a2c21d0df3610e54400
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/1110955Reviewed-by: David Grogan <dgrogan@chromium.org>
Commit-Queue: David Grogan <dgrogan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569381}

TBR=anthonyvd@chromium.org

Bug: 854630
Change-Id: I5685ee29e9b2b11b83483452683b07e09ca6245a
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/1110550
Commit-Queue: David Grogan <dgrogan@chromium.org>
Reviewed-by: David Grogan <dgrogan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569380}

This reverts commit 9bb54315.

Reason for revert:

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

Sample Failed Build: https://ci.chromium.org/buildbot/chromium.memory/Mac%20ASan%2064%20Tests%20%281%29/41389

Sample Failed Step: interactive_ui_tests

Original change's description:
> [MacViews] Show/hide top UI in fullscreen mode correctly
> 
> Unlike Windows and Linux, Mac allows top UI to show or hide in browser
> fullscreen mode. Also this option can be toggled at runtime to make the
> change. But in tab fullscreen mode, top UI should always hide. These
> require propagating fullscreen and user preference changes, recording
> the toolbar styles and applying the layout accordingly.
> 
> This CL makes sure the top chrome UI status is correct across different
> fullscreen modes, and responds to user changes as well. Some tests are
> also added.
> 
> BUG=851261,831219,852779
> TEST=Pls check the toolbar/tabstrip show or hide correctly when
> entering and exiting various fullscreen modes. Bookmark bar, slide-down
> menu and traffic lights will be fixed later.
> 
> Change-Id: I78a2b68821d5e633ac5c2823f65390809a57dad5
> Reviewed-on: https://chromium-review.googlesource.com/1102026
> Commit-Queue: Wei Li <weili@chromium.org>
> Reviewed-by: Trent Apted <tapted@chromium.org>
> Reviewed-by: Sarah Chan <spqchan@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#569301}

No-Presubmit: true
No-Tree-Checks: true
No-Try: true
BUG=851261,831219,852779

Change-Id: I2447ccf0b3a960a4e017dcf957d044bff8ae2433
Reviewed-on: https://chromium-review.googlesource.com/1110898
Cr-Commit-Position: refs/heads/master@{#569379}

TBR=anthonyvd@chromium.org

Bug: 854910
Change-Id: Ibc6fd782f7995a784f043f5d24c488d6c1aa38f5
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/1110885Reviewed-by: David Grogan <dgrogan@chromium.org>
Commit-Queue: David Grogan <dgrogan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569378}

This reverts commit 59da623a.

Reason for revert: This work was just deprioritized, so the investigation into the bot only failures is now on the backburner.

Original change's description:
> Add Views DesktopMediaPicker into the Overall Views Build
> 
> This moves the code into the toolkit_views source list and gates Aura
> specific code behind build flags.
> 
> Additionally, this links up DesktopMediaPicker::Create in a manner
> similar to ScreenCaptureNotificationUI::Create[Cocoa].
> 
> BUG=726005,657883
> NOAUTOREVERT=true
> Need to investigate any failure on the Mac Bot. Not reproducible locally.
> 
> Change-Id: I9ece0b875268495d70154378c7608c3e1bae2938
> Reviewed-on: https://chromium-review.googlesource.com/1102042
> Commit-Queue: Robert Liao <robliao@chromium.org>
> Reviewed-by: Scott Violet <sky@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#569095}

TBR=ellyjones@chromium.org,sky@chromium.org,robliao@chromium.org

Change-Id: Ice2800851d19895e687525bc63b8afa9d1746517
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 726005, 657883
Reviewed-on: https://chromium-review.googlesource.com/1110897Reviewed-by: Robert Liao <robliao@chromium.org>
Commit-Queue: Robert Liao <robliao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569377}

Panels were deprecated in M-68 and are no longer supported.

Bug: 788033
Change-Id: Ie62deb2b18fda1869ecf4cd1a12a4bdfa668facf
Reviewed-on: https://chromium-review.googlesource.com/1109028
Commit-Queue: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Ben Wells <benwells@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569376}

This change adds required settings strings for Autofill Home. No further
functionality is added.

Bug: 854562
Change-Id: Id8165651b2484f58818e218c81a4a457cbeda2e3
Reviewed-on: https://chromium-review.googlesource.com/1109680
Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org>
Reviewed-by: Hector Carmona <hcarmona@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569375}

Noticed that the enrollment UMA will be invoked through the
enrollment flow for offline demo mode. At least it shouldn't be
NOTREACHED(). Considering the situation, I believe it can be
handled as other normal enrollment.

BUG=835904
TEST=manually

Change-Id: I61d50258429f3c72132c29d58a6208736756e3d8
Reviewed-on: https://chromium-review.googlesource.com/1092092Reviewed-by: Aga Wronska <agawronska@chromium.org>
Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Commit-Queue: Jun Mukai <mukai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569374}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/3cb681ba..7a5731ed

Please follow these instructions for assigning/CC'ing issues:
https://github.com/v8/v8/wiki/Triaging%20issues

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

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_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;luci.chromium.try:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,machenbach@chromium.org,kozyatinskiy@chromium.org,sergiyb@chromium.org

Change-Id: I67a0d575a7c15c73fdcbe0f34e72935c7b45984c
Reviewed-on: https://chromium-review.googlesource.com/1110441Reviewed-by: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#569373}

Bug: None
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
Change-Id: I93933857c021e2b527abc8a70d74b908789832a6
Reviewed-on: https://chromium-review.googlesource.com/1110518Reviewed-by: Antoine Labour <piman@chromium.org>
Commit-Queue: Jay Civelli <jcivelli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569372}

This cl changes the layouttests in fast/events/wheel to use gpu benchmarking
for sending events rather than event sender.

The cl excludes the following tests for the following reasons:

To change these tests we need to implement touchpad fling (swipe) in GPU
benchmarking:
-mainthread-touchpad-fling-latching.html
-wheel-fling-cancel.html

These tests are skipped since they are related to wheel events only rather
than scrolling:
-wheelevent-constructor.html
-wheelevent-ctrl.html
-wheelevent-document-createevent.html
-wheelevent-handler-count.html

This test will be changed in a different cl among with tests that need
platform specific wheel DOM event expectation.
-wheelevent-in-scrolling-div.html

Bug: 846424
Change-Id: I086e6a7f4f62dce61a838d616a471bd030139e93
Reviewed-on: https://chromium-review.googlesource.com/1103149Reviewed-by: David Bokan <bokan@chromium.org>
Commit-Queue: Sahel Sharifymoghaddam <sahel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569371}

This fixes NavigationAndLoadCallbacksTest.RendererInitiatedHashNavigation.

Bug: 851119
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: Ia02421ad58b285ed62727453824f10eb403a5876
Reviewed-on: https://chromium-review.googlesource.com/1110265
Commit-Queue: Danyao Wang <danyao@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569370}

This fixes NavigationAndLoadCallbacksTest.StateNavigation for

Bug: 851119
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: Idfe93cc78bed9ed16b0ebffea6ab1cfa58a68955
Reviewed-on: https://chromium-review.googlesource.com/1107111
Commit-Queue: Danyao Wang <danyao@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569369}

The two WebCryptoAPI tests have been fixed (and renamed) in upstream
(https://github.com/web-platform-tests/wpt/issues/10794) and we can now
safely remove these two expectations.

TBR=foolip

No-Try: True
Bug: 787971
Change-Id: I76a0c288e37ef92c30d936d76d652e65ab9d204b
Reviewed-on: https://chromium-review.googlesource.com/1110738Reviewed-by: Robert Ma <robertma@chromium.org>
Commit-Queue: Robert Ma <robertma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569368}

The warning suppression flags have been copied from [1] but most of
them were redundant or not needed at all.

[1] - https://github.com/abseil/abseil-cpp/blob/master/absl/copts.bzl

Bug: None
Change-Id: Iac8daf6f7b9e1f213347cd305088d7eca8179388
Reviewed-on: https://chromium-review.googlesource.com/1107978
Commit-Queue: Mirko Bonadei <mbonadei@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569367}

Using wpt-import in Chromium 65ae4fa7.
With Chromium commits locally applied on WPT:
fb20841f "Remove unneeded WebAudio IDL tests"


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

Note to sheriffs: This CL imports external tests and adds
expectations for those tests; if this CL is large and causes
a few new failures, please fix the failures by adding new
lines to TestExpectations rather than reverting. See:
https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md

Directory owners for changes in this CL:
eroman@chromium.org, rsleevi@chromium.org:
  external/wpt/WebCryptoAPI

TBR=robertma

No-Export: true
Change-Id: I70887bd15f651f097bed144c120d7d9f4b164639
Reviewed-on: https://chromium-review.googlesource.com/1110266
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@{#569366}

Bug: 855166
Change-Id: I39d061de7c9d02b1aeb784c4a2fab1c352b39041
Reviewed-on: https://chromium-review.googlesource.com/1110557Reviewed-by: Florin Malita <fmalita@chromium.org>
Commit-Queue: Mike Reed <reed@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569365}

Bug: 853950
Change-Id: I39129f9adb62ca3a0298fc20cb60751959e4ebdd
Reviewed-on: https://chromium-review.googlesource.com/1110343
Commit-Queue: Ganggui Tang <gogerald@chromium.org>
Reviewed-by: Mathieu Perreault <mathp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569364}

Reland of crrev.com/c/1103218 with a one line change.

This cl was reverted because the security_level in the
autofill_metrics_unittests was not set explicitely.

The first patch is the original CL. The second one sets the security
level explicitely in the test class.

Original Description:
This Cl adds autofill metrics based on the security level. The
goal is to see whether the security level impacts the CTR of
autofill suggestions or the card save rate.

Tbr: eugenebut@chromium.org, michaelbai@chromium.org, cthomp@chromium.org
Bug: 853347
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I9ca3460921cf61f35f679013fa8a784c213fa35b
Reviewed-on: https://chromium-review.googlesource.com/1110139Reviewed-by: Eugene But <eugenebut@chromium.org>
Reviewed-by: Mathieu Perreault <mathp@chromium.org>
Commit-Queue: Sebastien Seguin-Gagnon <sebsg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569363}

This is a typedef of a flat set of string constants, plus a couple of
helper functions. In order to allow use within //gpu/vulkan without
needing a dependency on //ui/gl, move it to //ui/gfx.

Bug: 851997
Test: compile
TBR: vollick@chromium.org

Change-Id: I0b2efe8240409bb525467f9d6d47ca01633bdde8
Reviewed-on: https://chromium-review.googlesource.com/1108505Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Commit-Queue: Michael Spang <spang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569362}