GitLab

The test file doesn't need to be so large, and the size exceeds a limit
under Fuchsia, breaking the test.

Bug: 771429
Change-Id: I8421843fe43b66a3e769d70e6cb626d7b60ec040
Reviewed-on: https://chromium-review.googlesource.com/699597Reviewed-by: Ken Rockot <rockot@chromium.org>
Commit-Queue: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506457}

Makes it easier to see that we have a lot of slow tests in DevTools :(

Bug: 667560
Change-Id: I6f09032d3f34502ea117480f1cf94f995c368052
Reviewed-on: https://chromium-review.googlesource.com/692979
Commit-Queue: Will Chen <chenwilliam@chromium.org>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506456}

Since the spellchecker code has been migrated from the FILE
thread to TaskScheduler, tests need to use
content::RunAllTasksUntilIdle() instead of
base::RunLoop().RunUntilIdle() to wait for all spellchecker-related
tasks to run.

Bug: 770653
Change-Id: I8c4ac0e1183d8e11b8d60e334140e1fc1066d787
Reviewed-on: https://chromium-review.googlesource.com/695835Reviewed-by: Rachel Blum <groby@chromium.org>
Commit-Queue: François Doray <fdoray@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506455}

I've been testing the changes on net_parse_cookie_line_fuzzer,
which is a fuzz target of average size written in C++.

Improvements step by step:

0) Original configuration, Coverage + ASan:
158 MB  1,000 exec/s

1) Prohibit ASan (and other sanitizers), use only Coverage instrumentation:
132 MB  same speed

The following change hasn't been applied, but let's keep it in the description FTR:
- 2) Disable sanitizer coverage (which is different from clang source-based coverage):
- 90 MB   1,088 exec/s (speed +8-10%)

3) Avoid optimize_for_fuzzing config (i.e. use -O3 instead of -O1 for coverage build):
Same size  1,773 exec/s (speed +60-65% on top of the previous change)

4) Disable coverage for libFuzzer source code:
88 MB  3,988 exec/s (speed +125% on top of previous changes)

5) Disable coverage for libc++ and libc++abi sources
(https://chromium-review.googlesource.com/#/c/chromium/buildtools/+/693570):
86 MB  4,110 exec/s (speed +3% on top of previous changes)

In total, for that particular target:
- build size reduced by ~45%
- execution speed increased by ~310%

I've also tested the changes with zlib_uncompress_fuzzer (a tiny fuzz target for C-library):
- build size reduced by ~83%
- execution speed increased by ~120%

I haven't measured impact on the other fuzz targets, so it may vary a lot,
but the result seems to be quite significant anyway.


Bug: 759794
Change-Id: Icf61c979e38d0f7849ab7281bd9e24cf2b7a7d02
Reviewed-on: https://chromium-review.googlesource.com/693564Reviewed-by: Brett Wilson <brettw@chromium.org>
Reviewed-by: Oliver Chang <ochang@chromium.org>
Commit-Queue: Abhishek Arya <inferno@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506454}

GetTaskRunner() will crash with a nullptr ExecutionContext, and all the
other work is nonsensical in the absence of an ExecutionContext.

Bug: 763040
Change-Id: Ide915c02265e35e55c7dc5aa234652efc5016b55
Reviewed-on: https://chromium-review.googlesource.com/698606
Commit-Queue: Nate Chapin <japhet@chromium.org>
Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506453}

Moves upload bytes out of the for-loop to use less memory on the stack.

Bug: 771366
Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester
Change-Id: Icc1e20c8c6191f13c8889324699fd47bf8a1108c
Reviewed-on: https://chromium-review.googlesource.com/700482
Commit-Queue: Helen Li <xunjieli@chromium.org>
Reviewed-by: Andrei Kapishnikov <kapishnikov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506452}

This CL makes WebApkUpdateManager store the "WebAPK update request" to disk and
retrieve it from disk once the WebApkActivity is ready to do the update (Once
the WebApkActivity is in the background). This CL is in preparation for
https://codereview.chromium.org/2948713002/ The "WebAPK update request" cannot
be encoded as an extra on com.google.android.gms.gcm.Task#setExtras() because
GCMNetworkManager limits the total size of the extras to 10KB. We might send up
to two PNG images as part of an update request

BUG=713655

Change-Id: I9d86eb8ffe4f650340028ec6c4d12a7b8ddc1aec
Reviewed-on: https://chromium-review.googlesource.com/581231
Commit-Queue: Peter Kotwicz <pkotwicz@chromium.org>
Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506451}

