GitLab

This adds tests that stylesheets that result from requests that were
redirected cross-origin are considered cross-origin.

Note that A->B->A redirects, which redirect from cross-origin to
same-origin, are considered cross-origin. See
https://github.com/whatwg/fetch/issues/737 and
https://github.com/whatwg/fetch/pull/834.

In Blink, we have redirect tests at
http/tests/security/cannot-read-cssrules-redirect.html. This WPT
addition will supersede that test, but I won't yet remove it since
it asserts the opposite for the A->B->A case. I can remove the test
when Blink changes to pass this WPT test.

Bug: 911974
Change-Id: Ie015c0390829299de7c29cff6685ddfcd774c66f
Reviewed-on: https://chromium-review.googlesource.com/c/1370162Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#615475}

https://skia.googlesource.com/skia.git/+log/264843e30745..9cabb4f98e99


git log 264843e30745..9cabb4f98e99 --date=short --no-merges --format='%ad %ae %s'
2018-12-11 skia-bookmaker@skia-swarming-bots.iam.gserviceaccount.com Update markdown files


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

The AutoRoll server is located here: https://autoroll.skia.org/r/skia-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-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
TBR=ethannicholas@chromium.org

Change-Id: I2de3c5dc1c1a5b17947f8be476eac57818ee2d24
Reviewed-on: https://chromium-review.googlesource.com/c/1371256Reviewed-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@{#615474}

This patch removes a comment in a test that is not needed. It
was a left over in r615053 (CL:1366472).

Bug: 904291
Change-Id: I785080fd401426261d6259c22f5f20059fdcba1f
Reviewed-on: https://chromium-review.googlesource.com/c/1370148Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#615473}

This CL addsSigninTestUtil.resetSigninState call to
OAuth2TokenServiceIntegrationTest.tearDown, so all signin-related prefs
are wiped and the state doesn't leak from the test.

Bug: 908542
Change-Id: I43b37d76bd24e14687a4e9d0ab35d2e88d283f6f
Reviewed-on: https://chromium-review.googlesource.com/c/1369940Reviewed-by: Mihai Sardarescu <msarda@chromium.org>
Commit-Queue: Boris Sazonov <bsazonov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#615472}

This CL increases the switch compression resistance priority to make
sure that it doesn't get too compressed by the label.

