GitLab

Change-Id: Ib33e2722e02d84e043f4d1b962490a64d6eee464
Reviewed-on: https://chromium-review.googlesource.com/1026210
Commit-Queue: Steven Valdez <svaldez@chromium.org>
Reviewed-by: David Benjamin <davidben@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553301}

This cl creates the windows platform for ozone.

These changes are not sufficient for a successful Windows/Ozone build.
See: https://chromium-review.googlesource.com/c/chromium/src/+/974285
and https://swiftshader-review.googlesource.com/c/SwiftShader/+/17968

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: If27cd7b56d5503db6881cf1f2c563826f72f0be0
Reviewed-on: https://chromium-review.googlesource.com/975902Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Commit-Queue: Mustafa Çamurcu <camurcu@google.com>
Cr-Commit-Position: refs/heads/master@{#553300}

BUG=836426
TBR=skym@chromium.org
NOTRY=true

Change-Id: Ie9c07c1417ab693d517e1ac4ee3dc8082465a58a
Reviewed-on: https://chromium-review.googlesource.com/1026790Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553299}

Bug: 776877
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: Ic3263a6a8701cb9f99bcae657f041e624dc8ca01
Reviewed-on: https://chromium-review.googlesource.com/1011674
Commit-Queue: Peng Huang <penghuang@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553298}

Saw this when investigating 835741, and I think this makes the code
confusing that it appears like we need to run these ops when in
reality they don't do anything.

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Ia361cacc4c3760bc5caf2653b0a55b84ce4fdee9
Reviewed-on: https://chromium-review.googlesource.com/1024671Reviewed-by: Khushal <khushalsagar@chromium.org>
Commit-Queue: enne <enne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553297}

In RLS mode, the position of an iframe LayoutView's main GraphicsLayer
must account for any offset from the border or outline styling of the
<iframe> element.

Previously there were two different codepaths for applying this offset:
(1) LayoutView's CLM in the child frame's compositing update
(2) LayoutIFrame's CLM in the parent frame's compositing update

If both frames are invalidated at the same time, path (1) breaks,
because the parent document's lifecycle state disallows the child
frame's compositing queries.  Having two paths is also error-prone.
This patch removes (1) in favor of using (2) exclusively.

Bug: 825775
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: I00cf19be083081315e7918efc1ebd2af00cae906
Reviewed-on: https://chromium-review.googlesource.com/1020146
Commit-Queue: Steve Kobes <skobes@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553296}

When a view fails an accessibility check, it can be very helpful to find
out what line of code constructed it. This provides information on how
to patch in code that does that.

We may want to build this in at some point:
See https://crrev.com/c/1025637 or https://crrev.com/c/963284.

Bug: 811293
Change-Id: I14046d7d40a5475e28691d371acdcb6538b66663
Reviewed-on: https://chromium-review.googlesource.com/1026055Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Commit-Queue: Aaron Leventhal <aleventhal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553295}

Launching a process is racy with browser shutdown, and blocks it. So we
see shutdown hangs when process launch takes a long time. This CL makes
the process launcher use a CONTINUE_ON_SHUTDOWN instead of
BLOCK_SHUTDOWN task on Windows where it's presumably safe to do so given
no non-leaky globals are used, and based on local testing. This is not
safe on Linux since the process launcher there uses SandboxHostLinux
which is a non-leaky base::Singleton.

R=brucedawson,gab
BUG=830954

Change-Id: Ia8c5295924288819dcfdcc087d282a05e6ee7e55
Reviewed-on: https://chromium-review.googlesource.com/1020720Reviewed-by: Antoine Labour <piman@chromium.org>
Reviewed-by: Bruce Dawson <brucedawson@chromium.org>
Reviewed-by: Gabriel Charette <gab@chromium.org>
Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553294}

These changes were scripted as part of the effort to restrict exposure of the
raw MessageLoop*.

Note that many static methods exposed on MessageLoopCurrent are also deprecated
so it is very well possible that this is migrating to an already deprecated
method.

The goal of this pass is to reduce usage of MessageLoop::current() (and
ultimately make it impossible to obtain the MessageLoop* statically).

As such I will not edit this CL unless the script did something logically wrong.
I defer to owners to fix highlighted usage of already deprecated APIs.

Possible script screw ups / things to look out for in this review:
 - Storing MessageLoopCurrent in a MessageLoop* variable or comparing it against
   one (I will go over that in a separate pass).

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

