GitLab

Remove WebCORS::ListOfCORSEnabledURLSchemes() and
WebCORS::ContainsOnlyCORSSafelistedOrForbiddenHeaders() since
these methods won't be used by CORSURLLoader in favor of OOR-CORS
efforts.

Also move IsForbiddenHeaderName(), ContainsOnlyCORSSafelistedHeaders(),
and ContainsOnlyCORSSafelistedOrForbiddenHeaders() from FetchUtils
to CORS since they are CORS related thin wrapper methods to call
network::cors functions.

FetchUtils::IsOkStatus is also moved to CORS, and implementation is
placed at network::cors to reuse the same implementation in the
Network Service.

All changes are mechanical, and should not introduce any behavior
change.

Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: Ibffd079162ce2b79742deeeba66bd7449defce5d
Tbr: haraken@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/1005134
Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551270}

The WebAssembly spec [1] requires that a TypeError is thrown if the
status of the Response input of streaming compilation is not ok.

I added layout tests for this, and cleaned up the surrounding tests a
bit.


[1] https://github.com/WebAssembly/design/blob/master/Web.md#webassemblycompilestreaming

R=mlippautz@chromium.org, mathias@chromium.org

also-by: mathias@chromium.org
Bug: chromium:832552
Change-Id: Icd50e537ab659662708274a96959eb94d7fbc554
Reviewed-on: https://chromium-review.googlesource.com/1012035Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Commit-Queue: Andreas Haas <ahaas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551269}

The legacy IPC audio messages have been replaced by mojo interfaces.
This CL also removes related experiment configs.

Comments are also updated (diff against PS1), except for comments in
audio_mirroring_manager.h, since that one is soon to be removed. A more
comprehensive md file should be written when the audio service
situation has settled a bit.

Bug: 653871,721732
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;luci.chromium.try:win_optional_gpu_tests_rel
Change-Id: Ia67ffe766802adec971b41dfc0593be61909175a
Reviewed-on: https://chromium-review.googlesource.com/1010424Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Reviewed-by: Olga Sharonova <olka@chromium.org>
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Reviewed-by: Yuri Wiitala <miu@chromium.org>
Reviewed-by: Jesse Doherty <jwd@chromium.org>
Commit-Queue: Max Morin <maxmorin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551268}

This CL adds test coverage regarding an extension frame's ability to embed a
file frame. This ensures than an extension can only embed a file frame if it has
explicit file access and host permissions to the file scheme.

BUG=816685

Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: I8d167d9a8629ffece29d44bee4bd6db2ef988b02
Reviewed-on: https://chromium-review.googlesource.com/1003762
Commit-Queue: Karan Bhatia <karandeepb@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551267}

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: I7e2a0accac4ad76d4a2a00b197bd3d66024b19af
Reviewed-on: https://chromium-review.googlesource.com/1014566
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@{#551266}

The disable_flip added in CL:960403 mistakenly disables inclusion
of LocalClipPathBoundingBox. This patch fixes the logic only to
disable block flipping.

Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: I6617ddf1d852cd9d98dcaa86d6926d01a5e7af8c
Reviewed-on: https://chromium-review.googlesource.com/1013805Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551265}

Extract some more common code into WebFrameWidgetBase. The end goal is
to completely merge WebFrameWidgetImpl and WebViewFrameWidget into
WebFrameWidgetBase. This is an intermediate step to make it easier to
create the frame widget before creating the local frame root: by sharing
storage in the base class, the followup patch to invert creation order
will only have to update pointers in one place.

Bug: 820787
Change-Id: I5f096c8a8d74abb6b6773ff36c75288b998d3880
Reviewed-on: https://chromium-review.googlesource.com/1014017Reviewed-by: Albert J. Wong <ajwong@chromium.org>
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551264}

U+04CF (ӏ) has the confusability skeleton of 'i' (lowercase
I), but it can be confused for 'l' (lowercase L) or '1' (digit) if rendered
in some fonts.

