GitLab

In order to use cc::TouchAction on the blink mojom API we require it the
definition to move to somewhere blink can depend on (not content).

Being that touch_action is defined in CC it seems natural to introduce it
there.

BUG=1008432

Change-Id: I62ab198a169bd242d36e27a5357636800e296593
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1867036Reviewed-by: Ken Rockot <rockot@google.com>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: danakj <danakj@chromium.org>
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708796}

Some small fixes and Py3 compatibility.

Bug: None
Change-Id: I09855299135799527dbcf4d0070a2ce9d9147d6b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872564
Auto-Submit: Alexei Svitkine <asvitkine@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Alexei Svitkine <asvitkine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708795}

It's ignored by the Mac codesigning apparatus nowadays, anyway,
so this simplifies things.

Bug: 913074
Change-Id: I1aff929788171821a835bd5a4eed5514fe2df1be
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1876764Reviewed-by: Robert Sesek <rsesek@chromium.org>
Commit-Queue: Avi Drissman <avi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708794}

Revert the code changes from crrev.com/c/1590960 and mark the histogram
as obsolete. We were investigating how modifying the slop region
affected this metric, and have seen data showing that, as expected, the
metric goes proportional to the decrease in slop distance.

Bug: 988762
Change-Id: I802aad4f80b718d163f4b536f3ee66e7a90b3526
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1875367Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Commit-Queue: Daniel Libby <dlibby@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#708793}

In order to do this, we will need to know whether or not a PWA is
installed for a given profile, without actually loading that profile.
The suggested mechanism for this is to check the for the presence of
a Extensions/app_id subdirectory of the profile path.

Add a profile_menu_items_ member to ExtensionAppShimHandler that
lists all profiles in the AvatarMenu.

Add a installed_profiles member to ExtensionAppShimHandler::AppState
that lists all profiles for which a given app is installed (this is
a subset of the profiles in ExtensionAppShimHandler::
profile_menu_items_).

Add a ExtensionAppShimHandler::Delegate::GetProfilesForAppAsync
method to do the aforementioned path check.

Update ExtensionAppShimHandler::UpdateAppProfileMenu to sort menu
items by |menu_index| and to send an empty list if just one profile
would have appeared in the menu.

Add tests. Restructure tests such that ExtensionAppShimHandler
takes its delegate as a constructor argument (instead of having it
be set-able).

R=dominickn
TBR=skuhne

Bug: 1001215
Change-Id: I10bb7128c6f775759f1d1f381000eb7b33960eb3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1864098Reviewed-by: ccameron <ccameron@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Commit-Queue: ccameron <ccameron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708792}

This sets what field trials are enabled by default when running tests,
and is needed before the option can be enabled on beta.

The option is added to the pre-existing experiment
PartitionConnectionsByNetworkIsolationKey to mirror the server-side
configuration.

Bug: 963480
Change-Id: Ib1a6ca42b997658f2b66658b9ba2713f1669545d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1873959Reviewed-by: Zhongyi Shi <zhongyi@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Matt Menke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708791}

Add a generic isManagedPreference method to PrefServiceBridge, making
use of the prefs.h enums.

Migrate Java usages of prefs::kSearchSuggestEnabled to use the generic
methods as a sample (more to follow).

Bug: 1016957
Change-Id: Ib13181fd9ed6c2e2265b08c141985899bfbabe0c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1874719Reviewed-by: Theresa  <twellington@chromium.org>
Commit-Queue: Natalie Chouinard <chouinard@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708790}

This macro had apparently not been effective at detecting removed
origin trials since the OT/RTEF bindings were refactored earlier this
year. WebVR was removed from OT without triggering an assertion
failure. This CL fixes that now by testing for a method which is only
generated if the feature is part of a trial.

Bug: 960132
Change-Id: I1a8d8542d3c2513170ac5fc57411991e3988d938
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1874191
Commit-Queue: Ian Clelland <iclelland@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708789}

Adds expires_after attribute for 7 histograms that do not already have one.
The date will get pushed out automatically if significant use is detected.