Bug: 825327
Change-Id: Ic3627d36d9e562b112766c1d597351caae7c0718
Reviewed-on: https://chromium-review.googlesource.com/1024284Reviewed-by: Joe Downing <joedow@chromium.org>
Commit-Queue: Gabriel Charette <gab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553293}

These changes were scripted as part of the effort to restrict exposure of the
raw MessageLoop*.

Note that many static methods exposed on MessageLoopCurrent are also deprecated
so it is very well possible that this is migrating to an already deprecated
method.

The goal of this pass is to reduce usage of MessageLoop::current() (and
ultimately make it impossible to obtain the MessageLoop* statically).

As such I will not edit this CL unless the script did something logically wrong.
I defer to owners to fix highlighted usage of already deprecated APIs.

Possible script screw ups / things to look out for in this review:
 - Storing MessageLoopCurrent in a MessageLoop* variable or comparing it against
   one (I will go over that in a separate pass).

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

Bug: 825327
Change-Id: If17acb98d53b8a6a352a0c09699ddb60915393d0
Reviewed-on: https://chromium-review.googlesource.com/1024808Reviewed-by: Ken Rockot <rockot@chromium.org>
Commit-Queue: Gabriel Charette <gab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553292}

BUG=chromium:829085
TEST=Tested manually on device

Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I9353962f50ba3ea78abe8251e4ec3c2f140cb432
Reviewed-on: https://chromium-review.googlesource.com/1008967
Commit-Queue: David Valleau <valleau@chromium.org>
Reviewed-by: Sean Kau <skau@chromium.org>
Reviewed-by: Michael Giuffrida <michaelpg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553291}

This CL fixes the misalignment of the hosted app menu button
anchor point by updating its view bounds.

Overriding CalculatePreferredSize() didn't update the behaviour
of GetHeightForWidth() which caused it to be cropped by the
container's BoxLayout. LabelButton::SetMinSize() exists and
should be used instead.

Before rects:
https://bugs.chromium.org/p/chromium/issues/attachment?aid=335982&signed_aid=hz80AUGwixvyOI7d2jCIYQ==&inline=1

After rects:
https://bugs.chromium.org/p/chromium/issues/attachment?aid=335983&signed_aid=9NLhUbDPYjh_YRMnsVABAw==&inline=1

Bug: 836099
Change-Id: I77ad668816df936bbb3129aa1253330382fe22c5
Reviewed-on: https://chromium-review.googlesource.com/1025592Reviewed-by: Peter Kasting <pkasting@chromium.org>
Commit-Queue: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553290}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/034c66d8..0cf37360

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

Adds the SessionStorageLevelDBWrapper class, which works with the
SessionStorageMetadata and SessionStorageDataMap classes to support
shallow cloning for SessionStorage data maps.

TBR-ing jam for content/browser/BUILD.gn

TBR: jam@chromium.org
Bug: 716490
Change-Id: I1a3ad1a79f39ef001bd4489591d6e99ab0f6347f
Reviewed-on: https://chromium-review.googlesource.com/954410
Commit-Queue: Daniel Murphy <dmurph@chromium.org>
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553288}

This reverts commit e34f08fa.

Reason for revert: using_sanitizer should also set enable_frame_pointer on android.
The cfi bot was broken because it enabled cfi unwinding with frame pointers.

Original change's description:
> Revert "Fix conditions for can_unwind_with_cfi_table with frame pointers"
>
> This reverts commit 5e4c7d7b.
>
> Reason for revert:
> Speculative revert for failing base_unittests on Android,
> CFIBacktraceAndroidTest.TestUnwinding.
>
> See https://uberchromegw.corp.google.com/i/chromium.memory/builders/Android%20CFI/builds/579
>
> Original change's description:
> > Fix conditions for can_unwind_with_cfi_table with frame pointers
> >
> > CFI table unwinder is not appilcable for builds with frame pointer
> > enabled. Make sure can_unwind_with_cfi_table is set to false.
> > No need to check for use_thin_lto.
> >
> > BUG=469376
> >
> > Change-Id: I71a4de08a0496edf26829c69851ea89bdbc02bd6
> > Reviewed-on: https://chromium-review.googlesource.com/992890
> > Reviewed-by: Peter Collingbourne <pcc@chromium.org>
> > Reviewed-by: Nico Weber <thakis@chromium.org>
> > Commit-Queue: Siddhartha S <ssid@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#548634}
>
> TBR=thakis@chromium.org,ssid@chromium.org,pcc@chromium.org
>
> Change-Id: I1bb99a9cde8fd501bd5abb7aa7fe798684454226
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Bug: 469376,826718
> Reviewed-on: https://chromium-review.googlesource.com/999635
> Reviewed-by: Mikel Astiz <mastiz@chromium.org>
> Commit-Queue: Mikel Astiz <mastiz@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#548765}

