GitLab

This patch adds the Get/Update Settings APIs so that we can show and
update it in the Chrome OS Settings ambient mode page, which will be
implemented in a follow up cl.

Bug: b/148483925
Test: manual
Change-Id: Ia74d875813860a6abbfdc01479a67fed0c029fb8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2125685
Commit-Queue: Tao Wu <wutao@chromium.org>
Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#755531}

base::Bind can now bind __stdcall calls and indirection through
lambdas is not needed.

Bug: 1053729
Change-Id: Id9381a9370db07319f2e0998827b726a722281c7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2132932Reviewed-by: Joshua Pawlicki <waffles@chromium.org>
Commit-Queue: Sorin Jianu <sorin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#755530}

SkiaRenderer renders washed out colors when using PQ color space with a
RGB10A2 surface.  This happens in M81 because the default color space
and buffer format for HDR was changed to PQ and RGB10A2 on Windows.

The root cause is that the default PQ SkColorSpace uses normalized
luminance values whereas Chrome needs to output scaled values based on
the white point.  The fix is to construct a PQish SkColorSpace using the
scaling factor.

This CL includes pixel tests for HDR10 and scRGB linear.  The HDR10 test
fails before this fix.  The HDR10 test is temporarily suppressed due to
infra issues causing the test to run on different Windows versions.

Bug: 1058580, 1066979
Change-Id: I5a6b91631377a300010d045aaf44a9375d8ffa55
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2109254
Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org>
Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Reviewed-by: ccameron <ccameron@chromium.org>
Reviewed-by: kylechar <kylechar@chromium.org>
Reviewed-by: Brian Osman <brianosman@google.com>
Cr-Commit-Position: refs/heads/master@{#755529}

User-Agent isn't currently allowed to be set. Mark the TestExceptations
against it.

BUG=571722

Change-Id: I66e23de22c0cbf4e47c64a2b1f3b0adae9f5d886
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2132969Reviewed-by: Robert Ma <robertma@chromium.org>
Commit-Queue: Robert Ma <robertma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#755528}

This CL migrates this test out of
third_party/blink/web_tests/css3/flexbox and into the WPT-specific
directory, adding links to the relevant specs and a test assertion
describing its purpose and renames it to
flex-item-z-ordering-001.html.

Bug: 1063749
Change-Id: I36a4329db16e6cb805ada486ebbebe565a66c97a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2131550
Commit-Queue: David Grogan <dgrogan@chromium.org>
Reviewed-by: Robert Ma <robertma@chromium.org>
Reviewed-by: David Grogan <dgrogan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#755527}

This CL does the following:
a) Add a new enum policy to set the Safe Browsing protection level.
   This policy is called: SafeBrowsingProtectionLevel
b) Drops a policy named SafeBrowsingEnhancedProtection
   This policy never shipped.
c) Deprecates an existing boolean policy named: SafeBrowsingEnabled.

The new policy in a) has three values:
0 - Safe Browsing gets disabled. This is equivalent to setting
    SafeBrowsingEnabled to false.
1 - Safe Browsing gets enabled in standard mode. This is equivalent to
    setting SafeBrowsingEnabled to true.
2 - Safe Browsing Enhanced Protection gets enabled.

This CL also adds a handler class called SafeBrowsingPolicyHandler the
purpose of which is to map the policy being deprecated
(i.e. SafeBrowsingEnabled) and the policy being introduced
(i.e. SafeBrowsingProtectionLevel) to the appropriate prefs.

For details, please see: go/crsb-safer-chrome-policy

Bug: 1066371, 1056483
Change-Id: I37115f04e07ba190504b9cac85c5e0694f4aec12
Fixed: 1066371
TBR: blundell (for '+components/strings/grit/components_strings.h' DEPS)
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2129284
Commit-Queue: Varun Khaneja <vakh@chromium.org>
Auto-Submit: Varun Khaneja <vakh@chromium.org>
Reviewed-by: Pavol Marko <pmarko@chromium.org>
Reviewed-by: Martin Šrámek <msramek@chromium.org>
Reviewed-by: Bettina Dea <bdea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#755526}

Change-Id: Iecdfb6d697c1aa070618ebe3d9e8d476f746cbc0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2132675
Commit-Queue: Sam Bowen <sgbowen@google.com>
Reviewed-by: Becca Hughes <beccahughes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#755525}

