GitLab

|has_hw_overlay_support_| in the DC overlay Processor is updated after
display change. This cap is queried directly from
direct_composition_surface_win. All the other overlay_support
capabilities which are used for passing data have been removed.

|use_dc_overlays_for_video| is removed from |capabilities| of
gles2_cmd_decoder and gles2_cmd_decoder_passthrough.

|supports_dc_video_overlays| is removed from |capabilities| of
output_surface.



Bug: 1042989
Change-Id: I9fcfd0a0e9e2e19db00ea0418cfd299e17664cae
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2068920Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Reviewed-by: Alex Gough <ajgo@chromium.org>
Reviewed-by: weiliangc <weiliangc@chromium.org>
Commit-Queue: Maggie Chen <magchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750268}

This change adds metrics, for the gesture navigation screen, which
records the amount of time that each individual page is shown to the
user (pages include Intro, Home, Overview, and Back).

Bug: 1055690
Change-Id: Iddc76fc5f3b1666813693418b51ae943eec067fe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2098770Reviewed-by: Brian White <bcwhite@chromium.org>
Reviewed-by: Toni Baržić <tbarzic@chromium.org>
Commit-Queue: Matthew Mourgos <mmourgos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750267}

Bug: 1061460
Change-Id: I5d5c585ff3cecae9ac69c12737130bda89257b11
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2102778Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Commit-Queue: Michael Thiessen <mthiesse@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750266}

- Defined QueryTile proto and in-memory struct.
- Defined a collection_store interface.
- Implemented QueryTileStore.

TODO in next CLs: proto_conversion, query_tile_store_unittest,
query_tile_group_manager(tree operations).

Bug: 1060805c
Change-Id: I6da3c9be67b34843594476ae1c1302206a19f1fe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2099228
Commit-Queue: Hesen Zhang <hesen@chromium.org>
Reviewed-by: Min Qin <qinmin@chromium.org>
Reviewed-by: Xing Liu <xingliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750265}

In https://crrev.com/4d25b125dae5 I changed the scroll tree parenting
logic so that elements in position:fixed subtrees have the LayoutView's
ScrollNode as the scroll parent. This made sense since scrolling over a
fixed element should cause the document to scroll. However, this is
slightly different from how the transform tree looks. Because scrolling
the document doesn't cause position:fixed eement so translate, these
nodes don't have the LayoutView's ScrollTranslation transform node as an
ancestor.

As a simple example, a scrolling document with a position:fixed <div>
scroller will generate the following scroll and transform trees
(approximately):

      *ScrollTree*                          *TransformTree*

         Root                                    Root
          |                                       |
VisualViewport Translation                 VisualViewport
          |                                  /         \
  LayoutView Translation                    /           \
          |                             Fixed      LayoutView
  Fixed Scroller Translation


The situation above makes sense for what parent-child relationships mean
in each tree: the scroll tree encodes how scrolls chain; scrolling on a
child should bubble up to its parent in this tree. The transform tree
encodes the physical effect of scrolling a node. In the above example,
scrolling from the fixed scroller should bubble up to the LayoutView
(when the scroller is fully scrolled) but scrolling the LayoutView will
not cause movement of the fixed scroller.

The above makes sense but caused sticky code to get confused. A sticky
constraint is attached to the scroll translation node. With the above
situation, this meant that inside a fixed subtree, we'd attach it to the
VisualViewport's scroll translation node. This was unexpected; the
constraints are in "document coordinates", meaning that to translate
them into the viewport space we must apply the scroll offset [1]. The
compositor would use the visual viewport's (typically 0) scroll offset
to adjust these values, leading to incorrect calculations.

This previously worked because the scroll node used in a fixed subtree
would be the visual viewport (before the CL mentioned at the top). In
[2] we check whether the current overflow clip is also our scroller,
prior to the CL this check have failed because "our scroller" was the
visual viewport but our clip was the LayoutView. Now they are both the
LayoutView.

The fix in this CL is to make the check in [2] more stringent; we also
want to make sure that our scroller is the nearest scroller in the
transform tree. That is, if we scroll it, will we cause the current node
to move? If not, we don't need a sticky constraint on the compositor
because user scrolling can't change the sticky's offset relative to its
clip.

[1] https://cs.chromium.org/chromium/src/cc/trees/property_tree.cc?l=321&rcl=628f869d1fda631a85f051ad13b5d278319298fc
[2] https://cs.chromium.org/chromium/src/third_party/blink/renderer/core/paint/paint_property_tree_builder.cc?l=553&rcl=99a5a1266f303ba6ae46174a2b4cbd165ea7e934