Change-Id: Ic6637dfe890a51264f9d151a681534fe92fc9354
Bug: 469376, 826718
Reviewed-on: https://chromium-review.googlesource.com/1000412
Commit-Queue: Siddhartha S <ssid@chromium.org>
Reviewed-by: Peter Collingbourne <pcc@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Reviewed-by: Siddhartha S <ssid@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553287}

The flag is not currently used and disabled.

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

These changes were scripted as part of the effort to restrict exposure of the
raw MessageLoop*.

Note that many static methods exposed on MessageLoopCurrent are also deprecated
so it is very well possible that this is migrating to an already deprecated
method.

The goal of this pass is to reduce usage of MessageLoop::current() (and
ultimately make it impossible to obtain the MessageLoop* statically).

As such I will not edit this CL unless the script did something logically wrong.
I defer to owners to fix highlighted usage of already deprecated APIs.

Possible script screw ups / things to look out for in this review:
 - Storing MessageLoopCurrent in a MessageLoop* variable or comparing it against
   one (I will go over that in a separate pass).

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

Bug: 825327
Change-Id: I683a3fc7b20d41d4d069fb9e7fd0b4cdcf915028
Reviewed-on: https://chromium-review.googlesource.com/1024494Reviewed-by: Ryan Hamilton <rch@chromium.org>
Commit-Queue: Gabriel Charette <gab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553285}

This change will keep web content area in sync with displayed URL.
Previously displayed pending URL (like data:exe) did not match web
content.

Bug: 835400
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: I6417df266dd54b8aad0790b52bc2c576ead52d48
Reviewed-on: https://chromium-review.googlesource.com/1022743Reviewed-by: Sylvain Defresne <sdefresne@chromium.org>
Commit-Queue: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553284}

js_modules is used by closure during compilation.
It is not needed if there is no compilation.

This CL fixes the gn error on js_modules not being used
when compiling with compile_javascript=false.

Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: I9de8b97214e97c068f55b770a4f296bb1c9bee4d
Reviewed-on: https://chromium-review.googlesource.com/1024839
Commit-Queue: Olivier Robin <olivierrobin@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553283}

This change cleans up some logic in BrowserPlugin and
RenderFrameProxy, now that we fully support child-allocated local
surface IDs. Additionally, it removes AutoResize sequence numbers
from the code, as these were no longer used.

Bug: 811944
Change-Id: Ic15d6fbdbb2851282b9604dadfb7be47e315d506
Reviewed-on: https://chromium-review.googlesource.com/1024490Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Reviewed-by: Fady Samuel <fsamuel@chromium.org>
Commit-Queue: Eric Karl <ericrk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553282}

This CL is a refactor with no intended behavior change.

It updates the semantics to explicitly take ownership of the WebContents.

Bug: 832879
Change-Id: Icb8ffbd89b3d598ccdf228ad7d0e297b9f6f5bbc
Reviewed-on: https://chromium-review.googlesource.com/1026270Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Erik Chen <erikchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553281}

https://webrtc.googlesource.com/src.git/+log/7741b7ac499b..70244d225207

$ git log 7741b7ac4..70244d225 --date=short --no-merges --format='%ad %ae %s'

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


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

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng
TBR=webrtc-chromium-sheriffs-robots@google.com

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

Change Log: https://chromium.googlesource.com/external/github.com/abseil/abseil-cpp/+log/abd0824ba6..af7882601a
Full diff: https://chromium.googlesource.com/external/github.com/abseil/abseil-cpp/+/abd0824ba6..af7882601a

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

This is a followup addressing an advice from sadrul@ in
https://chromium-review.googlesource.com/c/chromium/src/+/1017300

BUG=828462
TEST=bots
R=sadrul@chromium.org,piman@chromium.org

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: Iea8ab8a76adf0d5728480d1fc97087dc6d5cb7c1
Reviewed-on: https://chromium-review.googlesource.com/1024493Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Commit-Queue: Zhenyao Mo <zmo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553278}