If a host name contains it, calculate the confusability skeleton
twice, once with the default mapping to 'i' (lowercase I) and the 2nd
time with an alternative mapping to 'l'. Mapping them to 'l' (lowercase L)
also gets it treated as similar to digit 1 because the confusability
skeleton of digit 1 is 'l'.

Bug: 817247
Test: components_unittests --gtest_filter=*IDN*
Change-Id: I7442b950c9457eea285e17f01d1f43c9acc5d79c
Reviewed-on: https://chromium-review.googlesource.com/974165
Commit-Queue: Jungshik Shin <jshin@chromium.org>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Reviewed-by: Eric Lawrence <elawrence@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551263}

This fixes a memory leak and renderer crash as described below.

Change Cache Storage "open" method callback to have a WeakPersistent
reference to CacheStorage to avoid a circular reference between them.
Remove Persistent<CacheStorage> from callback for "delete" since it
wasn't used.

WebServiceWorkerCacheStorageImpl keeps the callback while waiting for
mojo response from browser process which keeps CacheStorage alive,
CacheStorage also has a reference to WebServiceWQorkerCacheStorage,
which is implemented by WebServiceCacheStorageImpl, creating the
circular reference, this situation leads to memory leak because those
can't be garbage collected properly on some termination conditions,
this leak in turn would cause renderer to crash when starting a new
worker and trying to reuse pointer to address cleaned by Oilpan heap.

When a worker is terminated with pending WithCacheCallback objects,
the termination GC callback will access the Persistent handle. However,
it will point to an object in a dead Oilpan heap and cause a segfault.

Using a WeakPersistent is a workaround to prevent this crash, since
the termination GC callback won't try to access it. In the future,
Oilpan might be updated to handle this more gracefully see
https://crbug.com/831117.

The added test catches two conditions where renderer process was
crashing:
1. When initializing Cache Storage after "close()".
2. Initializing Cache Storage before "close()" and issuing new calls,
that trigger mojo after "close()".

Bug: 831054
Change-Id: I6620d8107c00aed1c386c869dc1a793bc51d97fa
Reviewed-on: https://chromium-review.googlesource.com/1011467
Commit-Queue: Luciano Pacheco (SYD) <lucmult@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551262}

Browser doesn't commit navigation if server responds HTTP 204 / HTTP 205
for the main resource or if navigation triggers a download.

In these cases, navigation is considered aborted.

This patch teaches page.navigate to return "ERR:ABORTED" when
either of the usecases happens.

R=dgozman, pfeldman

Change-Id: I0017e458c2f905429c7234bc8f9be20a4201bbfd
Reviewed-on: https://chromium-review.googlesource.com/1009487Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Reviewed-by: Camille Lamy <clamy@chromium.org>
Commit-Queue: Andrey Lushnikov <lushnikov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551261}

Bug: 824715
Change-Id: I71d7f38a2dbe9de6515b8e9d284ab622c2311276
Reviewed-on: https://chromium-review.googlesource.com/1014367
Commit-Queue: Matt Giuca <mgiuca@chromium.org>
Reviewed-by: Matt Giuca <mgiuca@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551260}

See go/closure-compile-gn for details.

This CL converts the Closure Compilation from GYP to GN for the following:
- cryptotoken
- download_internals
- md_downloads
- md_extensions
- md_history
- md_user_manager
- offline_pages
- signin
- webapks
- welcome

A local closure compile can be run by setting closure_compile = true in
args.gn, and then running ninja -C out/Default webui_closure_compile.
Individual projects can be compiled via, for example,
ninja -C out/Default chrome/browser/resources/md_extensions:closure_compile

Relanding with a fix for android builds.

TBR=calamity@chromium.org,dpapad@chromium.org,ntfschr@chromium.org

Bug: 632206, 833550
Change-Id: I197201fe9cd06153cce18a8e6243d6fd189f1087
Reviewed-on: https://chromium-review.googlesource.com/1013801
Commit-Queue: calamity <calamity@chromium.org>
Reviewed-by: Nate Fischer <ntfschr@chromium.org>
Reviewed-by: calamity <calamity@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551259}