Bug: 1019142
Change-Id: I781943ff43514905d399803c780c6081d7d47e8f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2097542Reviewed-by: Robert Flack <flackr@chromium.org>
Commit-Queue: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750264}

Extend metrics Arc.Runtime.Performance.* until 2021-03-11

TEST=None

Bug: b/151314714
Change-Id: Ib07a54a2f162e8bedde7944262e146c89dcc1186
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2101721
Commit-Queue: Mustafa Camurcu <camurcu@chromium.org>
Reviewed-by: Yury Khmel <khmel@chromium.org>
Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750263}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/ef7ec269b5b5..034b5438d90f


Created with:
  gclient setdep -r src-internal@034b5438d90f

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
Bug: chromium:1047357
Tbr: jbudorick@google.com
Change-Id: I7c6dbc2abb8e7b2a7f8c318dcaf2ea47460e1100
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2103032Reviewed-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@{#750262}

Extend metric Arc.PlayStoreShown.TimeDelta until 2021-03-11

TEST=None

Bug: b/151314714
Change-Id: Ia5e9320858138a4e6d7f12d0d77cbf2a7f587efe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2101545
Commit-Queue: Mustafa Camurcu <camurcu@chromium.org>
Reviewed-by: Yury Khmel <khmel@chromium.org>
Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750261}

Today, most parts of the code assume the browser controls min-height
is 0. This causes issues with the layout size and the fullscreen mode.
The most obvious issues currently are:
- If a min-height is set, ChromeFullscreenManager#controlsResizeView()
always returns true since the controls aren't completely hidden.
- Similarly if a min-height is set, position: fixed elements are sized
as if the controls are fully showing.

This CL changes the "browser controls resize/shrink blink" logic to try
and fix the issues listed above. With the changes in this CL, the
controlsResizeView bit will be false if the controls are at the
min-height.

Bug: 1049301
Change-Id: Ieb95e92c983b56b42a640f726c60c2eec9964064
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2048276
Commit-Queue: Sinan Sahin <sinansahin@google.com>
Reviewed-by: Theresa  <twellington@chromium.org>
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750260}

Extend metrics Arc.PlayAutoInstallRequest.* until 2021-03-11

Bug: b/151314714
Change-Id: Id7734c89b42aa1122762a82f76b49bd80fd3df77
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2101543
Commit-Queue: Mustafa Camurcu <camurcu@chromium.org>
Reviewed-by: Yury Khmel <khmel@chromium.org>
Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750259}

This uses the Clang profiling config during the instrumentation step of
a PGO build. This allows getting the profiling data out of the sandboxed
processes. This is not an ideal end state, ideally the coverage
configuration should be refactored and things common to the two
configurations should be moved to a new base config.

This requires to use the new version of goma, see go/ma-rbe-dogfood
(see crbug.com/990981#c26 for more details).

To build a PGInstrumented build (first step to do a PGO build) compile
with the following GN args:
  is_component_build = false
  is_debug = false
  chrome_pgo_phase = 1
  use_goma = true

Bug: 1056189
Change-Id: I717efdcbb6993ad574acce4c0f91eb5fb5bf3972
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2076424
Commit-Queue: Sébastien Marchand <sebmarchand@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750258}

When Wi-Fi sync is first enabled and a list of synced networks
has to be merged with the local networks on a device, use the last
connected timestamp to decide which configuration should be used.

Bug: 966270
Change-Id: Id7688a0fdb9e7922cee8ffec0ef69b804436e3e9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2093274Reviewed-by: James Vecore <vecore@google.com>
Commit-Queue: Jon Mann <jonmann@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750257}

The iOS tests were being run as gtests, but with the isolated merge
script because of iOS' output format (standard JSON output). Moving
them to use isolated_scripts instead, as it shortens the definition
in test_suites.pyl, and accomplishes the same.

Bug: 1055164
Change-Id: Icffb1a1cf72681e2ad08c5a3031d50e842a003f6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2100714Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Jeff Yoon <jeffyoon@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750256}

Extend lifetime of Arc.IconLoadFromFileTime.* metrics
until 2021-03-11

Bug: b/151314714
Change-Id: I2252633d23d8747fd6731f2d4eb3ef69709e550e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2100636
Commit-Queue: Mustafa Camurcu <camurcu@chromium.org>
Reviewed-by: Yury Khmel <khmel@chromium.org>
Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750255}

The first ever default desk created after boot should not
trigger any UMA stat reporting.