The Apple interpretation as gamma=1.961 will be used when the video
frame is displayed as an overlay, so use that interpretation in the GL
compositing path as well.

Bug: 836351
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: I7aee20d08e8162dd2bbfdc20ba3235789a5a6216
Reviewed-on: https://chromium-review.googlesource.com/1026430Reviewed-by: Fredrik Hubinette <hubbe@chromium.org>
Commit-Queue: ccameron <ccameron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553277}

Previously, we would defer commit when the child didn't yet have a
LocalSurfaceId. This meant we needed a special case to call
DidResizeOrRepaintAck() early when commit would be deferred.

But now the child has the ability to allocate its own
LocalSurfaceId. As a result, we no longer need to defer commit. And
thus, no longer need to call DidResizeOrRepaintAck() early.

BUG=805073,811944,836009

Change-Id: I4e85e926f217cf0fd2d4b5ed3854f09e7145e5a8
Reviewed-on: https://chromium-review.googlesource.com/1024739Reviewed-by: Antoine Labour <piman@chromium.org>
Reviewed-by: Fady Samuel <fsamuel@chromium.org>
Commit-Queue: Fady Samuel <fsamuel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553276}

This is a reland of 89dbe1f8

Original change's description:
> Fix build errors with upstream libassistant change
> 
> Test: build locally with upreved libassistant
> Bug: None
> Change-Id: I3db67f5a77824fcf0831447f353baba6167b0801
> Reviewed-on: https://chromium-review.googlesource.com/1025268
> Reviewed-by: Muyuan Li <muyuanli@chromium.org>
> Commit-Queue: Muyuan Li <muyuanli@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#552972}

Bug: None
Change-Id: Ibbd692cbde43012504d3790a9be8e7911be87149
Reviewed-on: https://chromium-review.googlesource.com/1026256Reviewed-by: Muyuan Li <muyuanli@chromium.org>
Commit-Queue: Xiaohui Chen <xiaohuic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553275}

These changes were scripted as part of the effort to restrict exposure of the
raw MessageLoop*.

Note that many static methods exposed on MessageLoopCurrent are also deprecated
so it is very well possible that this is migrating to an already deprecated
method.

The goal of this pass is to reduce usage of MessageLoop::current() (and
ultimately make it impossible to obtain the MessageLoop* statically).

As such I will not edit this CL unless the script did something logically wrong.
I defer to owners to fix highlighted usage of already deprecated APIs.

Possible script screw ups / things to look out for in this review:
 - Storing MessageLoopCurrent in a MessageLoop* variable or comparing it against
   one (I will go over that in a separate pass).

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

Bug: 825327
Change-Id: I23484e311db823f08ac571bf34411f960cd8fb3e
Reviewed-on: https://chromium-review.googlesource.com/1024316Reviewed-by: Tom Sepez <tsepez@chromium.org>
Commit-Queue: Gabriel Charette <gab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553274}

Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I5911beeac2719301ed7bbb3d154a5e9aaab4b596
Reviewed-on: https://chromium-review.googlesource.com/1017583Reviewed-by: Steve McKay <smckay@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553273}

Migrate MessageLoop::current() to MessageLoopCurrent in /chrome/browser/ui/webui/sync_internals_ui_unittest.cc

These changes were scripted as part of the effort to restrict exposure of the
raw MessageLoop*.

Note that many static methods exposed on MessageLoopCurrent are also deprecated
so it is very well possible that this is migrating to an already deprecated
method.

The goal of this pass is to reduce usage of MessageLoop::current() (and
ultimately make it impossible to obtain the MessageLoop* statically).

As such I will not edit this CL unless the script did something logically wrong.
I defer to owners to fix highlighted usage of already deprecated APIs.

Possible script screw ups / things to look out for in this review:
 - Storing MessageLoopCurrent in a MessageLoop* variable or comparing it against
   one (I will go over that in a separate pass).

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

Bug: 825327
Change-Id: Ic0b91000c8cd7fb5a08d97cf374d2fec8453038e
Reviewed-on: https://chromium-review.googlesource.com/1024396Reviewed-by: Pavel Yatsuk <pavely@chromium.org>
Commit-Queue: Gabriel Charette <gab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553272}