This reverts commit c4334bc5.

Reason for revert: Caused crashes when storing javascript modules in cache storage. https://crbug.com/832202

Original change's description:
> Enable ServiceWorkerScriptFullCodeCache by default
> 
> Bug: 768705,788619
> Change-Id: I18474261a0bb443b5ed7186adb8bc68227ece26c
> Reviewed-on: https://chromium-review.googlesource.com/994492
> Commit-Queue: Tsuyoshi Horo <horo@chromium.org>
> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#547946}

TBR=horo@chromium.org,kinuko@chromium.org

# Not skipping CQ checks because original CL landed > 1 day ago.

Bug: 768705, 788619, 832202
Change-Id: I53d3a401dfb83fbf54184588ca889b1a4f9f0474
Reviewed-on: https://chromium-review.googlesource.com/1014310Reviewed-by: Tsuyoshi Horo <horo@chromium.org>
Commit-Queue: Tsuyoshi Horo <horo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551258}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/38262cca..b08b074b

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: I6094c8bafa10382de5ffe1d86bcc422fc8f9f641
Reviewed-on: https://chromium-review.googlesource.com/1014323Reviewed-by: v8 autoroll <v8-autoroll@chromium.org>
Commit-Queue: v8 autoroll <v8-autoroll@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551257}

This CL changes MojoWebUIController to use a templated
AddHandlerToRegistry function which allows subclasses to add multiple
interfaces to the binder registry.

TBR=khorimoto@chromium.org

Change-Id: I943e3d583c9a3c8bb08873001cc533c2d23a0bcf
Reviewed-on: https://chromium-review.googlesource.com/991497
Commit-Queue: calamity <calamity@chromium.org>
Reviewed-by: calamity <calamity@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Reviewed-by: Ken Rockot <rockot@chromium.org>
Reviewed-by: Sam McNally <sammc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551256}

Bug: 821261
Change-Id: If9e14e0f503839955c159da7e18d402e50d0875b
Reviewed-on: https://chromium-review.googlesource.com/1013021Reviewed-by: Shinya Kawanaka <shinyak@chromium.org>
Reviewed-by: Ryan Tseng <hinoka@chromium.org>
Commit-Queue: Fumitoshi Ukai <ukai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551255}

This avoids large bitmaps yielding large messages, as BigBuffer falls
back onto shared memory beyond a certain size threshold.

Bug: 829659
Cq-Include-Trybots: luci.chromium.try:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win10_chromium_x64_rel_ng
Change-Id: I82f907144944f2e8ebea51264fc00afc171ce3bf
Reviewed-on: https://chromium-review.googlesource.com/1004598
Commit-Queue: Ken Rockot <rockot@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Mike Klein <mtklein@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551254}

changes:
Remove ShowAccessibilityNotification in AccessibilityObserver. That is
only used in TrayAccessibility, while TrayAccessibility should be pure
views code. Move the function and tests to AccessibilityController.

Bug: 800270
Test: covered by tests
Change-Id: I0551c8b36d1a4bfb030b786bd78d610627113828
Reviewed-on: https://chromium-review.googlesource.com/1007891Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Qiang Xu <warx@google.com>
Cr-Commit-Position: refs/heads/master@{#551253}

VDA client can request Flush() after Reset() and waits for NotifyFlushDone().
After FinishReset() is done, input stream becomes off. Even doing V4L2_DEC_CMD_STOP
at this time, the buffer with V4L2_BUF_FLAG_LAST will never be returned from
driver. As a result, NotifyFlushDone() will not be invoked and client waits
permanently.
To avoid this, V4L2VDA is changed as it tries to call NotifyFlushDone if input
stream is off.

BUG=chromium:833223, chromium:833221
TEST=Change resolution manually on crosvideo.appspot.com
TEST=VDA unittest on hana
TEST=CtsMediaTestCases on hana

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: I4245bdcee1e537dc7061e7833530ae59fc4aecb7
Reviewed-on: https://chromium-review.googlesource.com/1013787
Commit-Queue: Hirokazu Honda <hiroh@chromium.org>
Reviewed-by: Pawel Osciak <posciak@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551252}