Create a separate thread for the compositor. Use the thread the GpuMain
instance is created on as the thread for the GpuService. This allows
using it in content (in GpuChildThread), where the main thread is used
for the gpu service.

For the mus window server, until the gpu process-split happens, create
a separate thread for the gpu service from the DefaultGpuHost. After
the process split, the main thread of the new process can be used for
the gpu service (like GpuChildThread in content).

BUG=730213

Change-Id: I02eb4fef21bfbdac92201c35b96ac15473a43567
Reviewed-on: https://chromium-review.googlesource.com/693075Reviewed-by: kylechar <kylechar@chromium.org>
Reviewed-by: Fady Samuel <fsamuel@chromium.org>
Commit-Queue: Sadrul Chowdhury <sadrul@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506450}

There was previously a rare race condition in which trace events would
arrive in a different order, breaking this test.

We don't actually care about the ordering of these events, so we no
longer verify their order.

Bug: 736836
Change-Id: Iabb65f603c7fbb985faa97f43a65a5313711c53f
Reviewed-on: https://chromium-review.googlesource.com/700714Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Commit-Queue: Timothy Dresser <tdresser@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506449}

WebContents::GetRenderProcessHost is an API that doesn't behave as
expected with out-of-process iframes, as multiple processes can be
associated with a single WebContents.  This CL replaces callers of this
API, so that they go through an equivalent API that explicitly selects
which frame's process is needed.

This CL was started by using an ad-hoc clang-plugin that replaced
existing callsites of WebContents::GetRenderProcessHost() with a call to
something like wc->GetMainFrame()->GetProcess().  This was followed-up
by manually adding an include of render_frame_host.h and git cl format
and git cl lint and then a self-review with small tweaks (e.g. sometimes
using a wc->GetRenderViewHost()->GetProcess() is more appropriate).

This CL was uploaded by git cl split.

R=cylee@chromium.org

Bug: 666525
Change-Id: I08c5ee78b78aa268e37fe78651b915b12da0f635
Reviewed-on: https://chromium-review.googlesource.com/689024Reviewed-by: Cheng-Yu Lee <cylee@chromium.org>
Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506448}

instead of separate *Result functions. This is made possible by Mojo,
and resolves a TODO.

Bug: none
Change-Id: I5c1cda056b18beb0d9a2354078c05dffe5823c02
Reviewed-on: https://chromium-review.googlesource.com/695227
Commit-Queue: Marc Treib <treib@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506447}

This is a reland of b123ea27
Original change's description:
> applist-focus: Handle arrow key focus traversal
>
> Changes:
> 1. Enable arrow key focus handling in FocusManager.
> 2. Handle arrow up/down in SearchBoxView to move focus to the first/last
>    focusable element in ContentsView.
> 3. Handle arrow up/down in AppsGridView. AppsGridView has three states:
>    Peeking, Fullscreen all apps (outside folder) and Fullscreen all apps
>    (inside folder). Do separate handling for them, since they have
>    different layout.
>
> Design Doc: go/applist-focus
>
> BUG=766810
> TEST=AppListViewFocusTest.*
>
> Change-Id: I2ace4b3b21a69f10011eba2ed0079e1f7aee48d0
> Reviewed-on: https://chromium-review.googlesource.com/687818
> Commit-Queue: Weidong Guo <weidongg@chromium.org>
> Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#504818}

Bug: 766810
Change-Id: Ie7bb141fe052531cc249ed3df5bd70ed2fc2fdbd
Reviewed-on: https://chromium-review.googlesource.com/688808
Commit-Queue: Weidong Guo <weidongg@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506446}

When the savePreviousDocumentResources experiment is enabled, don't bother saving
resources for cross-origin navigations, since they are more likely to end up in
a different process, and will be very unlikely to share resources with the
current Document anyway.

Bug: 766653
Change-Id: I7facbf4239e482f11df8602ce72a5f1908eafd9a
Reviewed-on: https://chromium-review.googlesource.com/692679Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: Nate Chapin <japhet@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506445}

Bug: 
Change-Id: I833e04b125e557111e7301fd636555b38d73b575
Reviewed-on: https://chromium-review.googlesource.com/696324Reviewed-by: Mike West <mkwst@chromium.org>
Commit-Queue: Nate Chapin <japhet@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506444}

Bug: 758630
Change-Id: I38955c789d3cc360ac73d5eb080e66965ca117e3
Reviewed-on: https://chromium-review.googlesource.com/699023Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Stephen Martinis <martiniss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506443}