Change-Id: I8d2c670e6619a8e2d3477b982fcedfe4a7a9892e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1876751Reviewed-by: Brian White <bcwhite@chromium.org>
Commit-Queue: Brian White <bcwhite@chromium.org>
Commit-Queue: Brian White <bcwhite@google.com>
Cr-Commit-Position: refs/heads/master@{#708788}

This relaxes the requirements for tiled draw quads that can bypass a RenderPass.
Previously, the content quad had to have an identity transform and fill the
RenderPass's layer.

With this change, the geometry and transform constraints go away, and the RPDQ
params struct is updated to remember the additional transform that has to be
applied to draw the content correctly. The base transform and the new transform
are kept separate because the image filters of the render pass have to be
processed in the base transform's coordinate space. However, we also don't want
to just draw the base geometry with the content quad's textures because the
texture coordinates may not map to a gfx::Rect anymore. Storing separate transforms
cleanly handles both of these challenges.

Bug: 1013735
Change-Id: I0a05d2aa318238dae093899c697fac6a84e5c261
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1860302
Commit-Queue: Michael Ludwig <michaelludwig@google.com>
Reviewed-by: weiliangc <weiliangc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708787}

The NetworkService only considers redirects to certain schemes it's
familiar with unsafe. Now that it no longer handles data or file URLs,
there's no such scheme. As a result, allowing redirects to unsafe URLs
doesn't actually do anything.

The same mechanism was also being used to preserve the (lack of) a
fragment on redirects injected by extensions, rather than copying over
the fragment like a normal redirect, so in its place, add a concept of
a URL that, if redirected to, keeps its frament.

Unfortunately, the unsafe URL concept is still used for redirects to
chrome URLs on iOS (which doesn't allow that to be overridden), so
this CL does not completely remove the concept of unsafe redirects.

Bug: 934009
Change-Id: I366156d94aed9067ff18dc14bfd7bf9142817123
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869727
Commit-Queue: Matt Menke <mmenke@chromium.org>
Reviewed-by: Karan Bhatia <karandeepb@chromium.org>
Reviewed-by: Emily Stark <estark@chromium.org>
Reviewed-by: Eric Roman <eroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708786}

https://webrtc.googlesource.com/src.git/+log/6adb0a26846c..d7bf5c56b69b

git log 6adb0a26846c..d7bf5c56b69b --date=short --no-merges --format='%ad %ae %s'
2019-10-23 mbonadei@webrtc.org Revert "Define WEBRTC_ENABLE_SYMBOL_EXPORT if is_component_build=true."
2019-10-23 mbonadei@webrtc.org Reland "Define WEBRTC_ENABLE_SYMBOL_EXPORT if is_component_build=true."
2019-10-23 danilchap@webrtc.org change PacketBuffer to return it's result rather that use callback
2019-10-23 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 6dc3a51e..b5030084 (708537:708640)

Created with:
  gclient setdep -r src/third_party/webrtc@d7bf5c56b69b

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/webrtc-chromium-autoroll
Please CC webrtc-chromium-sheriffs-robots@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

TBR=webrtc-chromium-sheriffs-robots@google.com

Bug: chromium:None,chromium:None
Change-Id: I7bd0d1650c7147745e0b051076aba23c45aa9a05
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1876968Reviewed-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@{#708785}

This reverts commit 29a875e1.

Reason for revert: Strong suspect for compile failure blocking the tree: https://logs.chromium.org/logs/chromium/buildbucket/cr-buildbucket.appspot.com/8898774375244271360/+/steps/compile/0/stdout

Original change's description:
> Add underflow duration to our media UKM reporting.
> 
> This associates a completed underflow count and total underflow duration
> with each segment of watch time reported to UKM.
> 
> Generally the completion will always fall within a given segment of
> watch time, however it is possible that a completion can happen after a
> resolution change or other secondary property update and thus end up in
> a subsequent segment.
> 
> We impose impose a maximum value of 1 minute for rebuffer durations to
> avoid noise from rebuffers which may cross a suspend/resume boundary.
> 
> BUG=994021
> TEST=new unittests
> R=​sandersd
> 
> Change-Id: I1b4386845e21ec17472cbf8c85bf62185e28eb25
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869023
> Reviewed-by: Mustafa Emre Acer <meacer@chromium.org>
> Reviewed-by: Steven Holte <holte@chromium.org>
> Reviewed-by: Dan Sanders <sandersd@chromium.org>
> Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#708778}

TBR=dalecurtis@chromium.org,meacer@chromium.org,sandersd@chromium.org,holte@chromium.org

Change-Id: I6bdff8dee0fb365eabee3bea8501a22155059d0d
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 994021
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1877192Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708784}

This was not an issue in release builds, but it's causing failures in
libFuzzer debug builds.