Page.captureScreenshot blocks on arrival of a LatencyInfo with
BROWSER_SNAPSHOT_FRAME_NUMBER_COMPONENT component. However, the
browse process does not receive latency info when Viz is enabled.
Plumb latency info with BROWSER_SNAPSHOT_FRAME_NUMBER_COMPONENT
component from viz to the browser process.

TBR=boliu@chromium.org

Bug: 810037
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Ia81b0644f29a37059a7b3e0303074fb0db340757
Reviewed-on: https://chromium-review.googlesource.com/1020301Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Reviewed-by: kylechar <kylechar@chromium.org>
Reviewed-by: Fady Samuel <fsamuel@chromium.org>
Commit-Queue: Saman Sami <samans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553271}

Marks methods on the Command Line API that produce no JS-observable
side-effect.

Bug: 829571
Change-Id: I7920b2ded3eada33fc2d000aa46a0a7eef61daca
Reviewed-on: https://chromium-review.googlesource.com/1025171Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Reviewed-by: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org>
Commit-Queue: Erik Luo <luoe@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553270}

There are multiple types of iTunes media, only show StoreKit for apps

Bug: 835940, 835404
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: Ia355c97e2f556cd96faaecd478e950541cf03286
Reviewed-on: https://chromium-review.googlesource.com/1025177Reviewed-by: Eugene But <eugenebut@chromium.org>
Commit-Queue: Mohammad Refaat <mrefaat@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553269}

This patch exposes BrowserContextId as a part of TargetInfo.
This helps to attribute pages to the browser contexts they
belong to.

BUG=836272
R=dgozman

Change-Id: I93d54756c98124a077bd979c207c0c7cd7e38971
Reviewed-on: https://chromium-review.googlesource.com/1026391Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Commit-Queue: Andrey Lushnikov <lushnikov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553268}

Ninja has a quirk that makes it blind to incremental source file
changes, so long as the source files' timestamp precedes the last
build time. As a result Ninja was not correctly picking up changes
in SDK rolls, resulting in an unbootable combination of fresh and stale
build files.

This CL effectively implements a recursive "touch" on the SDK files,
which gives an unambiguous change signal to Ninja.

Change-Id: I6b5e15a2b4404fcc7a2f52ebf76f75f80a0a6605
Reviewed-on: https://chromium-review.googlesource.com/1025376Reviewed-by: Scott Graham <scottmg@chromium.org>
Commit-Queue: Kevin Marshall <kmarshall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553267}

They are flaky.

BUG=785555
TBR=satorux@chromium.org
NOTRY=true

Change-Id: I9e2fbaf9bb1efacc50da6e1b8cd855d379e34568
Reviewed-on: https://chromium-review.googlesource.com/1026560Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553266}

The NTP (New tab page) renderer is a semi-priveleged process having access to
some special APIs. But currently, network requests made by an NTP renderer can
be intercepted by extensions using the web request API.

This CL hides network requests made by an NTP renderer from extensions. This
works since it's guaranteed that the NTP won't share the renderer process with
any other site.

BUG=797461

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

There is a pre-existing bug on Mac where Control + A performs "Select
all" instead of Command + A. The equivalent context menu item just sends
the keystroke to perform "Select all". As such, when it tried to do the
right thing and use the Command modifier, "Select all" does not actually
work.

To fix this quickly, just make the context menu item send Control + A.
Of course this is not ideal, but making Command + A perform "Select all"
is harder than it appears.

BUG=834735,836074

Change-Id: I2c8201772d7e901984c427d0977a1fb899f802b5
Reviewed-on: https://chromium-review.googlesource.com/1025403Reviewed-by: dsinclair <dsinclair@chromium.org>
Reviewed-by: Bill Budge <bbudge@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553264}

Its use of feature flags causes data races.

The first attempt in https://chromium-review.googlesource.com/1026462
got incorrectly reverted by FindIt.

BUG=836359
TBR=xidachen@chromium.org
NOTRY=true

Change-Id: Icfeaf23ccb69b3b1e80f6df10556f5c75e663a71
Reviewed-on: https://chromium-review.googlesource.com/1026557Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553263}

Bug: 834899
Change-Id: I160ebe1b8e830851291e89fdc8b2a860881637f7
Reviewed-on: https://chromium-review.googlesource.com/1025651Reviewed-by: Adrienne Porter Felt <felt@chromium.org>
Commit-Queue: Edward Jung <edwardjung@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553262}