GitLab

With flash removal happening in M88, remove RenderWidgetFullscreenPepper
which was used to implement the Flash Fullscreen setting. Note this
is different that the PPAPI Fullscreen which uses the normal blink
fullscreen request via the WebContainer::RequestFullscreen call.

BUG=1134674

Change-Id: I166596f6f5a677cc1028aed02f74297e0c458696
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2446593
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Bill Budge <bbudge@chromium.org>
Cr-Commit-Position: refs/heads/master@{#813822}

This fixes a couple of build failures happening on a class of Python
installs.

I must say I can't quite pin down what characteristics in a Python
installation would influence this, but it certainly does on all
my machines that I setup to be non-corp machines to try and mimic
what open source developers may do.

Change-Id: Id60cd8b10141ca1486e0cdadfc7392b6d2bba3e2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2445878
Commit-Queue: Manu Cornet <manucornet@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#813821}

This is a reland of c14fae86

Original change's description:
> [fuchsia][a11y] Refactors convert node ID logic.
>
> This change refactors the logic to convert an ax node ID to a fuchsia semantic node ID.
>
> It also fixes the bug where if a regular ax node had ID == 0, it would conflict with the root ID.
>
> R=yangsharon
>
> TEST: web_engine_unittests
> Change-Id: Ie4ee52c65fbd5ad623986e015ad521e66c5e67fe
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2430264
> Reviewed-by: Kevin Marshall <kmarshall@chromium.org>
> Reviewed-by: Sharon Yang <yangsharon@chromium.org>
> Commit-Queue: Lucas Radaelli <lucasradaelli@google.com>
> Cr-Commit-Position: refs/heads/master@{#811926}

Change-Id: I8b89cb69007c7e7557660ef70e71d28807fff436
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2441278
Auto-Submit: Lucas Radaelli <lucasradaelli@google.com>
Reviewed-by: Sharon Yang <yangsharon@chromium.org>
Reviewed-by: Sergey Ulanov <sergeyu@chromium.org>
Commit-Queue: Sergey Ulanov <sergeyu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#813820}

The mouse cursor will be hidden/shown when entering/exiting tablet mode,
instead of when internal touchpad input events are blocked/unblocked.
Examples:
1. Detach the internal keyboard/touchpad from a nocturne. It enters
tablet mode, but it does not block internal touchpad input events,
because the internal touchpad is gone. With the present CL, the mouse
cursor will be hidden. Without the present CL, it is not.
2. Attach an external pointing device and then flip the lid to tablet
position and back to clamshell position. Without the present CL, the
mouse cursor will be hidden when you flip to tablet position, and then
shown when you flip back to clamshell position. With the present CL,
that will not happen.

Fixed: 1123687, 1133031
Test: All/TabletModeControllerTest.ShowAndHideMouseCursorTest/?
Change-Id: I22cb7d3ffeb6d62b1b74f182c4bbe73b2338ff2b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2436325Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Commit-Queue: Avery Musbach <amusbach@chromium.org>
Cr-Commit-Position: refs/heads/master@{#813819}

Screenshots:
- Diagnostics App (before) http://shortn/_9PftSxKEqe
- Diagnostics App (after) http://shortn/_PIhlqmECzl

Bug: 1125150
Test: browser_tests --gtest_filter=DiagnosticsApp*
Change-Id: I32bee1b48287b83153f1c3d1b43285ccf7779db3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2443109
Commit-Queue: Michael Checo <michaelcheco@google.com>
Reviewed-by: Zentaro Kavanagh <zentaro@chromium.org>
Cr-Commit-Position: refs/heads/master@{#813818}

https://swiftshader.googlesource.com/SwiftShader.git/+log/01144ed91c35..6d93a63356e1

2020-10-05 capn@google.com Regres: limit the number of GL tests opening X connections
2020-10-05 bclayton@google.com CMake: Add flag for controlling the logging level

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

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_chromium_msan_rel_ng;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:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86
Bug: None
Tbr: swiftshader-team+autoroll@google.com
Change-Id: Ic871729d03f572debf6bb7bb7b4f4c5d75e86d58
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2450122Reviewed-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@{#813817}

https://webrtc.googlesource.com/src.git/+log/8e4cda7de008..04482985b204

2020-10-05 tommi@webrtc.org Revert "[Sheriff] Revert "Remove MessageHandler[AutoCleanup] dependency from StreamInterface.""
2020-10-05 perkj@webrtc.org Add experimental extension RtpVideoLayersAllocation
2020-10-05 sprang@webrtc.org Cleans up code related to video packetization overhead.
2020-10-05 danilchap@webrtc.org Factor out common logic for full svc scalability structures
2020-10-05 hta@webrtc.org Separate PeerConnection's self-message functions to a new file

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/+doc/master/autoroll/README.md

Bug: None
Tbr: webrtc-chromium-sheriffs-robots@google.com
Change-Id: I85ba25e24ccb443802048793d7a844d4bfe84c48
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2448687Reviewed-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@{#813816}

This replaces the existing virtual implementations of
TransformOperation::CanBlendWith() with a single one that compares
PrimitiveType() values, as defined in the spec. Years ago, CanBlendWith
was only used by BlendedBoundsForBox, and returned false on operation
types not supported by that method. As these checks are currently in
BlendedBoundsForBox itself, and CanBlendWith is used in some Blend()
implementations, eliminate the return false cases in favor of the
as-specced primitive type comparison.

As CanBlendWith is now to-spec for all operation types, replace the many
ad-hoc primitive type comparisons with calls to CanBlendWith(). Change
if/return type checks in TransformOperation::Blend() to DCHECKs as the
there is already a type check at the call site in TransformOperations,
so these should always succeed. In the case of SkewTransformOperation,
replace the loose type check (which would allow blending between skewX
and skewY which have different primitive types) with CanBlendWith. This
causes no behavioral change since a primitive type comparison already
existed in the caller.

Change-Id: Ife892b72798fe81d61ff6528deff064f41bdbfbb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2432672Reviewed-by: Kevin Ellis <kevers@chromium.org>
Reviewed-by: Ian Vollick <vollick@chromium.org>
Commit-Queue: George Steel <gtsteel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#813815}

This reverts commit d46bdb4f.

Reason for revert: Added web test is timing out on Mac10.15 Tests
https://ci.chromium.org/p/chromium/builders/ci/Mac10.15%20Tests/4574

Original change's description:
> [Editing] Fix canonical caret position at line break
>
> Consider this testcase:
>     <style>div { width: min-content; padding: 5px; }</style>
>     <div contenteditable>line1<wbr>line2</div>
> which is rendered as
>     line1
>     line2
>
> Before this patch, when clicking at the beginning of the 2nd line, the
> caret would appear at the end of the 1st one, because CanonicalPosition
> would search backwards even with a downstream affinity.
>
> Also, when clicking at the beginning of the 1st line and pressing the
> down arrow key, the caret would move to the end of the 1st line instead
> of to the beginning of the 2nd one. And pressing the key again would
> have no effect, the caret would refuse to go down.
>
> This patch fixes these problems by making CanonicalPosition take a
> TextAffinity parameter which affects whether the canonical position is
> first searched backwards or forwards. If no suitable candidate is found,
> it will still search in the other direction.
>
> And then, VisiblePosition::Create takes care of deciding between the
> upstream and the downstream canonical positions, depending on the
> affinity and whether there is a line break.
>
> Bug: 1002937
>
> Web tests:
> TEST=external/wpt/editing/run/caret-navigation-around-line-break.html
>
> Unit tests:
> TEST=All/ParameterizedVisibleUnitsLineTest.inSameLine/0
> TEST=All/ParameterizedVisibleUnitsLineTest.inSameLine/1
> TEST=All/ParameterizedVisibleUnitsWordTest.StartOfWordShadowDOM/0
> TEST=All/ParameterizedVisibleUnitsWordTest.StartOfWordShadowDOM/1
> TEST=VisiblePositionTest.ShadowV0DistributedNodes
> TEST=VisibleUnitsLineTest.endOfLine
> TEST=VisibleUnitsLineTest.isEndOfLine
> TEST=VisibleUnitsLineTest.isLogicalEndOfLine
> TEST=VisibleUnitsLineTest.isStartOfLine
> TEST=VisibleUnitsLineTest.logicalEndOfLine
> TEST=VisibleUnitsLineTest.logicalStartOfLine
> TEST=VisibleUnitsLineTest.startOfLine
> TEST=VisibleUnitsTest.canonicalPositionOfWithHTMLHtmlElement
> TEST=VisibleUnitsTest.canonicalPositionOfWithInputElement
> TEST=VisibleUnitsTest.canonicalizationWithCollapsedSpaceAndIsolatedCombiningCharacter
>
> Change-Id: I82d86d40a87513b2e92c024735957e9f71154094
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2410404
> Commit-Queue: Oriol Brufau <obrufau@igalia.com>
> Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#813744}

TBR=yosin@chromium.org,xiaochengh@chromium.org,obrufau@igalia.com

Change-Id: I5f6da8b5b9be5167cf49dd5b27d0f9c03b0b285e
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 1002937
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2450770Reviewed-by: Kristi Park <kristipark@chromium.org>
Commit-Queue: Kristi Park <kristipark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#813814}

PredictionMetricsHandler appears to be designed to work for anything
that is predicting points. However, it currently only reports metrics
in the Event.InputEventPrediction.Scroll* histograms. De-couple the
class from these histograms so it can be used for things only than
scroll metrics.

Bug: 1133785
Change-Id: Ib34129fc46b20b45810cbd5ca195483e88c513e2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2441197Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Commit-Queue: Mario Bianucci <mabian@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#813813}

This reverts commit fdae2298.

Reason for revert: Test is causing Fuchsia trunk builder to fail https://ci.chromium.org/p/chrome/builders/ci/fuchsia-x64-trunk

Original change's description:
> [fuchsia][a11y] Sends full semantic tree when semantics are enabled.
>
> This change fixes the bug where chrome was sending the full semantic tree only for the first time that semantics were enabled. This happened because the semantic tree was not getting cleared on the chrome side when disabled. when semantic were disabled / enabled, the events fired on the tree included only the diffs from the previous state of the tree.
>
> Test: web_engine_browsertests
>
> Bug: fuchsia:59680, 1134147
> Change-Id: I8266d6436f9bfb9ee9e89a0f46c0916bac7a5e75
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2442646
> Commit-Queue: Lucas Radaelli <lucasradaelli@google.com>
> Reviewed-by: Sergey Ulanov <sergeyu@chromium.org>
> Reviewed-by: Sharon Yang <yangsharon@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#813771}

TBR=wez@chromium.org,sergeyu@chromium.org,teisenbe@google.com,yangsharon@chromium.org,lucasradaelli@google.com

Change-Id: Id3df2d7e4c31632f65d2dcc4a2a9b07fc92f9b83
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: fuchsia:59680
Bug: 1134147
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2450693Reviewed-by: Sharon Yang <yangsharon@chromium.org>
Commit-Queue: Sharon Yang <yangsharon@chromium.org>
Cr-Commit-Position: refs/heads/master@{#813812}

TBR=ikilpatrick@chromium.org

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

This change depends on
https://android-review.googlesource.com/c/platform/external/perfetto/+/1438933

Bug: 1119834
Change-Id: I55bc44de601479704fd35c2f12ccad2459a61fb5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2431566Reviewed-by: Sami Kyöstilä <skyostil@chromium.org>
Reviewed-by: Mikhail Khokhlov <khokhlov@google.com>
Commit-Queue: Julia Semavina <nuwanda@google.com>
Cr-Commit-Position: refs/heads/master@{#813810}

These histograms are no longer needed, see bug for more context.

Bug: 1132985
Change-Id: If6a0def7f61923cc2ce08aace717f90d5eacb9d5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2436351
Commit-Queue: John Delaney <johnidel@chromium.org>
Reviewed-by: Eric Robinson <ericrobinson@chromium.org>
Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#813809}

This change also includes moving the padding for check box set in
TosAndUmaFirstRunFragment to the xml.

Note that the covered scenario only includes the general UI and the
loading phase UI. The UI when FRE is skipped is not included.

Change-Id: I31577104b1dd793f9f708268944ed85b3d453cb8
Bug: 1120852
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2438094Reviewed-by: Theresa  <twellington@chromium.org>
Reviewed-by: Sky Malice <skym@chromium.org>
Commit-Queue: Wenyu Fu <wenyufu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#813808}

HardwareDisplayPlaneManager::BeginFrame currently iterates all the
planes active on a specific crtc and set in_use to false, so that they
can be used when building up the next frame to commit.

Not all the path of HDPM::AssignOverlayPlanes and HDPM::Commit end up
committing the planes though, this means a pageflip test, or a failing
pageflip, might end up leaving |in_use| set to false, while the crtc is
actually still using those planes.

Bug: 1127487
Test: HardwareDisplayPlaneManagerAtomicTest.{AssignPlanesRestoresInUse,PageflipTestRestoresInUse}

Change-Id: Iee7f6b87af7e38f9ac7c6dea0687cc37dc4c6493
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2446831
Commit-Queue: Daniele Castagna <dcastagna@chromium.org>
Reviewed-by: Mark Yacoub <markyacoub@google.com>
Cr-Commit-Position: refs/heads/master@{#813807}

Part 1/3 for relanding crrev.com/c/2426045.
The old files will be deleted in a follow up CL after the internal CL for updating references (https://chrome-internal-review.googlesource.com/c/clank/internal/apps/+/3301233) lands.

Bug: 1131415
Change-Id: Iadae724b6e00a04cbb84e46e04f2c2b1b687df42
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2442533Reviewed-by: Boris Sazonov <bsazonov@chromium.org>
Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Commit-Queue: Tommy Nyquist <nyquist@chromium.org>
Auto-Submit: Andrey Zaytsev <andzaytsev@google.com>
Cr-Commit-Position: refs/heads/master@{#813806}

This CL introduces a feature toggle than controls showing explicit save
prompts before storing address profiles.

Bug: 1135178
Change-Id: If72c323489a7cee20ea9d812ba8945b4dfe2e366
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2450094
Commit-Queue: Mohamed Amir Yosef <mamir@chromium.org>
Reviewed-by: Matthias Körber <koerber@google.com>
Cr-Commit-Position: refs/heads/master@{#813805}

Roll ChromeOS Airmont AFDO profile from 87-4265.0-1601286022-benchmark-87.0.4280.7-r1 to 87-4265.0-1601895675-benchmark-87.0.4280.7-r1

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/cros-afdo-airmont-chromium
Please CC c-compiler-chrome@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/+doc/master/autoroll/README.md

Tbr: c-compiler-chrome@google.com
Change-Id: Ie60f00449299d7d0aa39853879f59f1626e75148
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2450515Reviewed-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@{#813804}

This reverts commit bb269b0e and
attempts to solve the original issue in a different manner.

That commit attempted to solve the problem of column header labels
being cut off (https://crbug.com/1109129) by not setting a maximum
column width. That caused the issue of, when the window is re-opened,
that all the columns split the width of the table view. That means
that, for a large window, lots of space is wasted on columns with
small-width data, and no space is left for the "Task" column.

That commit also switched the autoresize style to "sequential". That
was meant to ensure that the "Task" column got the extra space when
the window was resized, but in fact it forces the *last* column to
get the extra space. I suppose "reverse sequential" was intended,
but reverting things is easier.

This CL fixes the problem by adjusting the maximum size to be at
least as large as the labels.

Bug: 1109129, 1134831
Change-Id: I4452fa2256ec05ce6cca9fbe1fee38df79eddbab
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2447099
Commit-Queue: Avi Drissman <avi@chromium.org>
Reviewed-by: Leonard Grey <lgrey@chromium.org>
Cr-Commit-Position: refs/heads/master@{#813803}

CalculatePreferredSize() calls GetHeightForWidth() which calls
CalculatePreferredSize() if there's no LayoutManager installed.

This change adds a new LayoutManager as a workaround that should not be
necessary (see linked bugs).

Bug: 1128500, 1135104
Change-Id: I0563e3b8c39c892dca84d488f207ebbb0deb4594
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2448772
Commit-Queue: Peter Boström <pbos@chromium.org>
Commit-Queue: David Bienvenu <davidbienvenu@chromium.org>
Auto-Submit: Peter Boström <pbos@chromium.org>
Reviewed-by: David Bienvenu <davidbienvenu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#813802}

Storing a GlobalFrameRoutingId is the preferred method of keeping a
reference to a RenderFrameHost

Change-Id: I70266e1e7e5d7c9863df43e300c26a1e7b82e563
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2449389Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
Commit-Queue: Jochen Eisinger <jochen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#813801}

Bug: 1135150, 1126350
Change-Id: Ic16867aa6db47e26af0a2d971fb5717a4028c43b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2449931Reviewed-by: Greg Kerr <kerrnel@chromium.org>
Commit-Queue: Robert Sesek <rsesek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#813800}

Add support for CTAP 2.1 PIN/UV Auth Protocol Two (6.5.11).

Bug: 1129946
Change-Id: I6e0f0bfa3164b84d1e428f83f86e11d4f3151419
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2440535Reviewed-by: Adam Langley <agl@chromium.org>
Commit-Queue: Martin Kreichgauer <martinkr@google.com>
Cr-Commit-Position: refs/heads/master@{#813799}

R=dpranke@google.com,nodir@chromium.org
CC=​chanli@chromium.org,iannucci@chromium.org

Change-Id: I8df1342d5c36e2de2cc2d7343bc07f128c78ce2c
Bug: 1017288
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2315008
Commit-Queue: Scott Lee <ddoman@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@google.com>
Cr-Commit-Position: refs/heads/master@{#813798}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/69b996bd..88d84cce

Please follow these instructions for assigning/CC'ing issues:
https://v8.dev/docs/triage-issues

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,vahl@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com

Change-Id: I4c8e886deb404daac32a76348ac4b68c75818078
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2449910Reviewed-by: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#813797}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/af5911446cd0..e6a8f4ed40bb

2020-10-03 engeg@google.com Instantiate the M87 builders
2020-10-03 yichengli@chromium.org Generate python bindings for artifacts.proto change
2020-10-02 frkoenig@chromium.org trogdor: enable hw tests
2020-10-02 chrome-bot@chromium.org Update config settings by config-updater.
2020-10-02 bmgordon@chromium.org cros lint: Disable warning for local in /bin/sh

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/chromite-chromium-autoroll
Please CC chrome-os-gardeners@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/+doc/master/autoroll/README.md

Cq-Include-Trybots: luci.chrome.try:chromeos-betty-pi-arc-chrome;luci.chromium.try:chromeos-kevin-rel
Tbr: chrome-os-gardeners@google.com
Change-Id: I80b5f98880f0ed05705ce23a0903903c131b9e8e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2450115Reviewed-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@{#813796}

VulkanWebEngineIntegrationTest.WebGLContextPresentWithVulkanFeature no
longer fails in local or bot testing so re-enable it.

Bug: 1104563
Change-Id: I8d91d71fb7916a9c2c5da559571aee08a23707f6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2446449
Commit-Queue: Sergey Ulanov <sergeyu@chromium.org>
Reviewed-by: Sergey Ulanov <sergeyu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#813795}

Fix one remaining tiny test failure, all others should now be fixed.
We should leave this flag around for at least one milestone just in
case, but if there are no issues then we can remove the flag and
hard-code it this way.

This is a big step towards getting rid of the "ignored and not
included in the tree" state.

Bug: 1063155
Change-Id: I92241af7ec752dc537919740ef96c7e149d460e5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2448656Reviewed-by: Aaron Leventhal <aleventhal@chromium.org>
Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#813794}

Currently OS_LINUX is defined on Chrome OS Build,
but it will be unset. This CL is the preparation to keep
the current behavior.

Bug: 1110266
Test: Built locally.
Change-Id: Ifffd315c669fd8d0d38ab41c8f4f7bbda6c0cbb7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2450129
Auto-Submit: Hidehiko Abe <hidehiko@chromium.org>
Commit-Queue: Eugene Zemtsov <eugene@chromium.org>
Reviewed-by: Eugene Zemtsov <eugene@chromium.org>
Cr-Commit-Position: refs/heads/master@{#813793}

Roll ChromeOS Broadwell AFDO profile from 87-4258.0-1601290734-benchmark-87.0.4280.7-r1 to 87-4265.0-1601892862-benchmark-87.0.4280.7-r1

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/cros-afdo-broadwell-chromium
Please CC c-compiler-chrome@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/+doc/master/autoroll/README.md

Tbr: c-compiler-chrome@google.com
Change-Id: I0615282cc895be787d6d053d539fcd069ebad135
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2450572Reviewed-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@{#813792}

Roll ChromeOS Silvermont AFDO profile from 87-4265.0-1601289755-benchmark-87.0.4280.7-r1 to 87-4265.0-1601890590-benchmark-87.0.4280.7-r1

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/cros-afdo-silvermont-chromium
Please CC c-compiler-chrome@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/+doc/master/autoroll/README.md

Tbr: c-compiler-chrome@google.com
Change-Id: Iea2d6b9f27ef1963377cc7d82dd34d3f4d27da39
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2450514Reviewed-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@{#813791}

This is a reland of dc61429b
after infra team fixed the incremental build issue: crbug/1133102

Original change's description:
> [Payments][Metrics] Extend expiry for ever-green metrics.
>
> Also updated ownership.
>
> Bug: 1128111
> Change-Id: Iba6ba54d4a47e02579faa69ff7078ba6ab012333
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2426977
> Commit-Queue: Danyao Wang <danyao@chromium.org>
> Reviewed-by: Mark Pearson <mpearson@chromium.org>
> Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
> Reviewed-by: Sahel Sharify <sahel@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#811232}

Bug: 1128111
Change-Id: I7c00c0cc30538381cda80e2dfb98148b944d6481
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2446891
Commit-Queue: Danyao Wang <danyao@chromium.org>
Reviewed-by: Danyao Wang <danyao@chromium.org>
Reviewed-by: Mark Pearson <mpearson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#813790}

Release_Notes: http://go/media_app-x20/relnotes/Main/media_app_202010050700_RC00.html

https://chrome-infra-packages.appspot.com/p/chromeos_internal/apps/media_app/app/+/F5O08dsIWdHTa7NozxSJmHAyJsTLlm6Zxo9jTQjw1qEC

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://skia-autoroll.corp.goog/r/media-app-chromium-autoroll
Please CC media-app@grotations.appspotmail.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/+doc/master/autoroll/README.md

Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome;luci.chrome.try:linux-chromeos-chrome-easwa
Bug: None
Tbr: media-app@grotations.appspotmail.com
Change-Id: I5d2ec3cd4b0c58c9f3e71c1807f4ffee6bfc00a1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2450112Reviewed-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@{#813789}

https://skia.googlesource.com/skia.git/+log/750261f41af6..00a8b5bb4fcb

2020-10-05 brianosman@google.com Revert "Revert "Convert sksl_frag.sksl to an IRIntrinsicMap""
2020-10-05 johnstiles@google.com Create TinyUnorderedMap class for small-N data storage.

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 jvanverth@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/+doc/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
Cq-Do-Not-Cancel-Tryjobs: true
Bug: None
Tbr: jvanverth@google.com
Change-Id: I5d7d6f8d134fd6d300c08dcc2fd9140736dc1a24
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2450117Reviewed-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@{#813788}

This CL fixes color type that we pass to the skia for the
FBO0. It changes two things:
* Use RGB565 if the surface uses 16 bit format .
* Fallback to RGBA is skia doesn't support rgb color type.

Bug: 1126490

Change-Id: I6f5342ac7bb128134afc2c5182a6c6b99600c7a9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2441311
Commit-Queue: Vasiliy Telezhnikov <vasilyt@chromium.org>
Reviewed-by: Jonathan Backer <backer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#813787}

https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/0afca615a816..256b2c258767

2020-10-05 sigurds@chromium.org [ts] Type-check front_end/coverage/CoverageDecorationManager.js with TypeScript
2020-10-05 bmeurer@chromium.org [ts] Type-check wasmparser_worker/WasmParserWorker.js with TypeScript
2020-10-05 sigurds@chromium.org [ts] Type-check front_end/coverage/CoverageListView.js with TypeScript
2020-10-05 sigurds@chromium.org [ts] Type-check front_end/coverage/CoverageView.js with TypeScript

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/devtools-frontend-chromium
Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.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/+doc/master/autoroll/README.md

Bug: chromium:1011811
Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com
Change-Id: Idd03c1c0b2612666fca703754724dd9426064eda
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2450118Reviewed-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@{#813786}

Set android:includeFontPadding="false" to better align favicon with URL.
Use padding instead of margin to get the right background color.
Show details link if there is a connection message.
Show red warning triangle if there is a connection security issue.
Also includes some general cleanup for margins.

Bug: 1135124
Change-Id: Iff1f880b51a2a8bd60ef0606afec03fea82e9318
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2449372Reviewed-by: Ehimare Okoyomon <eokoyomon@chromium.org>
Commit-Queue: Christian Dullweber <dullweber@chromium.org>
Cr-Commit-Position: refs/heads/master@{#813785}

This reverts commit 44f6ea57.

Reason for revert: crashes in stack_unwinder::Module::Load()

Original change's description:
> [Sampling profiler] Enable on ARM32 Android canary for render thread
>
> Enables the ThreadProfiler on Android canary channel Chrome releases
> for ARM32. The profiler is enabled solely on the renderer main thread
> for now, pending stability and performance metrics from the wild.
>
> Bug: 1004855
> Change-Id: If393653adf362f3fccbfa93078f45d88284fc81b
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2433125
> Commit-Queue: Mike Wittman <wittman@chromium.org>
> Reviewed-by: Etienne Pierre-Doray <etiennep@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#813548}

TBR=wittman@chromium.org,etiennep@chromium.org

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

Bug: 1135152, 1004855
Change-Id: I3e04e2b1f5174fb01e29bbf912f70517d1424af9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2448960Reviewed-by: Mike Wittman <wittman@chromium.org>
Commit-Queue: Mike Wittman <wittman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#813784}

This is necessary as embedders are pulling from canary, not stable,
which makes for a much smaller skew.

BUG=none
TEST=none

Change-Id: I28bc2aac2038fb5757c60ee5251cb281ea10cdd3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2450389Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#813783}