Change-Id: Ic4297a97c3cd6361e778b19f66aa8779bbb89e0b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1875516
Auto-Submit: Martin Barbella <mbarbella@chromium.org>
Commit-Queue: Daniel Murphy <dmurph@chromium.org>
Reviewed-by: Daniel Murphy <dmurph@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708783}

The stable_eset tag was deprecated August 22, but Omaha is still
reporting many users still using the stable_eset tag. It's possible
something is pulling tag values from fieldtrial_testing_config,
so add a unique value for those tags.

Fixed: 1017200
Change-Id: Icc8dd004cf84e6f3af05e03d0eb7a9ce03719617
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1876026Reviewed-by: Brian White <bcwhite@chromium.org>
Reviewed-by: Joe Mason <joenotcharles@chromium.org>
Commit-Queue: Daniel Rubery <drubery@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708782}

This CL adds the plumbing to have separate top and bottom shown ratios.
Having separate ratios is required for the upcoming CLs as we
ultimately want to be able to animate the top and the bottom controls
independently.

Bug: 989148
Change-Id: I874cf7f6fa0380cb9a1497d3804969b82bd419c3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1827951
Commit-Queue: Sinan Sahin <sinansahin@google.com>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Will Harris <wfh@chromium.org>
Reviewed-by: Khushal <khushalsagar@chromium.org>
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708781}

https://skia.googlesource.com/skia.git/+log/e9462dd2dac4..cba64462d266

git log e9462dd2dac4..cba64462d266 --date=short --no-merges --format='%ad %ae %s'
2019-10-23 mtklein@google.com hide color filters from blitters
2019-10-23 bsalomon@google.com Rewrite ReadPixels_Gpu test to be more exhaustive and share code.

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

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/skia-autoroll
Please CC michaelludwig@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

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=michaelludwig@google.com

Bug: None
Change-Id: Ie0a193841f0a5eeb75030ff940ac53e6f7d6e9d5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1876080Reviewed-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@{#708780}

Bug: 1016901,925035
Change-Id: Iaec42b329c4b8a84011a999181ed4d89cf976c09
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1876491Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Commit-Queue: Ben Kelly <wanderview@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708779}

This associates a completed underflow count and total underflow duration
with each segment of watch time reported to UKM.

Generally the completion will always fall within a given segment of
watch time, however it is possible that a completion can happen after a
resolution change or other secondary property update and thus end up in
a subsequent segment.

We impose impose a maximum value of 1 minute for rebuffer durations to
avoid noise from rebuffers which may cross a suspend/resume boundary.

BUG=994021
TEST=new unittests
R=sandersd

Change-Id: I1b4386845e21ec17472cbf8c85bf62185e28eb25
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869023Reviewed-by: Mustafa Emre Acer <meacer@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Reviewed-by: Dan Sanders <sandersd@chromium.org>
Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708778}

This flag was on by default but only took effect if HTML Imports
was also enabled. The [1] commit disabled Custom Elements v0 and
Shadow DOM v0, but it also disabled the HTMLImportsStyleApplication
flag. This broke some sites (notably Youtube) that use HTML
Imports with imported style sheets. This CL fixes that breakage,
and removes this unnecessary flag.

[1] https://chromium.googlesource.com/chromium/src/+/f52dff0d3c5bc52ba608920f843162832f2da6b1

Bug: 1017069
Change-Id: I0f806635185932abab8d675fdb0814ede1fb8465
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1876744Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Mason Freed <masonfreed@chromium.org>
Auto-Submit: Mason Freed <masonfreed@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708777}

Bug: 1016946
Change-Id: Ib9bb97271e18eb1428eded141068a4c0526a8096
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872481Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Commit-Queue: Yulun Wu <yulunwu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708776}

This is relatively easy because every WebContentsDelegate that overrides
LoadProgressChanged is also a WebContentsObserver (aside from a few
thunks which are easily updated).

This fixes a TODO and makes upcoming changes to WebLayer APIs more
natural.

While we're at it, convert Clank from using integer progress in
[0,100] range to float progress in [0,1] range.

Change-Id: I3020aaa1848361d134f7422cc226f838f624dacc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872740
Commit-Queue: Evan Stade <estade@chromium.org>
Reviewed-by: Bo <boliu@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708775}

- All thumbnails shown can be released after GTS is gone.
- No thumbnails are loaded before GTS becomes visible.