Migrate MessageLoop::ScopedNestableTaskAllower to RunLoop::Type::kNestableTasksAllowed in /third_party/blink/renderer/platform/scheduler/child

This is another scripted pass done by a slightly modified version of
https://bugs.chromium.org/p/chromium/issues/detail?id=781352#c1 which
has a better notion of "scope".

The script should have replaced a MessageLoop::ScopedNestableTaskAllower
in the same scope as a RunLoop with a RunLoop of
Type::kNestableTasksAllowed.

Includes should have been stripped if that was the last usage of message_loop.h
in that file.

Please CQ if LGTY

This CL was uploaded by git cl split.

R=alexclarke@chromium.org

Bug: 781352
Change-Id: I3ffef78836b7c4ffe22be0bc8043c39d9397729f
Reviewed-on: https://chromium-review.googlesource.com/1013216Reviewed-by: Alex Clarke <alexclarke@chromium.org>
Reviewed-by: Alexander Timin <altimin@chromium.org>
Commit-Queue: Alexander Timin <altimin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551251}

Migrate MessageLoop::ScopedNestableTaskAllower to RunLoop::Type::kNestableTasksAllowed in /third_party/blink/renderer/platform/scheduler

This is another scripted pass done by a slightly modified version of
https://bugs.chromium.org/p/chromium/issues/detail?id=781352#c1 which
has a better notion of "scope".

The script should have replaced a MessageLoop::ScopedNestableTaskAllower
in the same scope as a RunLoop with a RunLoop of
Type::kNestableTasksAllowed.

Includes should have been stripped if that was the last usage of message_loop.h
in that file.

Please CQ if LGTY

This CL was uploaded by git cl split.

R=altimin@chromium.org

Bug: 781352
Change-Id: I471d4462277bf67332939a1cfce7f6f17d642cc7
Reviewed-on: https://chromium-review.googlesource.com/1013214
Commit-Queue: Alexander Timin <altimin@chromium.org>
Reviewed-by: Alexander Timin <altimin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551250}

The current ng_caret_rect.h/cc contains two different parts:
1. Computation of NGCaretPosition
2. Conversion from NGCaretPosition to LocalCaretRect

The two parts are very different that, NGCaretPosition is a building
block of other Layout NG components (e.g., ng_line_utils), while
LocalCaretRect is only passed to legacy.

For better code health, this patch splits them into different files.

Bug: 822575
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: I1dbc1b683d54c2f066cf84c21e7388bb07f8e3f1
Reviewed-on: https://chromium-review.googlesource.com/1014800Reviewed-by: Koji Ishii <kojii@chromium.org>
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551249}

Need to DCHECK has_brightness, instead of DCHECKing brightness itself.

Bug: 833692
Change-Id: I1f3f6667f4b3ae83e1bbbd30402864a539581390
Reviewed-on: https://chromium-review.googlesource.com/1013847Reviewed-by: Jia Meng <jiameng@chromium.org>
Reviewed-by: Dan Erat <derat@chromium.org>
Commit-Queue: Paul Dyson <pdyson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551248}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/90906cbf2fc5..745ac35bed03

$ git log 90906cbf2..745ac35be --date=short --no-merges --format='%ad %ae %s'
2018-04-13 pwang autotest_quick_merge: Follow the symlink

Created with:
  roll-dep src/third_party/chromite
BUG=chromium:832564


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

Change-Id: Ia6c5df358bae5acea0588fe9dcf9ae70528d0621
Reviewed-on: https://chromium-review.googlesource.com/1014674Reviewed-by: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#551247}