This CL limits the state that FirstRunActivity restores to the state sent via
FirstRunFlowSequencer#createGenericFirstRunIntent(). This enables
deleting the FirstRunActivity#EXTRA_USE_FRE_FLOW_SEQUENCER and
FirstRunActivity#POST_NATIVE_SETUP_NEEDED extras

Bug=755646

Change-Id: I1a8f4dd7c13ab5649ac2656e5a0b20c34b875e90
Reviewed-on: https://chromium-review.googlesource.com/670359Reviewed-by: Boris Sazonov <bsazonov@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Peter Kotwicz <pkotwicz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506442}

BUG=717091

Change-Id: Iaa193a2c59c61846535b5686f234cf3022f2c24e
Reviewed-on: https://chromium-review.googlesource.com/678510
Commit-Queue: Scott Violet <sky@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506441}

This removes the mac sandbox libraries dependency on //base. 
The dependency was causing the Chromium Helper binary to be 
linked against everything //base uses 
(AppKit, Security.framework, etc.), which is bad for security 
because of the resource access that happens in those libraries 
initializers.

Bug: 757577
Change-Id: I4699b9cd490c188e1659932e5c97621e37438f32
Reviewed-on: https://chromium-review.googlesource.com/676262
Commit-Queue: Greg Kerr <kerrnel@chromium.org>
Reviewed-by: Mark Mentovai <mark@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506440}

clang_tot_msan_release_bot was renamed in #506239.

BUG=765859
TBR=dpranke

Change-Id: I865b202422bc626c98bfca70338ad4e8650aa7cf
Reviewed-on: https://chromium-review.googlesource.com/699642Reviewed-by: Hans Wennborg <hans@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506439}

This reverts commit 33b53b7f.

Original change's description:
> Add browser_tests for WebAssembly out-of-bounds behavior
>
> Trap-based bounds checking requires interaction with the crash reporter
> to catch out of bounds accesses. These browser tests make sure this
> behavior is working in the context of a full Chrome browser.
>
> Bug: chromium:722585
> Change-Id: I1993540f85f5d3500681cd3fbd7a9af817fe4ce8
> Reviewed-on: https://chromium-review.googlesource.com/648363
> Commit-Queue: Eric Holk <eholk@chromium.org>
> Reviewed-by: Scott Violet <sky@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#503907}

Change-Id: I32b968177873c1c462c406a23a92dfc8cd27470c
Reviewed-on: https://chromium-review.googlesource.com/696293Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Eric Holk <eholk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506438}

Previously, the Password Manager would suggest adding username
autocomplete attributes for fields before those it thought were password
fields. Now, those fields have to be explicitly marked as password
fields to trigger such warnings.

This CL is copy of https://chromium-review.googlesource.com/c/chromium/src/+/691669 with minor fixes, rebasing and a new test

Bug: 749516

Bug: 
Change-Id: Id2b340ba22da064106400b1a49919b081804c42e
Reviewed-on: https://chromium-review.googlesource.com/700262
Commit-Queue: Vadym Doroshenko <dvadym@chromium.org>
Reviewed-by: Maxim Kolosovskiy <kolos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506437}

NOTRY=true

Bug: 
Change-Id: I5909d84b77ae71b6b611efe11c1835e925c86ef3
Reviewed-on: https://chromium-review.googlesource.com/699859
Commit-Queue: James Zern <jzern@google.com>
Reviewed-by: Urvang Joshi <urvang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506436}

The content::WebContentsDelegate::WebUISend virtual method is a no-op
and is not overriden anywhere.  Therefore it should be safe to just
delete this method and stop calling it (since calling it is a no-op).

The only caller of content::WebContentsDelegate::WebUISend was
WebContentsImpl::OnWebUISend method which is also deleted by this CL.

ViewHostMsg_WebUISend is *not* being deleted - it is still handled by
the browser in content::WebUIImpl::OnWebUISend.

Bug: 683418, 666525
Change-Id: Icf6272b0df3f4359e758e04ddefd026402b9ea03
Reviewed-on: https://chromium-review.googlesource.com/698348
Commit-Queue: Nick Carter <nick@chromium.org>
Reviewed-by: Nick Carter <nick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506435}

https://skia.googlesource.com/skia.git/+log/a02fe096a89c..fa8c08044989