Bug: 983170
Change-Id: Ib7b38909625033c82213f728b6d2e9d4a33e7b53
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1868844
Commit-Queue: Wei-Yin Chen (陳威尹) <wychen@chromium.org>
Reviewed-by: Yusuf Ozuysal <yusufo@chromium.org>
Reviewed-by: Yue Zhang <yuezhanggg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708774}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/4900f195bb83..9709599c10ff


Created with:
  gclient setdep -r src-internal@9709599c10ff

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll
Please CC jbudorick@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome
TBR=jbudorick@google.com

Bug: chromium:None
Change-Id: Ic97ea5e1ed4574cbca38d0d2f12725461368591f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1876079Reviewed-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@{#708773}

Defining xcode build version as recipe properties for each respective builder.
ios-simulator-cr-recipe already had 11a1027 set as part of recipe properties.

Migrating over the following:
- xcode_10e1001
- xcode_11m382q

Bug: 1014539
Change-Id: I111bc9a02bb125c38daf2694441d3d6fd9bd3318
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1874735Reviewed-by: Takuto Ikuta <tikuta@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Jeff Yoon <jeffyoon@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708772}

Currently the navbar is too long and some image titles are prematurely
cutoff.  This CL ensures the navbar is up to specs.

screenshots (after):
https://screenshot.googleplex.com/ZYi94ycYreo (english ltr)
https://screenshot.googleplex.com/cVFMK99HuDv (arabic rtl)

Specs:
https://drive.google.com/open?id=10Mwipz5IFvlf_bOVSu7JnTS2bKckrGBp

Bug: 1016964
Change-Id: Ibba8c02abf66249b6f2a42fd9af7781951db8b47
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1874817Reviewed-by: Xiaoqian Dai <xdai@chromium.org>
Commit-Queue: Regan Hsu <hsuregan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708771}

This reverts commit 1a394948.

Reason for revert: crbug.com/1011605 (probably caused by a linker bug
on ARM ChromeOS) has been worked around in crbug.com/1011161.

Original change's description:
> Revert "Mark some blink testing targets testonly"
>
> This reverts commit a4453534.
>
> Reason for revert: http://crbug.com/1011605
>
> Original change's description:
> > Mark some blink testing targets testonly
> >
> > This forbids production code depending on these targets, and enables
> > these targets to depend on other testonly targets in the future.
> >
> > The only dependency prevented core:testing from being testonly was
> > from BlinkLeakDetector. Add Page::PrepareForLeakDetection() and
> > InternalSettingsPageSupplementStub (in page.h) to avoid the
> > dependency.
> >
> > Change-Id: Ie22676a233d9b5c02cf3cde79629f4b84782b572
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1829586
> > Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
> > Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#701334}
>
> TBR=wangxianzhu@chromium.org,chrishtr@chromium.org
>
> # Not skipping CQ checks because original CL landed > 1 day ago.
>
> Change-Id: Icb266b74d3f75ffff2176ec2b0ca4871d99e7587
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1842973
> Reviewed-by: Kuo Jen Wei <inker@chromium.org>
> Commit-Queue: Kuo Jen Wei <inker@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#703202}

TBR=wangxianzhu@chromium.org,chrishtr@chromium.org,inker@chromium.org

Change-Id: I7390267d2f56aed847dd0f615bebdac5e2348526
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1876870Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708770}

https://chromium.googlesource.com/devtools/devtools-frontend/+log/acb77af66d..d45051a43c

TBR=bmeurer@chromium.org

Change-Id: Id86bca44c7d9356d44e722fa83af81707bfab610
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1876848Reviewed-by: Yang Guo <yangguo@chromium.org>
Commit-Queue: Yang Guo <yangguo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708769}

Mirroring ScopedImageDecodeTask, measure and record decoded image upload
time for gpu raster tasks.

Added metrics:
 Renderer4.ImageUploadTaskDurationUs.{ImageType}
 Renderer4.ImageUploadTaskDurationUs
 Renderer4.ImageUploadTaskDurationUs.OutOfRaster

Bug: 963619
Change-Id: Ie4faaba63129b13a35eddf3b91b93635940e04bd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1852485Reviewed-by: Eric Karl <ericrk@chromium.org>
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Sasha McIntosh <sashamcintosh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708768}

Remove FrameMsg_NotifyUserActivation and add an API on LocalFrame to
cause a UserActivation caused from some user action in the browser.

BUG=1008432