The histograms are deprecated, and replaced by
Ash.Desks.NewDesk2, and Ash.Desks.DesksCount2 respectively.

BUG=1060709

Change-Id: I09f851009aa05a71e73e914692919d2f8150344e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2095973Reviewed-by: Mark Pearson <mpearson@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Commit-Queue: Ahmed Fakhry <afakhry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750254}

Extend lifetime of Arc.FirstAppLaunchRequest.TimeDelta
metric until 2021-03-11

Bug: b/151314714
Change-Id: I8308e1684468acc8aef37927d40e529ffd05249e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2100948
Commit-Queue: Mustafa Camurcu <camurcu@chromium.org>
Reviewed-by: Yury Khmel <khmel@chromium.org>
Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750253}

This change modifies LeakDetectionRequest to explicitly check for
HTTP_TOO_MANY_REQUESTS, indicating the user ran out of quota. It
modifies corresponding enums and introduces an optional LeakDetectionError
to the LookupSingleLeakCallback, so that the error can be forwarded to
consumers like the Password and Safety Check.

Bug: 1061108
Change-Id: I86d561b47bbf39e996a425dbd3459eb8bbda52ea
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2100941
Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org>
Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750252}

Add helper functions to do the conversion and switch to gfx equivalents.

Bug: 10611824
Change-Id: Ie4633980d37ba97a92f46b8f465356a4334ac483
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2101984
Commit-Queue: Lei Zhang <thestig@chromium.org>
Reviewed-by: Daniel Hosseinian <dhoss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750251}

Bug: 524134
Change-Id: I99e53d134f2542f06d63519ad2a96b4d24738649
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2101494Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750250}

No change to production logic, only test shell.

This adds 'system_webview_shell_package_name' to configure WebView
shell's package name. This is handy for Android emulators, because the
default package name will cause signature mismatches.

I kept the original documentation (for removing the shell from the
system image) because it may be relevant for some use cases. But I hope
the GN arg is a simpler solution for most developers.

Fixed: 1061211
Test: $OUT/bin/system_webview_shell_apk package-info (verify name)
Test: $OUT/bin/system_webview_shell_apk install (succeeds on emulator)
Test: Upload to gerrit > open file > click "gitiles" > verify markdown
Change-Id: I24a35524bc5042da33b8203637ec67a0f610f363
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2101859Reviewed-by: Hazem Ashmawy <hazems@chromium.org>
Commit-Queue: Nate Fischer <ntfschr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750249}

This is a follow up to https://crrev.com/i/2756704.

Bug: 1047357
Change-Id: I850d2478e978d9dab188f9a2a0913ac30a2083c2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2101716
Commit-Queue: Gang Wu <gangwu@chromium.org>
Auto-Submit: Natalie Chouinard <chouinard@chromium.org>
Reviewed-by: Gang Wu <gangwu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750248}

There are variants of viz_unittests that use SkiaRenderer Dawn if it is
enabled in the build, and variants of cc_unittests are underway. Add
them to the SkiaRenderer Dawn FYI bot, which builds with the gn arg
"use_skia_dawn = true".

Bug: 1021566
Change-Id: Ia0d96a9389308f45e4a697455f396d69d7d20db4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2094758Reviewed-by: Yuly Novikov <ynovikov@chromium.org>
Commit-Queue: Sean Gilhuly <sgilhuly@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750247}

This CL migrates UnsizedMedia from feature policy to document policy.

Following web tests are being migrated:
- unsized-media.tentative.https.sub.html
- unsized-media-reporting.html

Following web tests are removed, because document policy currently
does not have a js API to list all features available.
- feature-policy-unsized-media-disabled.html
- feature-policy-unsized-media-enabled.html

Bug: 993790
Change-Id: Id5e0189c0277c940177460380970eab0015109d0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2097028
Commit-Queue: Charlie Hu <chenleihu@google.com>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Reviewed-by: Ian Clelland <iclelland@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750246}

This CL moves the Java-side definition of the kGenericSensorExtraClasses
Feature from ChromeFeatureList to a new DeviceFeatureList class that
lives in //services/device/public/java. This will allow non-Chrome
embedders to query the status of the Feature from Java.

Bug: 1058597
Change-Id: Iab3c75fea6c8755de52714be7776547a774842d4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2095445
Commit-Queue: Robbie McElrath <rmcelrath@chromium.org>
Reviewed-by: Henrique Nakashima <hnakashima@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Reviewed-by: Colin Blundell <blundell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750245}

TBR=dmurph@chromium.org