$ git log a02fe096a..fa8c08044 --date=short --no-merges --format='%ad %ae %s'
2017-10-04 robertphillips Use SK_DISABLE_DEFERRED_PROXIES to only disable deferred proxies for Chrome
2017-10-04 caryclark add missing params
2017-10-04 angle-deps-roller Roll skia/third_party/externals/angle2/ 035fd6b39..a99ed554c (2 commits)
2017-10-04 egdaniel Revert "Revert "When flushing, reset flush state before op lists""
2017-10-04 brianosman Ensure glxGetProcAddress is declared
2017-10-04 robertphillips Disable PinnedImageTest on Test-Win10-MSVC-AlphaR2-GPU-RadeonR9M470X-x86_64-Release-ANGLE bot
2017-10-04 egdaniel Revert "When flushing, reset flush state before op lists"
2017-10-03 egdaniel When flushing, reset flush state before op lists

Created with:
  roll-dep src/third_party/skia


Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, see:
http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls


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;master.tryserver.chromium.android:android_optional_gpu_tests_rel
TBR=scroggo@chromium.org

Change-Id: Ibaab00c67e4aad33ec4439d9b678906bd6b6dcfd
Reviewed-on: https://chromium-review.googlesource.com/699575Reviewed-by: Skia Deps Roller <skia-deps-roller@chromium.org>
Commit-Queue: Skia Deps Roller <skia-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506434}

+ minor refactoring to make some no-op functions in base class abstract.

Bug: 766824
Change-Id: Iea4244f08f82df7331bc2adc0d1f76466dec6445
Reviewed-on: https://chromium-review.googlesource.com/691284
Commit-Queue: Jialiu Lin <jialiul@chromium.org>
Reviewed-by: Vadym Doroshenko <dvadym@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Varun Khaneja <vakh@chromium.org>
Reviewed-by: Nathan Parker <nparker@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506433}

This command is required for running some WPTs for WebDriver.
Will add integration tests in a follow up CL implementing Set Window Rect

spec:https://w3c.github.io/webdriver/webdriver-spec.html#get-window-rect


Bug: chromedriver:1940
Change-Id: Idef3513dc5ad26fe8dd82d9808e32e84e8f7ad80
Reviewed-on: https://chromium-review.googlesource.com/685639Reviewed-by: John Chen <johnchen@chromium.org>
Commit-Queue: Jonathon Kereliuk <kereliuk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506432}

Since the service manager is outside of content and knows about all
the sandbox types it supports, we don't need a callback mechanism, and
instead add the one additional type here. This was used by only one
platform, and that's too much mechanism for this one case. Embedders
can still add a sandbox via //sandbox interfaces, as required.

Remove mention of nonexistent class SandboxInitializerDelegate while
we're at it.

Change-Id: If77e29e9c8c564b63f959c62e53f89808f19d9cf
Reviewed-on: https://chromium-review.googlesource.com/688683Reviewed-by: Jochen Eisinger <jochen@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Commit-Queue: Tom Sepez <tsepez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506431}

Still support the old property name and wrap this with w3c mode

spec: https://w3c.github.io/webdriver/webdriver-spec.html#switch-to-window

Bug: chromedriver:2045
Change-Id: I455fc9c8be076e259809c6b8c505c429db4284c3
Reviewed-on: https://chromium-review.googlesource.com/687807Reviewed-by: John Chen <johnchen@chromium.org>
Reviewed-by: Shuotao Gao <stgao@chromium.org>
Commit-Queue: Jonathon Kereliuk <kereliuk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506430}

Nobody used the member connection_monitor_started and that warning
broke jumbo build experiments (it notices such things more than
non-jumbo builds).

Change-Id: I77055474ecdbb1eaab8fbb925ea9b7a739a6f273
Reviewed-on: https://chromium-review.googlesource.com/700268
Commit-Queue: Daniel Bratell <bratell@opera.com>
Commit-Queue: Vincent Scheib <scheib@chromium.org>
Reviewed-by: Vincent Scheib <scheib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506429}

Change task queue ownership semantics in the scheduler:
- TaskQueueManager does not keep a scoped_refptr to TaskQueue.
- TaskQueueImpl may be detached from TaskQueue and passed back to
  TaskQueueManager.

New task queue lifetime:
- TaskQueueImpl should be unregistered before deletion.
- TaskQueueManager unregisters all task queues upon deletion.
- TaskQueue holds a unique pointer to TaskQueueImpl while the queue
  is active.
- TaskQueue passes TaskQueueImpl to TaskQueueManager when
  TaskQueue::UnregisterTaskQueue is called.
- (future) TaskQueue may opt into graceful shutdown. In this case
  a async task runner is provided and upon deleting unregistered
  TaskQueue TaskQueueImpl will be asynchronously passed
  to TaskQueueManager. No new tasks may be posted to this task queue
  due to TaskQueue being deleted and TaskQueueManager will continue
  running tasks until TaskQueueImpl is empty.

This patch is a first step towards supporting graceful shutdown.