Bug: 912698
Change-Id: Ib8926b6fbcc60394506a9b348e9f79e4a11fae5d
Reviewed-on: https://chromium-review.googlesource.com/c/1370274Reviewed-by: Yi Su <mrsuyi@chromium.org>
Commit-Queue: Gauthier Ambard <gambard@chromium.org>
Cr-Commit-Position: refs/heads/master@{#615471}

Currently if the default favicon request is caught by the testing service worker
the test fails.
This is causing the test flakiness.
To fix this flakiness, this CL change the fetch event handler of the service
worker to ignore the default favicon request.

Bug: 912543
Change-Id: Icdddd902a4547361320f43db5b9090270ba74509
Reviewed-on: https://chromium-review.googlesource.com/c/1370160
Commit-Queue: Tsuyoshi Horo <horo@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#615470}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/8a7be9d55a9c..b04ad33a6ff2


Created with:
  gclient setdep -r src-internal@b04ad33a6ff2

The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-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=mmoss@chromium.org

Change-Id: I07ce2495c2f1f849b57cbc435a5a865bbd1522f6
Reviewed-on: https://chromium-review.googlesource.com/c/1371255Reviewed-by: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#615469}

There are some edge cases where IsLoaded is true but IsFinishedInternal
is not (yet) true, so remove that check and expand the comment.

Bug: 865098
Bug: 899217
Bug: 909858
Change-Id: I886df54c9a373e7431938aadd4a6a1a4d256d7dc
Reviewed-on: https://chromium-review.googlesource.com/c/1369789Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Commit-Queue: Leszek Swirski <leszeks@chromium.org>
Cr-Commit-Position: refs/heads/master@{#615468}

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

Please note that, despite rolling to chrome/android, this profile is
used for both Linux and Android.

The AutoRoll server is located here: https://autoroll.skia.org/r/afdo-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=gbiv@chromium.org

Change-Id: I74bc59cee5321321971257c15ddf89fe9773c1a9
Reviewed-on: https://chromium-review.googlesource.com/c/1371039Reviewed-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@{#615467}

This CL changes the view displayed when the TabGrid is empty to add a
scroll view. The scroll view allows the user to display the whole text
even with large fonts.

Bug: 896302
Change-Id: I94696f969aa1f7ae05be626bde2c10248f00b6df
Reviewed-on: https://chromium-review.googlesource.com/c/1363281
Commit-Queue: Gauthier Ambard <gambard@chromium.org>
Reviewed-by: edchin <edchin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#615466}

This reverts commit d080cfa6.

Reason for revert: Suspected culprit for ExtensionApiTabTest.UpdateWindowResize failure on network_service_browser_tests (failing on chromium.mac/Mac10.12 Tests).

Bug: 913848

Original change's description:
> Move toolbar to new FlexLayout, demonstrating new layout manager.
> 
> Vastly simplifies layout in the toolbar and makes it mostly declarative with a
> single init function, rather than complex, bespoke - and sometimes incorrect -
> Layout(), GetMinimumSize(), etc. methods.
> 
> Because of a logical change in the way the UI works when an extension is
> uninstalled, we uncovered a possible read-after-free in the extension install
> UI (shows up in some ASAN tests). So we plumbed the scoped_refptr through from
> crx_installer to the UI so that the memory would be valid until the bubble is
> closed.
> 
> See parent CL for FlexLayout details and future work.
> 
> Bug: 898632
> Change-Id: I2cfe5b6119dc2886f88ae12675f8184cf90d56fd
> Reviewed-on: https://chromium-review.googlesource.com/c/1331041
> Commit-Queue: Dana Fried <dfried@chromium.org>
> Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
> Reviewed-by: Bret Sepulveda <bsep@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#615372}

TBR=rdevlin.cronin@chromium.org,bsep@chromium.org,dfried@chromium.org

Change-Id: Ie93f170c2c6048072820f2d6dc9950f75bc4aa94
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 898632
Reviewed-on: https://chromium-review.googlesource.com/c/1371384Reviewed-by: Friedrich Horschig [CET] <fhorschig@chromium.org>
Commit-Queue: Friedrich Horschig [CET] <fhorschig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#615465}

Bug: 886583
Change-Id: I107a11cdcd9d299533789cffed8c3446561f4968
Reviewed-on: https://chromium-review.googlesource.com/c/1365432Reviewed-by: Vadym Doroshenko <dvadym@chromium.org>
Reviewed-by: Rohit Rao <rohitrao@chromium.org>
Reviewed-by: Olivier Robin <olivierrobin@chromium.org>
Commit-Queue: David Jean <djean@chromium.org>
Cr-Commit-Position: refs/heads/master@{#615464}

Bug: 576864
Change-Id: I3290cb0876f3ca84ec0efb13922b2756138b9492
Reviewed-on: https://chromium-review.googlesource.com/c/1369763Reviewed-by: Marc Treib <treib@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Takuto Ikuta <tikuta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#615463}

Read and parse the plist, and tell Print Preview about the custom paper
sizes.

BUG=477699

Change-Id: Ia22e2d95e627d1796b1346ab6e3baeef89a9f2ae
Reviewed-on: https://chromium-review.googlesource.com/c/1364228
Commit-Queue: Lei Zhang <thestig@chromium.org>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#615462}

The new test is similar to the existing PersonalDataManagerSanity test,
but adds checks for the Sync.ModelTypeEntityChange3.AUTOFILL_PROFILE
histogram.
Compared to PersonalDataManagerSanity, the new test skips the step of
adding a duplicate profile, since that seems to produce flaky results.

Bug: 904390
Change-Id: Ic85050dcab80e53ea1a5e1fa63f61db5e6c2cb09
Reviewed-on: https://chromium-review.googlesource.com/c/1369778Reviewed-by: Jan Krcal <jkrcal@chromium.org>
Commit-Queue: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#615461}

https://skia.googlesource.com/skia.git/+log/ae0d860ba31b..264843e30745


git log ae0d860ba31b..264843e30745 --date=short --no-merges --format='%ad %ae %s'
2018-12-11 skia-recreate-skps@skia-swarming-bots.iam.gserviceaccount.com Update go_deps asset


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

The AutoRoll server is located here: https://autoroll.skia.org/r/skia-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-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
TBR=ethannicholas@chromium.org

Change-Id: Ie41dd4f4977bf51bd0d31225f555d62f0a6dafde
Reviewed-on: https://chromium-review.googlesource.com/c/1371252Reviewed-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@{#615460}

Openssl does not take --subj parameter, but -subj.

Bug: 803774
Change-Id: Ie5e1da18941468fc66ea567134a49178b4260aba
Reviewed-on: https://chromium-review.googlesource.com/c/1370177Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Commit-Queue: Rob Buis <rbuis@igalia.com>
Cr-Commit-Position: refs/heads/master@{#615459}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/d31d9e9af460..8a7be9d55a9c


Created with:
  gclient setdep -r src-internal@8a7be9d55a9c

The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-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=mmoss@chromium.org

Change-Id: Iac716d778c5208ad7431b0daa4cdb1cde8f832fb
Reviewed-on: https://chromium-review.googlesource.com/c/1371251Reviewed-by: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#615458}

Bug: 911415
Change-Id: I8f4a0e452bb508fa5ccb2c9f9701e1b9834b8b81
Reviewed-on: https://chromium-review.googlesource.com/c/1370163Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/master@{#615457}

Following Chris Palmer's email[1], this CL removes apacible from
Picture-in-Picture related OWNERS as she is not actively working on
Chromium.

[1] https://groups.google.com/a/chromium.org/d/msg/chromium-dev/ZgEddsRE6do/UPcD-sptBgAJ

Change-Id: I77f12a916c359c92dc329a5b59076983ecd86269
Reviewed-on: https://chromium-review.googlesource.com/c/1361729Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Commit-Queue: François Beaufort <beaufort.francois@gmail.com>
Cr-Commit-Position: refs/heads/master@{#615456}

We limit the maximum number of rows shown by how many sites each category had to begin with (before any blacklisting occurs).

Bug: 911362
Change-Id: I35ac39870422248ae830050bb6ccf4f405960f4d
Reviewed-on: https://chromium-review.googlesource.com/c/1359694
Commit-Queue: Cathy Li <chili@chromium.org>
Reviewed-by: Justin DeWitt <dewittj@chromium.org>
Reviewed-by: Peter Williamson <petewil@chromium.org>
Cr-Commit-Position: refs/heads/master@{#615455}

This CL updates the FakePageHandler to use generated Mojo types.

Bug: 906508
Change-Id: Ib04a9118e7ad7de6ac1aa9dfdf2d232c3280034a
Reviewed-on: https://chromium-review.googlesource.com/c/1370232
Commit-Queue: Reka Norman <rekanorman@google.com>
Reviewed-by: calamity <calamity@chromium.org>
Cr-Commit-Position: refs/heads/master@{#615454}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/768c73895b2f..bdff670a66b9


git log 768c73895b2f..bdff670a66b9 --date=short --no-merges --format='%ad %ae %s'
2018-12-11 athilenius@google.com Added a find_project_path script, updated repo_manifest lib


Created with:
  gclient setdep -r src/third_party/chromite@bdff670a66b9

The AutoRoll server is located here: https://autoroll.skia.org/r/chromite-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=chrome-os-gardeners@chromium.org

Change-Id: I0d317d3eb531673796b8aa47ed41a98b4c2e69ca
Reviewed-on: https://chromium-review.googlesource.com/c/1371250Reviewed-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@{#615453}

BUG=913249

Change-Id: Icacda434b78bc09b85290734f888f914dc91d3ac
Reviewed-on: https://chromium-review.googlesource.com/c/1369547Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Simon Que <sque@chromium.org>
Cr-Commit-Position: refs/heads/master@{#615452}

Adds a method to SharedImage interface (SII) which allows us to create
a shared image and upload initial data in a single command. This method
is then used in LTHI to convert the UI Resource uploader code to SII.

As SII can't rely on the command buffer, it uses the following pattern
for uploads:
 - Allocate a 1MB (or required size) block of shared memory.
 - Sub allocate from it for each upload, duplicating the SHM and
   transferring ownership to the GPU service for each upload.
 - When the current shared memory buffer is used up, drop it on the
   client side. It will be kept alive by the duplicated handles passed
   to the service, until these are no longer needed.
 - Repeat.

This may be a bit inefficient, so we may need a more complex allocation
scheme in the future.

Bug: 906794
Change-Id: Ie91ab352b06097da6e00f80582b0cc92d690a6f9
Reviewed-on: https://chromium-review.googlesource.com/c/1343346
Commit-Queue: Eric Karl <ericrk@chromium.org>
Reviewed-by: Chris Palmer <palmer@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#615451}

Bug: 911036
Change-Id: I1096638e46760674d9c9a85522f775f767f0faa1
Reviewed-on: https://chromium-review.googlesource.com/c/1370234Reviewed-by: Makoto Shimazu <shimazu@chromium.org>
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#615450}

Bug: 913688
Change-Id: Ibd0124bd99389142c4538fdb6c55ca2c634f6f42
Reviewed-on: https://chromium-review.googlesource.com/c/1371164Reviewed-by: Dominick Ng <dominickn@chromium.org>
Commit-Queue: Sidney San Martín <sdy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#615449}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/f88410f8..5ca85e30

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=luci.chromium.try:linux-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,v8-waterfall-sheriff@grotations.appspotmail.com

Change-Id: Id130e26eed952d7d9ff0a64c0c19531612c22ce6
Reviewed-on: https://chromium-review.googlesource.com/c/1370859Reviewed-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@{#615448}

ResourceLoadScheduler was already launched, and enabled by default.
fieldtrial_testing_config.json does not need to have a configuration
for testing performance on the feature.

Bug: 729954
Change-Id: Ie7d468ad320980c857e3612dbff3f18cc2b74bd3
Reviewed-on: https://chromium-review.googlesource.com/c/1369550Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#615447}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/ea2cff61234c..d31d9e9af460


Created with:
  gclient setdep -r src-internal@d31d9e9af460

The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-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=mmoss@chromium.org

Change-Id: I886418486b60a062c29400f1d0663311c55ddfed
Reviewed-on: https://chromium-review.googlesource.com/c/1371249Reviewed-by: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#615446}

And remove blink::ToIsolate(ExecutionContext) altogether.

Originally https://chromium-review.googlesource.com/c/chromium/src/+/1355944
The difference is added checks in:
* AsyncTaskCanceled
* AllAsyncTasksCanceled
for nullptr ExecutionContext.

Bug: 889542, 911800
Change-Id: Icef90fadbc89019118119f044dde8f10ddffa72f
Reviewed-on: https://chromium-review.googlesource.com/c/1366358
Commit-Queue: Ryan Tseng <hinoka@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#615445}

This boundsForRange should return null in Non-arc, non-text nodes.
Otherwise, since bounds for these nodes exist (eg - on images),
highlighting for these would occur unexpectedly on select-to-speak side.

Test: Manual
Bug: 908509
Change-Id: I344a050a9033d7d839cb242b1fc56196ec28bcce
Reviewed-on: https://chromium-review.googlesource.com/c/1358105
Commit-Queue: Sara Kato <sarakato@chromium.org>
Reviewed-by: Yuki Awano <yawano@chromium.org>
Reviewed-by: David Tseng <dtseng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#615444}

Using wpt-import in Chromium 2bcd17a0.

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:
drott@chromium.org, kojii@chromium.org:
  external/wpt/css/css-fonts
eroman@chromium.org, rsleevi@chromium.org:
  external/wpt/WebCryptoAPI
foolip@chromium.org, robertma@chromium.org, smcgruer@chromium.org:
  external/wpt/infrastructure
ksakamoto@chromium.org:
  external/wpt/resource-timing
panicker@chromium.org:
  external/wpt/user-timing
rmcilroy@chromium.org:
  external/wpt/requestidlecallback
tdresser@chromium.org:
  external/wpt/hr-time
  external/wpt/navigation-timing
yhirano@chromium.org, mkwst@chromium.org, japhet@chromium.org:
  external/wpt/fetch

NOAUTOREVERT=true
TBR=robertma

No-Export: true
Change-Id: I3a940f1891ee1fab3deac0ed104cc1c7a66bd1ca
Reviewed-on: https://chromium-review.googlesource.com/c/1371217Reviewed-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@{#615443}

For now ViewportProperties contains the page scale node only, and
Settings contains prefer_compositing_to_lcd_text only. In the future
they will contain more properties/settings.

Change-Id: I760b79191aa25a8fc489aa9c4d9ab1dc1e6204fc
Reviewed-on: https://chromium-review.googlesource.com/c/1370278Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#615442}

Some interfaces depend on many other interfaces. Before this patch users
would have to manually add externs for every interface used.

This CL introduces a new target that js_libraries can use to include
all the necessary externs to use an interface.

Bug: 849993
Change-Id: I97acb7bbbd604e7ebeb1cb5fe814e4afecefe2d6
Reviewed-on: https://chromium-review.googlesource.com/c/1369485Reviewed-by: Ken Rockot <rockot@google.com>
Reviewed-by: calamity <calamity@chromium.org>
Commit-Queue: Giovanni Ortuño Urquidi <ortuno@chromium.org>
Cr-Commit-Position: refs/heads/master@{#615441}

Remove the following tests:
- fetch-canvas-tainting.html
- fetch-cors-xhr.html
- fetch-csp.html

These are redundant with corresponding WPT tests. They previously could
not be removed without losing test coverage because the WPT tests were
being skipped due to time outs, see
https://codereview.chromium.org/2805313003/. But those WPT tests are now
passing. A small exception is the WPT fetch-canvas-tainting* tests
flakily timeout, but they are still enabled and mostly passing so we
won't lose test coverage.

These tests were originally written at r179595 and upstreamed to WPT
at https://github.com/web-platform-tests/wpt/commit/b2e3ab765e26436850208dbdcf747c3be75b1999.

Bug: 688116, 373120
Change-Id: Ic2dc2ddc322aae89b1e06e5a16b1ed8c30265d00
Reviewed-on: https://chromium-review.googlesource.com/c/1370236Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Commit-Queue: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#615440}

ios webview uses butter sync which does not need overall sync consent
because it will never be enabled.

Bug: 873790
Change-Id: Id6f6dfd6ebd424f2d3c385a85f425171d03ef1d9
Reviewed-on: https://chromium-review.googlesource.com/c/1371203
Commit-Queue: John Wu <jzw@chromium.org>
Reviewed-by: Hiroshi Ichikawa <ichikawa@chromium.org>
Cr-Commit-Position: refs/heads/master@{#615439}

A new flag was added recently that prevented server cards from being
offered as autofill suggestions. We simply enable to restore the
intended behavior.

Change-Id: I537ae79a6bf6acfef081f9002654e4d4fc202fe5
Reviewed-on: https://chromium-review.googlesource.com/c/1371202
Commit-Queue: John Wu <jzw@chromium.org>
Reviewed-by: Hiroshi Ichikawa <ichikawa@chromium.org>
Cr-Commit-Position: refs/heads/master@{#615438}

MetadataBoxController uses the availability of externalFileUrl in file
metadata to decide whether to obtain metadata via
ExternalMetadataProvider or by reading the file. With DriveFS,
externalFileUrl is not set but ExternalMetadataProvider should be used
for fetching metadata. Also use alternateUrl (which is only set for
Drive files) to detect files where this metadata provider should be
used.

Also skip FSP metadata requests when none of the metadata fields are
available via the FSP API.

Bug: 913738, 587231
Change-Id: I95636e6bcf1d21cea3366d17363ab6300b1d59f8
Reviewed-on: https://chromium-review.googlesource.com/c/1370154
Commit-Queue: Sam McNally <sammc@chromium.org>
Reviewed-by: Luciano Pacheco <lucmult@chromium.org>
Cr-Commit-Position: refs/heads/master@{#615437}

This allows the job to use userdata.qcow in the user's /home.

BUG=b:118408409
TEST=sign in, confirm the job is running

Change-Id: I1bcb5ff1cfcae06a7ce404b17ffd2c329419736e
Reviewed-on: https://chromium-review.googlesource.com/c/1367085Reviewed-by: Hidehiko Abe <hidehiko@chromium.org>
Commit-Queue: Yusuke Sato <yusukes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#615436}