Bug: 1061251
No-Try: true
Change-Id: I30bbc831be9069b6b246242f3ed4eeb46576e65c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2103247
Commit-Queue: Oksana Zhuravlova <oksamyt@chromium.org>
Reviewed-by: Oksana Zhuravlova <oksamyt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750244}

There is a discrepancy between BlinkAXTreeSource::GetChildren() and
BlinkAXTreeSource::GetParent().

- GetChildren() does not return direct children when they are ignored
  and not included in the tree. This is because when
  AXNodeObject::InsertChild() visits an object that is ignored and not
  included in tree, it recurses and inserts the next generation.
- GetParent() always returns the direct parent.

This discrepancy an lead to confusion within AXTreeSerializer, with
respect to analyzing reparenting.

Bug: 651614
Change-Id: I4e4c8c6a2900cf5516cc98f3b260e619220ea7e9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2095882
Auto-Submit: Aaron Leventhal <aleventhal@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Reviewed-by: Adam Ettenberger <Adam.Ettenberger@microsoft.com>
Reviewed-by: Jacques Newman <janewman@microsoft.com>
Commit-Queue: Mounir Lamouri <mlamouri@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750243}

This reverts commit 823317ab.

Reason for revert: unit_tests failing on https://ci.chromium.org/p/chromium/builders/ci/Linux%20Tests%20%28dbg%29%281%29/87477 and https://ci.chromium.org/p/chromium/builders/ci/Win%207%20Tests%20x64%20%281%29/64989

Original change's description:
> [Profiles] Record state of profiles on session start
>
> This CL introduces new metrics about profile representation state that
> get recorded on session start:
>  - Profile.State.Avatar
>  - Profile.State.LastUsed
>  - Profile.State.Name
>  - Profile.State.UnconsentedPrimaryAccountType
> all with 6 suffixes that zoom into particular subpopulations of users.
>
> Bug: 1060113
> Change-Id: Ifdb7dff6638ba29896e33e4f99086c8ca6e21b00
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2096697
> Commit-Queue: Jan Krcal <jkrcal@chromium.org>
> Reviewed-by: Alex Ilin <alexilin@chromium.org>
> Reviewed-by: David Roger <droger@chromium.org>
> Auto-Submit: Jan Krcal <jkrcal@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#750107}

TBR=droger@chromium.org,jkrcal@chromium.org,alexilin@chromium.org

Change-Id: I2c6a43c3fd5be4c0eb3d73f66007c6f1b209060a
No-Presubmit: true
No-Tree-Checks: true
No-Try: false
Bug: 1060113
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2102779
Commit-Queue: Oksana Zhuravlova <oksamyt@chromium.org>
Reviewed-by: Oksana Zhuravlova <oksamyt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750242}

This moves ChromeFeatureList.setTestFeatures to a new base.FeatureList
class so it can be shared by other *FeatureList implementations.
Eventually this class will the the primary method of querying Feature
state, but for now it only handles test configuration.

See crrev.com/c/2095445 and the bug for more information.

Bug: 1060097
Change-Id: Idd0c8ebc447f9f936192f81fc1465600f28ad7d7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2099470Reviewed-by: Henrique Nakashima <hnakashima@chromium.org>
Reviewed-by: Richard Coles <torne@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Robbie McElrath <rmcelrath@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750241}

A number of browser tests use URLLoaderInterceptors solely to look at
parameters for requests, and they have similar boilerplate code to set
that up. This CL moves URLLoaderMonitor from web_request_apitest to
content/public/test/, and switches over a couple browser tests to use
it.

Bug: 1052148
Change-Id: Id1e9a474ecd77017659f471a54621d0b9c35b0ef
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2092276Reviewed-by: Karan Bhatia <karandeepb@chromium.org>
Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Reviewed-by: Min Qin <qinmin@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Shivani Sharma <shivanisha@chromium.org>
Commit-Queue: Matt Menke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750240}

By unifying  AddChildren() methods, the code is easier to follow and
harder to break.

NOTRY=true

Bug: None
Change-Id: I385a73fa5bb72cb4b733a4f42bd9f35727660ec0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2101372
Commit-Queue: Aaron Leventhal <aleventhal@chromium.org>
Reviewed-by: Nektarios Paisios <nektar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750239}

TBR=jbudorick@chromium.org

Bug: 1061249
No-Try: true
Change-Id: Ia8392d4bb8c697cea1bd04d7a67cdbbb4f571bc1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2103254
Commit-Queue: Oksana Zhuravlova <oksamyt@chromium.org>
Reviewed-by: Oksana Zhuravlova <oksamyt@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750238}