Change-Id: I0d4f808b1cd23d73baa2cd752026c5541e770801
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1871643
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708767}

Not sure why the other phases weren't included in the initial patch
when this was introduced:
https://chromium.googlesource.com/chromium/src/+/dd40dd139ddc8739797f923d4bcd3681e694ac2c

But this fixes all the descendant clip related issues when
turning on block-level fragment painting.

Bug: 988015
Change-Id: If6d88422ff5a4dc1bc06d60588a5b4fd5227e74b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869012
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708766}

Since we have been unable to join on the VideoDecoderStats table due to
processing times and lack of cross correlation per resolution, metrics
leadership has asked we add this field directly to watch time
calculations.

BUG=1002587
R=chcunningham

Change-Id: Id7ef8a28ec43607920885d62f3597b54aad647cd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869681Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Reviewed-by: Mustafa Emre Acer <meacer@chromium.org>
Reviewed-by: Chrome Cunningham <chcunningham@chromium.org>
Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708765}

This omission has resulted in some bugs not being credited properly in
release notes.

R=wfh@chromium.org

Change-Id: I27f9ff6605f3d037afdbeb8552e7f277436d9b7d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1868917
Auto-Submit: Adrian Taylor <adetaylor@chromium.org>
Reviewed-by: Will Harris <wfh@chromium.org>
Commit-Queue: Adrian Taylor <adetaylor@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708764}

Provides a little more information when a particular pathological case
is reached. This case can happen due to quirks in Views and almost
always indicates a bug in the infrastructure so it's important to know
what view is causing the problem.

Change-Id: I9527773a2a8660fcb5646c6802a489772db8a6e5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1876914
Commit-Queue: Dana Fried <dfried@chromium.org>
Commit-Queue: Charlene Yan <cyan@chromium.org>
Auto-Submit: Dana Fried <dfried@chromium.org>
Reviewed-by: Charlene Yan <cyan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708763}

Currently, RemoteSuggestionsService sounds more general than its true
usage, which is only for ZeroSuggestProvider.

This CL makes that more clear in the class comment, as well as adding a
TODO for a structural cleanup.

Bug: NONE
Change-Id: Iac4604e62b967d27ae65218813ecfd31e32d3d30
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1876875Reviewed-by: Justin Donnelly <jdonnelly@chromium.org>
Commit-Queue: Tommy Li <tommycli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708762}

Changes the static cast to fix a type mismatch.

Bug: 1016898
Change-Id: I4133129cc676065e0014d8c938bf04e3957b9962
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1875469
Commit-Queue: Joe DeBlasio <jdeblasio@chromium.org>
Reviewed-by: Joe DeBlasio <jdeblasio@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708761}

This CL adds the ability to hide the app icon view in Message Center's
NotificationHeaderView. This allows the Global Media Controls dialog to
hide the unnecessary Chromium icon that appears before the URL.

Bug: 1011047
Change-Id: Ic3e5a8e57ecfc14698697370e4fc0d5840c28ff0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1875276Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Tommy Steimel <steimel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708760}

Convert the implementation and all users of the
ui::ozone::mojom::GesturePropertiesService interface.

Bug: 955171
Change-Id: I8a70b91624fef3f7e94e25e2f7071d85a4dec42a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1864776Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Reviewed-by: Michael Spang <spang@chromium.org>
Reviewed-by: Oksana Zhuravlova <oksamyt@chromium.org>
Reviewed-by: Ryo Hashimoto <hashimoto@chromium.org>
Commit-Queue: Henrique Ferreiro <hferreiro@igalia.com>
Cr-Commit-Position: refs/heads/master@{#708759}

Once GPU hang is detected in the GPU watchdog V2, the watchdog will try
to load/unload a file from the hard drive and create/destroy a thread
to see if the GPU has made any progress in the current task. This will
give a hint if the system is busy. If the GPU is still stuck, Wait until
60 seconds has passed and check again the GPU status. After this, the
watchdog kill the GPU main thread.

This is to see whether the GPU thread is killed too early and to
compare with V2 on the number of hangs. This piece of code can be deleted
after the data is collected.

Bug:949839

Change-Id: I3a6afeed21776553d7416682baf6eed2d521286c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872166Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Commit-Queue: Maggie Chen <magchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708758}

Change-Id: If554173ce7a75ecbcbb0464288875a3a5510e6bd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869941Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Hui Yingst <nigi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708757}