This fixes S13nSW specific failures on
external/wpt/service-workers/service-worker/fetch-canvas-tainting-video-cache.https.html.
Note that "fix" here means that the result would be the same as
non-S13nSW. There are still some failures on the test page.

Bug: 833241
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: I8c6dce03475cc50f0fb8900b73a8d7407606f170
Reviewed-on: https://chromium-review.googlesource.com/1013362Reviewed-by: Daniel Murphy <dmurph@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Commit-Queue: Kenichi Ishibashi <bashi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551246}

Change DiskMountManagerImpl's "Found disk" warning messages
to DVLOG(1). I don't think that these indicate problems.

Bug: 826990
Change-Id: I60a8ae1e032d209f4649d774ee4fb60d91842197
Reviewed-on: https://chromium-review.googlesource.com/1014376Reviewed-by: Ryo Hashimoto <hashimoto@chromium.org>
Commit-Queue: Dan Erat <derat@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551245}

Add a dbus client method for the DestroyDiskImage Concierge service. Add a method to CorstiniManager to check the input. This is not used yet. Will be used in my next CL which adds a button in the Settings page to delete Crostini VMs.

Bug: 833125

Change-Id: I6dd817a23764b484f4ac507adb0566ccbfeac5df
Reviewed-on: https://chromium-review.googlesource.com/1013657Reviewed-by: Ryo Hashimoto <hashimoto@chromium.org>
Reviewed-by: Nicholas Verne <nverne@chromium.org>
Commit-Queue: Renée Wright <rjwright@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551244}

Also remove checks for |ServiceWorkerContextCore::observer_list_| being
NULL. That cannot happen.

BUG=558179

Change-Id: I33685dd6d113aab2e6d2fbe85c62365131fc07d3
Reviewed-on: https://chromium-review.googlesource.com/1014659Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551243}

This CL is a refactor with no intended behavior change outside of tests.

Test behavior change:
* TestDriver::CheckOrStartProfiling now waits for the allocator shim to be
  initialized even if profiling was enabled for the current process via command
  line flags. This is because initialization is asynchronous.
* TestDriver::ValidateRendererAllocations no longer makes any checks if the
  renderer is not being profiled, since on Android WebView there may not even be
  a renderer process in this case.

Refactor:
* Moves the C++ side of the android test shim into components/heap_profiling, so
  that the logic can be shared with Android Webview.
* Renames the test shim from TestAndroidShim to HeapProfilingTestShim.
* Removes redundant checks in TestDriver::ValidateRendererAllocations.

Change-Id: I4755f6169b0f9c556a86005916aa9150dec6853b
BUG: 827545
Reviewed-on: https://chromium-review.googlesource.com/1012542Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Erik Chen <erikchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551242}

Move check-webkit-style and lint-webkitpy from //third_party/WebKit/Tools/Scripts to //third_party/blink/tools.

This CL also adds add_webkitpy.py to blinkpy/common.

Bug: 829697
Change-Id: I592d0b2c5076bc89ee30fa6a7afbb15e8cb77319
Reviewed-on: https://chromium-review.googlesource.com/1013820
Commit-Queue: Kent Tamura <tkent@chromium.org>
Reviewed-by: Quinten Yearsley <qyearsley@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551241}

The above mentioned function is symmetric when adjusting left and right
edge of an inline box.

This patch enforces the symmetry by unifying the algorithms with a
template. It is also preparation for crrev.com/c/997134.

Bug: 822575
Change-Id: Iacb6a77c3e43c598d2405d7f859e5f619e138a0b
Reviewed-on: https://chromium-review.googlesource.com/1013059
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Reviewed-by: Yoichi Osato <yoichio@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551240}

The clang tot bots moved off chromium.fyi to chromium.clang a while
ago, and the testers were removed altogether since all the tests
now run on swarming and can hence be triggered by the builder.

Bug: none
Change-Id: Ie6951241a375d397d98768811483a522ac589ad7
Reviewed-on: https://chromium-review.googlesource.com/1013611
Commit-Queue: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551239}