The dummy GPU builders are triggered by non-branched builders that
won't have the bucketed_triggers property set.

Bug: 1061502
No-Try: true
Change-Id: I0054470418bd0736f4e256c5ae49680799362e71
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2103249
Commit-Queue: John Budorick <jbudorick@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Auto-Submit: Garrett Beaty <gbeaty@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750237}

Config mb so that this try builder can build with needed gn configs.

Bug: 943883
Change-Id: Iad397828705170bf88040922cb4a8d1d74e9dd95
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2101723Reviewed-by: Aaron Gable <agable@chromium.org>
Commit-Queue: Zhaoyang Li <zhaoyangli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750236}

Put new implementation of ResizeObserver::observe behind
ResizeObserverUpdates flag to prevent compat issues until the final
version of Resize Observer is shipped. No JavaScript error shold
be thrown when unsupported second argument is passed to
ResizeObserver::observe(). Issue was introduced in the
following CL: http://crrev.com/c/2004051

Bug: 1056535
Change-Id: I7e6d319d14f9d318e0f68ea3e056cfa27eb7f937
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2077280
Commit-Queue: Sahir Vellani <sahir.vellani@microsoft.com>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Reviewed-by: Daniel Libby <dlibby@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#750235}

This Cl modifies AppActivityRegistry to
correctly handle corner cases where applications
are re-installed by doing the following:
1. If the running active time of an app is non-zero
restore the application when initializing AppActivityRegistry
even if the application is uninstalled.

2. Only remove entries in CleanRegistry if the application
is uninstalled, has no unreported activities and its running
active time is zero.

Bug: 1060340
Change-Id: Idbefe82a686eaa56d31488d305f93c379d7b2bda
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2097303
Commit-Queue: Yilkal Abe <yilkal@chromium.org>
Reviewed-by: Aga Wronska <agawronska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750234}

Handle fragmentation for fieldset content with a negative margin block
start. The following was required to accomplish this:

1. Don't wait to layout fieldset content until there is available
space in the current fragment.
2. Break before fieldset content if necessary.

Bug: 875235
Change-Id: I0c95fe37694e2a0022ed9222db0a7af13cc958b9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2099284
Commit-Queue: Alison Maher <almaher@microsoft.com>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750233}

https://android.googlesource.com/platform/external/perfetto.git/+log/658be97b1940..acd3faab763a

git log 658be97b1940..acd3faab763a --date=short --first-parent --format='%ad %ae %s'
2020-03-13 taylori@google.com Merge "ui: Use track name helper for thread tracks"
2020-03-13 hjd@google.com Merge "ui: Fix percentage in thread state label"
2020-03-13 fmayer@google.com Merge "Revert^2 "Assert extra_guardrails fails on user.""

Created with:
  gclient setdep -r src/third_party/perfetto@acd3faab763a

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/perfetto-chromium-autoroll
Please CC perfetto-bugs@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

Bug: None
Tbr: perfetto-bugs@google.com
Change-Id: Ifca881095f3a2bf1e199d9e30252ffb7bff09106
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2103031Reviewed-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@{#750232}

A previous patch added clamping for sub-pixel borders to ensure they
did not round to zero size. The change was done in paint code, leaving
the borders as sub-pixel sized in layout. The code prior to that patch
clamped the borders during style conversion but did not account for zoom,
meaning borders disappeared under zoom.

This change removes the clamping in paint and reverts to clamping in the
style conversion code, only this time accounting for zoom when considering
whether to clamp or not. This will prevent borders growing too large as
content is made larger, while preventing sub-pixel borders from disappearing
as content is made smaller.

Design Doc: https://docs.google.com/document/d/1fAYkOFxp2Luh6OOoXxtwOehmvNRGNss58ibQtVXL0Tw/edit?usp=sharing

Bug: 763402, 834489
Change-Id: Iba2ae80b0a981736b93453c1058fd586ba10212c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2097514
Commit-Queue: Stephen Chenney <schenney@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750231}

Screenshot: http://screen/eqiMqP4ssYd

Bug: 1043108
Change-Id: I04526e314d7666e1b8d5ba71deed50f7cb0f4ba7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2096556Reviewed-by: Kush Sinha <sinhak@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Anastasiia Nikolaienko <anastasiian@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750230}

BUG=1061042

Change-Id: I91c3d60d0f9be69fb8ed82b3ca8f67434b4b84c6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2100716
Commit-Queue: Min Qin <qinmin@chromium.org>
Reviewed-by: Xing Liu <xingliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750229}