R=alexclarke@chromium.org, skyostil@chromium.org
BUG=770736

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

This removes the bulk validation of histograms that was introduced
to try to locate where the corruption was originating.  Validation is
still done during metrics upload so corruption will still be detected
at that point.

Bug: 744734
Change-Id: Ie62ab5617c6939671b1eea93d2fecdf2e55e94d5
Reviewed-on: https://chromium-review.googlesource.com/699760Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Commit-Queue: Brian White <bcwhite@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506427}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/b16fa6d2..22069a18

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;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;master.tryserver.chromium.android:android_optional_gpu_tests_rel

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

Change-Id: I340bf869d7d8b7e413f07e0ab4a11277fcb8632d
Reviewed-on: https://chromium-review.googlesource.com/700479Reviewed-by: v8 autoroll <v8-autoroll@chromium.org>
Commit-Queue: v8 autoroll <v8-autoroll@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506426}

After r505922, the
http/tests/security/mixedContent/insecure-iframe-in-main-frame.html test
will no longer crash, but we still have a test output difference with
--site-per-process because of https://crbug.com/771003 (because with
--site-per-process the newly opened https window is in a different
process than the main test frame).

Bug: 602493, 770487
Change-Id: Ic19079c0edbb6c74cb2a2d408acada00340d8973
Notry: True
Reviewed-on: https://chromium-review.googlesource.com/699764Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506425}

This change makes the progress updates to the throttled progress bar
decelerate in updating linearly.

BUG=759799

Change-Id: Id146bd253bca2d86e655fc4470c98c8bd945937e
Reviewed-on: https://chromium-review.googlesource.com/692630Reviewed-by: Yusuf Ozuysal <yusufo@chromium.org>
Commit-Queue: Matthew Jones <mdjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506424}

TemplateWriter.IsPolicySupported and
TemplateWriter.IsPolicySupportedOnPlatform are now checking whether the
currect version is supported or not. It will affect the generation of
html documentation, adm/admx file, etc.

TEST: components/policy/tools/template_writers/test_suite_all.py
Bug: 770874


Change-Id: I6fcecfaae5c87197b7829bb102afc407d2120779
Reviewed-on: https://chromium-review.googlesource.com/687870
Commit-Queue: Owen Min <zmin@chromium.org>
Reviewed-by: Lutz Justen <ljusten@chromium.org>
Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506423}

(Not a direct reland: the change to extension_settings_browsertest.h
was not in the original CL)

This is a reland of f3bd7c65
Original change's description:
> Extension content verification: unify "is from store" logic
> 
> Bug: 766806
> Change-Id: I1a210ded77cc9ffdc0039fca097c6fdba7ff0131
> Reviewed-on: https://chromium-review.googlesource.com/677403
> Commit-Queue: proberge <proberge@chromium.org>
> Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#505092}

Bug: 766806
Change-Id: I4a0c69c50d7bc41a47e264ad9b9e3136a729ec96
Reviewed-on: https://chromium-review.googlesource.com/698985Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Commit-Queue: proberge <proberge@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506422}

NOTRY=true  # winbot flake

Change-Id: I2510eb714c4ae40903aecbc48da712a2c0b4898c
Reviewed-on: https://chromium-review.googlesource.com/699698
Commit-Queue: Andrew Grieve <agrieve@chromium.org>
Reviewed-by: Peter Wen <wnwen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506421}

Bug: 768429
Change-Id: I67d24b9cc4781fc9a1386a8dcdb160a5f3b23d34
Reviewed-on: https://chromium-review.googlesource.com/687275Reviewed-by: Jesse Doherty <jwd@chromium.org>
Reviewed-by: Greg Thompson <grt@chromium.org>
Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Commit-Queue: Marc-André Decoste <mad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506420}

We were already stripping 'clang' and the .so's (in package.py), but
more executables have been added since then.

On Linux, the package size goes from 67246968 to 65948746 bytes, so
about 1.2 MB savings.

BUG=none

Change-Id: I104055e7faec49d15dd433739d740f00492c48a0
Reviewed-on: https://chromium-review.googlesource.com/699019Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Hans Wennborg <hans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506419}

This patch adds a test for a payment method https://jonpay.com/pay that
supports payment apps from two origins: https://alicepay.com and
https://bobpay.com.

Bug: 771323
Change-Id: I62feba283ea34cd909019aec0d84046bee572087
Reviewed-on: https://chromium-review.googlesource.com/699084Reviewed-by: Sebastien Seguin-Gagnon <sebsg@chromium.org>
Commit-Queue: Rouslan Solomakhin <rouslan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#506418}