Related spec change:
  https://github.com/w3c/payment-handler/pull/294

Bug: 833530
Change-Id: I65d0e01bb5b6bfdd44925b90ba98837161cc136b
Reviewed-on: https://chromium-review.googlesource.com/1013664Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
Commit-Queue: Jinho Bang <jinho.bang@samsung.com>
Cr-Commit-Position: refs/heads/master@{#551238}

See the comments in the patch for why this is necessary.

R=eae@chromium.org, ikilpatrick@chromium.org

Bug: 635619
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: I0a4042c0782c98fab1bfd27cb3bf6ca29c820542
Reviewed-on: https://chromium-review.googlesource.com/1013306Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551237}

Using wpt-import in Chromium 6d63741e.
With Chromium commits locally applied on WPT:
303956b6 "Enable WPT tests for the Generic Sensor classes"


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

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:
jsbell@chromium.org:
  external/wpt/service-workers/cache-storage

TBR=raphael.kubo.da.costa@intel.com

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

This reverts commit 5f77b73e.

Reason for revert: Roll has landed, reinstating tests.

Original change's description:
> Temporarily disable angle_vulkan_deqp_tests.
> 
> Unblocks the Vulkan roll.
> 
> Bug: angleproject:2482
> 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: I9577f331977e9add28bb7875e70260d428ad0cd5
> Tbr: kbr@chromium.org
> No-try: True
> Reviewed-on: https://chromium-review.googlesource.com/1014322
> Reviewed-by: Jamie Madill <jmadill@chromium.org>
> Commit-Queue: Jamie Madill <jmadill@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#551102}

TBR=jmadill@chromium.org,kbr@chromium.org

Change-Id: Iab80706a6e74c442533d4df60c753e7dc270c380
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: angleproject:2482
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
Reviewed-on: https://chromium-review.googlesource.com/1014726Reviewed-by: Jamie Madill <jmadill@chromium.org>
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551235}

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

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

Turn off FileManagerUITests from CQ until current audit
of tests by noel@ is complete.

Bug: 819478
Change-Id: I14dca567de4fb7919d94b1d89a0cb2dada5b8d67
Reviewed-on: https://chromium-review.googlesource.com/1013668Reviewed-by: Sasha Morrissey <sashab@chromium.org>
Commit-Queue: Joel Hockey <joelhockey@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551233}

https://chromium.googlesource.com/angle/angle.git/+log/aa8b3982aeeb..08b9e046c1b6

$ git log aa8b3982a..08b9e046c --date=short --no-merges --format='%ad %ae %s'
2018-04-16 jmadill Vulkan: Disable warning in Mock ICD.
2018-04-16 tobine Roll (2/2) to latest LVL as of 4/16/18

Created with:
  roll-dep src/third_party/angle


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=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
TBR=jmadill@chromium.org

No-Try: True
Change-Id: I34309b2c8fc6f4d49ba465929378687aaaa181a1
Reviewed-on: https://chromium-review.googlesource.com/1014671
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Reviewed-by: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#551232}

Impending changes to Mojo IPC will require that handles serialized
as shared memory handles are actually shared memory handles. DXGI
resources are not, but are being transported using
GpuMemoryBufferHandle's shared_memory field.

This introduces a Windows-only GpuMemoryBufferHandle field for a
generic HANDLE to be used for DXGI resources, as well as a corresponding
mojom field for the same purpose.

There should be no net effect on the behavior of the system wrt handle
lifetime or usage.


Bug: 826213
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;master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2;luci.chromium.try:win_optional_gpu_tests_rel
Change-Id: I5d510e0ebdb60d4872fc428a95ce681dd18369dc
Reviewed-on: https://chromium-review.googlesource.com/1011600Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Sunny Sachanandani <sunnyps@chromium.org>
Reviewed-by: Bill Orr <billorr@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: David Reveman <reveman@chromium.org>
Commit-Queue: Ken Rockot <rockot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551231}