The 2 tests were failing on wpt.fyi because the coordinates passed to Actions.pointerMove were not integers (like on local run). Since Actions.pointerMove expects integer coordinates, the tests were failing with an exception.
Use Math.ceil on coordinates passed to Actions.pointerMove. Apply memory leak fix.

Bug: 810882
Change-Id: I399f763fa03ebd98167fd060ad1769e8dd7f9d30
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2132950
Commit-Queue: Liviu Tinta <liviutinta@chromium.org>
Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#755524}

BUG: 961064

Change-Id: I14020da7f64f1cc5dd14b4ca89340d554031a82d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2130486
Commit-Queue: Joe Downing <joedow@chromium.org>
Reviewed-by: Joe Downing <joedow@chromium.org>
Cr-Commit-Position: refs/heads/master@{#755523}

The patch adds owning_element to CSSTransition class. Now the
CSSTransition have an owning_element and we will clear the owning
element if the animation disassociate from the owning_element.

The next follow up patches will enable us to use owning element to
compare the composite ordering. And a clean-up will required to fixed
the previous work-around due to no owning element.
As per spec: https://drafts.csswg.org/css-transitions-2/#owning-element


Bug: 1043778
Change-Id: Ic034ae25a39bacdab0bddbcc4a2ebab1a8a65a57
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2121453
Commit-Queue: Hao Sheng <haozhes@chromium.org>
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Reviewed-by: Majid Valipour <majidvp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#755522}

Switches all tests that use Skia Gold to use a mixin instead of
individually specifying arguments in each test definition. As a
prerequisite, also ensures that all test types that use Skia Gold use
the same naming for Gold-related arguments.

This is requisite work for adding a universal Gold kill switch in the
unlikely event of an outage that can't be fixed quickly, as the switch
can just be added to the mixin.

Bug: 1057848
Change-Id: Ib57480f374eab088ac3a389637bfbff1ee41e8b4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2121419
Commit-Queue: Brian Sheedy <bsheedy@chromium.org>
Reviewed-by: Sven Zheng <svenzheng@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Auto-Submit: Brian Sheedy <bsheedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#755521}

Change-Id: I826216ae37c1602081b75fb7f7161a0bfad01951
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2125237
Commit-Queue: Piotr Bialecki <bialpio@chromium.org>
Reviewed-by: Alexander Cooper <alcooper@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Cr-Commit-Position: refs/heads/master@{#755520}

This CL migrates this test out of
third_party/blink/web_tests/css3/flexbox and into the WPT-specific
directory, adding links to the relevant specs and a test assertion
describing its purpose and renames it to
flexbox_width-change-and-relayout-children.html.

Bug: 1063749
Change-Id: I7782b4a7230f6a28872a4eecba544abca89aafcb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2131786
Commit-Queue: David Grogan <dgrogan@chromium.org>
Reviewed-by: David Grogan <dgrogan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#755519}

The bounds is transformed to viewport coordinates before being
pushed to Java side.

Bug: 1064420
Change-Id: Ib473e5ee1723c361edcfee39e742274be9a83c62
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2131039Reviewed-by: Dominic Battré <battre@chromium.org>
Commit-Queue: Tao Bai <michaelbai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#755518}

When we process multiple test types' coverage data, profdata files from
each test target will be used multiple times for different test types.
So these can't be removed after a merge.

Bug: 1064785
Change-Id: I28b92ec5d721192b20781a432ec8d90edbad74b3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2132672
Commit-Queue: Zhaoyang Li <zhaoyangli@chromium.org>
Reviewed-by: Sajjad Mirza <sajjadm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#755517}

https://dawn.googlesource.com/dawn.git/+log/a0afd3158504..373a3ff26ec7

git log a0afd3158504..373a3ff26ec7 --date=short --first-parent --format='%ad %ae %s'
2020-04-01 cwallez@chromium.org Rename GetBindGroupLayout's argument group->groupIndex

Created with:
  gclient setdep -r src/third_party/dawn@373a3ff26ec7

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/dawn-chromium-autoroll
Please CC cwallez@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:dawn-linux-x64-deps-rel;luci.chromium.try:dawn-mac-x64-deps-rel;luci.chromium.try:dawn-win10-x64-deps-rel;luci.chromium.try:dawn-win10-x86-deps-rel
Bug: None
Tbr: cwallez@google.com
Change-Id: I09a6849fe4afc4ba670a13ef91344bce1f37fe9b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2132863Reviewed-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@{#755516}

No change to logic. This swaps out the color of highlight-all-webviews
for a paler shade of yellow, and makes it more transparent. This is
based on feedback from the test team.

Fixed: 1066983
Test: Manual - load http://www.cnn.com/ and compare color filters
Change-Id: I27b22cae1f233ea9f4d410d091520c25d74309d3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2132929
Commit-Queue: Nate Fischer <ntfschr@chromium.org>
Commit-Queue: Bo <boliu@chromium.org>
Auto-Submit: Nate Fischer <ntfschr@chromium.org>
Reviewed-by: Bo <boliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#755515}

Prior to this CL, using the QuickLook feature (hard-press on the
touchpad of a Mac) on a popup like the color picker or date picker
would cause a crash. TextInputClientMac::GetStringAtPoint()
requires a RenderFrame attached to the RenderWidget on the
renderer side to do anything, which only is true for main frame
and iframes.

Prior to [1], this would not do anything either, but after [1]
this became a crash. This CL returns the behavior to a no-op for
popups.

[1] https://chromium-review.googlesource.com/c/chromium/src/+/2006209

Bug: 1065328
Change-Id: I6a1a1cf12898c615ba756d32dd75bb5f87b4cc86
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2132963
Commit-Queue: Mason Freed <masonfreed@chromium.org>
Commit-Queue: danakj <danakj@chromium.org>
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Auto-Submit: Mason Freed <masonfreed@chromium.org>
Reviewed-by: danakj <danakj@chromium.org>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#755514}

Fixes this TODO before M83 branches.

Bug: 1031830
Change-Id: I280cc8378cb1124fdcc12965ff067382d669ef09
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2132827
Auto-Submit: Clark DuVall <cduvall@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#755513}

Intent: https://groups.google.com/a/chromium.org/g/blink-dev/c/WPvxi5nUK2E/m/Xd0ZzPwxAwAJ

Bug: 857041
Change-Id: I3f11c310624d5c2153eefbf9c1e08383d9aad4f8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2074777
Commit-Queue: Florent Castelli <orphis@chromium.org>
Reviewed-by: Henrik Boström <hbos@chromium.org>
Auto-Submit: Florent Castelli <orphis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#755512}

Applies patch from https://gitlab.xiph.org/xiph/opus/-/commit/adcb7bc2

Bug: 1061593
Change-Id: I377991d493cfd1cf5bf509fee2deec6207feee56
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2132634
Auto-Submit: Felicia Lim <flim@chromium.org>
Commit-Queue: James Zern <jzern@google.com>
Reviewed-by: James Zern <jzern@google.com>
Cr-Commit-Position: refs/heads/master@{#755511}

This is in preparation of migrating to Polymer3.

Specifically:
 - Adjust icon color in dark mode, previously same color was used
   in both light and dark mode.
 - Correctly hide "Learn more" link when it should be hidden.
   Previously was not correctly hidden because :empty CSS selector
   was always false.
 - Add missing icon on 3rd row of profile-blocking-error-message.
 - Remove unnecessary white space between #normal-error-message and
   #action-container.

In the process of fixing these bugs and paving the way for Polymer3:
 - Stop using "flattenhtml" to embed icons, instead use same icons
   from shared cr_elements/icons.html along with iron-icon.html
 - Extract most UI and logic in a <signin-error-app> element.
 - Leverage Polymer bindings to determine what to show/hide instead of
   :empty CSS selectors.

Bug: 1012533
Change-Id: Iaed8fdabbeb821f5c4d5b52f76510d477c55fd1d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2130809Reviewed-by: David Roger <droger@chromium.org>
Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Commit-Queue: dpapad <dpapad@chromium.org>
Auto-Submit: dpapad <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#755510}

This CL does three things:
1) Remove the "swipe up to get started UI and gesture" related code.
2) Make the "Get Started" button on the marketing screen always visible
   for screen completion/exit.
3) Remove the accessibility link and replace it with an accessibility
   button to view the accessibility setting page.

Bug: 1065487
Change-Id: I0825847d7c4b9e99ada1159eff7f072c9d699e8b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2127900Reviewed-by: Roman Sorokin [CET] <rsorokin@chromium.org>
Commit-Queue: Matthew Mourgos <mmourgos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#755509}

https://swiftshader.googlesource.com/SwiftShader.git/+log/c66dad9552ef..cb58662302c8

git log c66dad9552ef..cb58662302c8 --date=short --first-parent --format='%ad %ae %s'
2020-04-01 cwallez@cwallez-macbookpro3.roam.corp.google.com MetalSurface: set layer.device to a ref of the system default device.

Created with:
  gclient setdep -r src/third_party/swiftshader@cb58662302c8

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/+/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: I9343f48a4995a098a83160bae0049671cd675d82
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2132857Reviewed-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@{#755508}

This reverts commit 4edeedc6.

Reason for revert:

Fixed the error that broke compilation:
welcome_to_chrome_view_controller.mm should not have been edited.

Original change's description:
> Revert "[ios] Remove dead code in first_run_util"
>
> This reverts commit 721f0aa1.
>
> Reason for revert:
> suspect this is breaking compilation on ios-simulator
>
> Original change's description:
> > [ios] Remove dead code in first_run_util
> >
> > Removed dead codepaths and marked unused histograms obsolete.
> >
> > Change-Id: Ie4f5485ebd9c915dcb36c8ac7d14d2d688b200e7
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2129507
> > Reviewed-by: Kurt Horimoto <kkhorimoto@chromium.org>
> > Reviewed-by: Ilya Sherman <isherman@chromium.org>
> > Commit-Queue: edchin <edchin@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#755163}
>
> TBR=isherman@chromium.org,kkhorimoto@chromium.org,mrefaat@chromium.org,edchin@chromium.org
>
> Change-Id: I1d3d94ce35b28df80626a1838b3c110957b8757d
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2131354
> Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
> Commit-Queue: Rebekah Potter <rbpotter@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#755166}

TBR=isherman@chromium.org

Change-Id: Ibb79afe4242978bf9d7271d2b0609cb0013f9d23
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2131215
Commit-Queue: edchin <edchin@chromium.org>
Reviewed-by: Kurt Horimoto <kkhorimoto@chromium.org>
Reviewed-by: edchin <edchin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#755507}

Bug: 1002674
Change-Id: I01e0daa245231d101425d8ff5a82f7d197f390e4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2098350
Commit-Queue: Nick Yamane <nickdiego@igalia.com>
Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#755506}

App was crashing when trying to navigate from an interstitial page
(forward, backward, back to safety). Remove WebStateObserver in
both the destructor and WebStateDestroyed so that both navigations
and closing the page are covered.

Bug: 1066445
Change-Id: Iace4d26edbaec1ccc26a9b6c410a4de827c5be7b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2130777
Commit-Queue: Livvie Lin <livvielin@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#755505}

Tests assume that NOTIFICATION_EXTENSION_HOST_CREATED fires at most once
(see BrowserActionInteractiveTest::TearDownOnMainThread which compares
the number of "created" vs "destroyed" notifications).  This assumption
has not been met by the product code, which would fire
NOTIFICATION_EXTENSION_HOST_CREATED for every RenderViewReady
notification which happens not only for the very first RenderViewHost,
but also for possible subsequent RenderViewHost swaps (e.g. when
navigating cross-site).

This CL fixes ExtensionHost::RenderViewReady, to ensure that the
NOTIFICATION_EXTENSION_HOST_CREATED fires at most once per ExtensionHost
object.

Note that NOTIFICATION_EXTENSION_HOST_CREATED is only listened to by
test code (browser_action_interactive_test.cc and
management_api_browsertest.cc).  This means that this CL should have no
effect on production code and product behavior.

Fixed: 1066287
Change-Id: I30b26294c9edb18420b7d3d4b8d560c360914a06
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2129230
Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org>
Reviewed-by: Karan Bhatia <karandeepb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#755504}

This is needed for Fullscreen to reset itself when a navigation occurs.

Bug: 790886
Change-Id: I8ac3cb22679e5f2dfc5f966797513d67e8b08da0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2132627Reviewed-by: Kurt Horimoto <kkhorimoto@chromium.org>
Commit-Queue: Chris Lu <thegreenfrog@chromium.org>
Cr-Commit-Position: refs/heads/master@{#755503}

The following legacy policies are read by the manager:
  DelayDeliveryUntilVerdict
  BlockLargeFileTransfer
  AllowPasswordProtectedFiles
  BlockUnsupportedFiletypes
  kURLs* policies

The manager is not called by chrome code yet since the CL is already
quite large and to avoid having this reverted if subsequent code breaks
something.

Bug: 1062348
Change-Id: I4708a9a8a3bab8e559536b426bc4759705f48395
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2124856Reviewed-by: Roger Tawa <rogerta@chromium.org>
Commit-Queue: Dominique Fauteux-Chapleau <domfc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#755502}

These issues were open against a WPT test that was written but the patch
was reverted in blink, implementation is still pending.

BUG=922618

Change-Id: I33ade6c7805a7d3ec55fc3e6b1f1f3747b192657
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2132860Reviewed-by: Robert Ma <robertma@chromium.org>
Commit-Queue: Robert Ma <robertma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#755501}

https://chromium.googlesource.com/openscreen.git/+log/e5b4b11496a0..07dc402b0545

git log e5b4b11496a0..07dc402b0545 --date=short --first-parent --format='%ad %ae %s'
2020-04-01 rwkeane@google.com Add Hashing functions to Util

Created with:
  gclient setdep -r src/third_party/openscreen/src@07dc402b0545

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/openscreen-chromium
Please CC jophba@chromium.org 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: jophba@chromium.org
Change-Id: Icee3acde6623b2fe0eca14b5ed4475f736e985fb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2132856Reviewed-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@{#755500}

Previously NativeKeycodeToDomCode() would treat codes with a NULL name
for the DomCode (i.e. DomCodes used internally by Chrome to represent
keys with no standardized DOM |code| value.) as unknown.

This has been work-around in the DomCode table by assigning non-NULL
names to non-standard DomCodes, leading to confusion over which are
standardized mappings, and which are Chrome-internal.

Allow native keycodes with no standardized DOM |code| name to be mapped
to their Chrome-internal DomCode value, so that non-standard keys may
be switched to NULL names.

Bug: 952051
Change-Id: I1a08928765e76816410c3b005383b43910be5b51
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2020928
Commit-Queue: Navid Zolghadr <nzolghadr@chromium.org>
Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Auto-Submit: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#755499}

This reverts commit f4b86b70.

Reason for revert: This broke the build and the CQ.

https://logs.chromium.org/logs/chromium/buildbucket/cr-buildbucket.appspot.com/8884198304462181456/+/steps/generate_build_files/0/stdout

Original change's description:
> [chromecast] Add process/thread id to the logs.
> 
> Also remove the timestamp since logd adds the timestamp. This
> makes the logs similar to cast.
> 
> Bug: internal b/152558058
> Change-Id: Ifda50ed1115e2192aaa7887440aba7a02341ef09
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2123507
> Reviewed-by: Kenneth MacKay <kmackay@chromium.org>
> Commit-Queue: Mohit Hotwani <hmohit@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#755445}

TBR=halliwell@chromium.org,jlevasseur@google.com,kmackay@chromium.org,kmackay@google.com,hmohit@chromium.org

Change-Id: I537c73a4453f1d31e54c75ab2f8a23757b6be2a9
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: internal b/152558058
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2132831Reviewed-by: Matt Menke <mmenke@chromium.org>
Commit-Queue: Matt Menke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#755498}

Change-Id: Ifbc6768dd3e0bbf8b64e2a1a6bd93322c6916ddc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2132826
Auto-Submit: Clark DuVall <cduvall@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#755497}

Before this CL some os and browser routes had the same name. This was
a bit confusing. If a some c++ code called '/reset', it is not clear if
this url is a chrome or browser subpage. A distinction needed to be made.
This CL renames OS specific route RESET, which is shared with browser
routes to a more distinguishable name OS_RESET. Allowing this bug(990169)
to be unblocked.

Bug: 990169
Change-Id: Ia805b6889bf3b6afe0c22dfc1b11b3ea93fdb2a6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2108873Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Nnamdi Theodore Johnson-kanu <tjohnsonkanu@google.com>
Cr-Commit-Position: refs/heads/master@{#755496}

Bug: 1066832
Change-Id: Ib53fc0452e7d4157cfe8adb64acee2d2e8c81e5c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2132147Reviewed-by: Denis Kuznetsov [CET] <antrim@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Commit-Queue: Roman Sorokin [CET] <rsorokin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#755495}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/85b8bc1b0e14..56891834a29d


Created with:
  gclient setdep -r src-internal@56891834a29d

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: None
Tbr: jbudorick@google.com
Change-Id: I7a422407aa0112092ffff7a61e5fca53ff4d2228
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2132851Reviewed-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@{#755494}

Also keeping it for another 4 months and changing ownership to policy
infrastructure team.

Bug: 1053252
Change-Id: Ic3d59b06d03b6ed11b6e701afcb9db32c172470a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2130252Reviewed-by: Igor <igorcov@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Commit-Queue: Sergey Poromov <poromov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#755493}

Roll src/third_party/shaderc/src/ 1db568ebb..486655782 (1 commit)

https://chromium.googlesource.com/external/github.com/google/shaderc.git/+log/1db568ebb1f0..486655782f8b

$ git log 1db568ebb..486655782 --date=short --no-merges --format='%ad %ae %s'
2020-03-31 rharrison Add knob to control force_zero_initialized_variables (#1028)

Roll src/third_party/spirv-cross/spirv-cross/ 172e39f03..e58e8d5db (40 commits)

https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Cross.git/+log/172e39f0398b..e58e8d5dbe03

$ git log 172e39f03..e58e8d5db --date=short --no-merges --format='%ad %ae %s'
2020-03-31 post MSL: Fix access chain for deep struct hierarchy on array of buffers.
2020-03-30 dsinclair Roll GLSLang, SPIRV-Tools and SPIRV-Headers
2020-03-26 post Add support for forcefully zero-initialized variables.
2020-03-19 post GLSL: Implement GL_EXT_shader_framebuffer_fetch.
2020-03-19 post Run format_all.sh.
2020-03-19 post GLSL/HLSL: Fix nonuniform qualifier for SSBO atomics.
2020-03-19 post GLSL/HLSL: Implement nonuniform qualifier for image atomics.
2020-03-10 post include/spirv_cross: Fix typo.
2020-03-05 post HLSL: Do not emit globallycoherent for SRV ByteAddressBuffer.
2020-03-04 post Add test for disable-storage-image-qualifier-deduction.
2020-03-04 post HLSL: Add option to always treat SSBO as UAV, even with readonly.
2020-03-04 post Add option to disable storage image qualifier deduction.
2020-03-04 post Remove old hack which forces NonWritable/NonReadable.
2020-03-02 post Add -V alias for --vulkan-semantics.
2020-02-24 post MSL: Add C API for force native arrays.
2020-02-24 post MSL: Add native array test for composite array initialization.
2020-02-24 post MSL: Reintroduce workaround for constant arrays being passed by value.
2020-02-24 post MSL: Reinstate workaround for returning arrays.
2020-02-24 post MSL: Add a workaround path to force native arrays for everything.
2020-02-19 dsinclair Roll GLSLang, SPIRV-Tools and SPIRV-Headers
2020-02-14 post Reject SPIR-V modules with garbage ID bound.
2020-02-08 post HLSL: Declare undef variables as static.
2020-02-06 post Remove old memory_scope flag from iOS barriers.
2020-02-03 post Use GNUInstallDirs for include path as well.
2020-02-01 orbea cmake: Don't hardcode the pkg-config file.
2020-02-01 orbea cmake: Use GNUInstallDirs.
2020-02-01 post CMake: Avoid warning when parent project uses VERSION in project().
2020-01-27 post Compile fix on older compilers.
2020-01-27 post GLSL: Support GL_ARB_enchanced_layouts for XFB.
2020-01-25 cdavis MSL: Move inline uniform blocks to the end of the argument buffer.
2019-12-16 cdavis MSL: Support inline uniform blocks in argument buffers.
2020-01-23 post Make SmallVector noexcept.
2020-01-22 42098783+barath121 Typo at line 324
2020-01-16 post Update license headers to 2020.
2020-01-16 post Run format_all.sh.
2020-01-16 post MSL: Add support for force-activating IAB resources.
2020-01-16 post Deal with illegal names in types as well.
2020-01-15 post Reflection: Add array stride/matrix stride reflection.
2020-01-15 post Reflection: Emit reflection information for array size literalness.
2020-01-15 post GLSL: Implement geometry shader passthrough extension.

Created with:
  roll-dep src/third_party/shaderc/src src/third_party/spirv-cross/spirv-cross

Change-Id: I77642e3f04f1fd9ddd52962b324876f352680f4d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2132850
Auto-Submit: Ryan Harrison <rharrison@chromium.org>
Commit-Queue: dsinclair <dsinclair@chromium.org>
Reviewed-by: dsinclair <dsinclair@chromium.org>
Cr-Commit-Position: refs/heads/master@{#755492}