GitLab

Remove conformance/textures/misc/compressed-tex-image.html expectation

Skip unsupported extensions expectations on SwiftShader
Also skip unsupported extensions expectations on other platforms,
to speed up test execution.

This takes a different approach to handling conflicting expectations.
SwiftShader expectations are duplicated for linux, mac, win.
Other expectations are simplified to their original version.

TBR=bsheedy

Bug: 1099955
Change-Id: Ibfcc44b454a7cea94f3e629928d7f79f66d71c39
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2353581
Commit-Queue: Yuly Novikov <ynovikov@chromium.org>
Reviewed-by: Yuly Novikov <ynovikov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#797796}

When no frame is produced due to no damage on impl thread, and the main
thread still has not responded to an earlier 'begin main frame', treat
that as a 'dropped frame', rather than a 'no damage frame'.

BUG=1102071

Change-Id: Icf06fb7e9e98531f87bcb3e0bf477af8eae52132
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2353831
Auto-Submit: Sadrul Chowdhury <sadrul@chromium.org>
Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org>
Reviewed-by: Sunny Sachanandani <sunnyps@chromium.org>
Cr-Commit-Position: refs/heads/master@{#797795}

android debug static bot for lorenz-graph-dbg

Bug: 1098864
Change-Id: Iae186de07a787c77b34d489dca8ab20a73db8145
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2353390
Auto-Submit: Jeff Yoon <jeffyoon@chromium.org>
Reviewed-by: Garrett Beaty <gbeaty@chromium.org>
Commit-Queue: Garrett Beaty <gbeaty@chromium.org>
Cr-Commit-Position: refs/heads/master@{#797794}

Tiles with different scale can't use LCD text because their pixels
are not aligned with physical pixels. Once the flag is set on a tiling,
it should keep unchanged and set the flag for all tiles of the tiling,
to avoid mosaic effect caused by different LCD text settings of
different tiles, and we accept the temporary imperfection of LCD-text.

Also when a layer's LCD-text status changes, only invalidate the highres
tiling in the same way as we invalidate the highres tiling when raster
translation changes.

This is a preparation CL for crbug.com/1111195.

Bug: 1111195
Change-Id: I64ef167ac322ee94c96a82575e3f2448060fcda6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2344809
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: vmpstr <vmpstr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#797793}

This adds NavigationHandle::SetReferer() and calls it from
WebLayer's Navigation::SetRequestHeader().

BUG=1114870
TEST=covered by test

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

Currently there is only one ctor for SwapPromiseMonitor, which takes
both SwapPromiseManager* and LayerTreeHostImpl*, however these two
parameters should never used together. This CL changes the ctor to
two separate ctors so we can distinguish each use case more clearly.

Test: Should be covered by the current tests.
Bug: 1104665
Change-Id: If9bad83cb151a51484ad9b87ab8a6d8ad3b04e47
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2350879Reviewed-by: Khushal <khushalsagar@chromium.org>
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Commit-Queue: Shimi Zhang <ctzsm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#797791}

https://chromium.googlesource.com/external/github.com/AOMediaCodec/libavif.git/+log/4cfee6282b97..fdc636b4ce09

$ git log 4cfee6282..fdc636b4c --date=short --no-merges --format='%ad %ae %s'
2020-08-12 wtc Use fullSize for alpha in avifImageAllocatePlanes
2020-08-12 wtc Check for grid images consistently
2020-08-12 wtc Clean up avifDecoderReset()
2020-08-12 wtc Fix avifDecoderDataFillImageGrid for alpha images
2020-08-12 wtc Change conditional expressions to prevalent style (#273)
2020-08-12 wtc Validate grid image size and tile size (#272)
2020-08-12 wtc Ignore clang -Wc11-extensions warnings on dav1d.h (#271)
2020-08-12 52529860+novomesk Disable Clang warning (drop const qualifier) (#270)
2020-08-12 wtc avifParseImageGridBox should consume all item data (#269)
2020-08-12 wtc Declare local variable 'alphaTile' in if statement (#268)
2020-08-11 wtc Use local var 'data' throughout avifDecoderReset (#266)
2020-08-11 wtc Disallow zero grid output_width or output_height (#265)

Created with:
  roll-dep src/third_party/libavif/src
R=dalecurtis@chromium.org

Change-Id: I78507ef6bc038cdb7a96dad09cd5ae65e3a89c8e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354613Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Commit-Queue: Wan-Teh Chang <wtc@google.com>
Cr-Commit-Position: refs/heads/master@{#797790}

This changes adds metrics to record the printer status reasons returned
by printer status queries. This metric coincides with the addition of
printer availability icons to the Print Preview destination dropdown
(go/printer-status-design-doc).

Bug: 1059607
Change-Id: Ica85163a3dcc0ecdbe34370f14f998512aaa3a4e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2347313Reviewed-by: Zentaro Kavanagh <zentaro@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Reviewed-by: Bailey Berro <baileyberro@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Commit-Queue: Gavin Williams <gavinwill@chromium.org>
Cr-Commit-Position: refs/heads/master@{#797789}

- Search tag now includes both "Android settings" and
  "Android preferences" to link to the android settings
  subpage.
- Set "Android preferences" as the primary search tag as it
  matches the text of the link to android preferences app.

Bug: 1115330
Change-Id: Id0dd5b40c2fab9e4a9a41f1d67357475a0a78817
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2353675Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Commit-Queue: Jimmy Gong <jimmyxgong@chromium.org>
Cr-Commit-Position: refs/heads/master@{#797788}

This reverts commit 01efb7a7.

Reason for revert: Causing bot failures:
https://ci.chromium.org/p/chromium/builders/ci/Win7%20%2832%29%20Tests

Original change's description:
> Implement initializer list support for containers
> 
> Implement initializer list support for creating arrays and dictionaries
> in TracedValue::Build. Thus speed up adding debugging tracing of
> multiple parameters, including container types.
> 
> Follow-up of: crrev.com/c/2263160
> 
> Bug: 1043616
> Change-Id: I2d3205d550e6ce6328ea253e6b94f9cc2cbe3098
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2346286
> Reviewed-by: Eric Seckler <eseckler@chromium.org>
> Reviewed-by: Alexander Timin <altimin@chromium.org>
> Commit-Queue: Karel Král <karelkral@google.com>
> Cr-Commit-Position: refs/heads/master@{#797706}

TBR=altimin@chromium.org,eseckler@chromium.org,karelkral@google.com

Change-Id: I7334c762ede0d06226398ee9ff7b38bf5a30e44e
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 1043616
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354830Reviewed-by: Takumi Fujimoto <takumif@chromium.org>
Commit-Queue: Takumi Fujimoto <takumif@chromium.org>
Cr-Commit-Position: refs/heads/master@{#797787}

With the flag on, articles context menus weren't working. Moving the
flag check to the MostVisited flow instead of overall the long-press
gesture recognizer fixes it.

Bug: 1115970
Change-Id: Ic9945928c949cbef9ed874d5a381b071b18a54d3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354272
Auto-Submit: Sebastien Lalancette <seblalancette@chromium.org>
Commit-Queue: Sergio Collazos <sczs@chromium.org>
Reviewed-by: Sergio Collazos <sczs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#797786}

Add the appropriate help link to chrome://devices

Also fixing a typo in the link itself - should be support.google.com,
not www.google.com.

Note: String itself is not modified by this change, but is detected
as a change due to adding the URL argument.

Bug: 1114186
Change-Id: Ibb8583d419639da3b1ba13058060cf91298deeb9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2353406Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Rebekah Potter <rbpotter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#797785}

Change-Id: I7b2aa098037f0bfd89b46b360493c6ec3fc24834
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354515
Auto-Submit: Justin Cohen <justincohen@chromium.org>
Commit-Queue: Sergio Collazos <sczs@chromium.org>
Reviewed-by: Sergio Collazos <sczs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#797784}

This takes the values returned as base::Value from the sandbox
policy and allows them to be expanded in the summary display of
chrome://sandbox.

Expansion is deferred as the page can become slow in debug builds if
it is performed every time, and expanded values are not always
required for debugging.

Bug: 1115305
Change-Id: I96d71b21ccc28e678fdb3fb9714f30cf88b730ef
Tests: manual testing on Win7 x86 and Win10 10.0.18362
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2350331Reviewed-by: Will Harris <wfh@chromium.org>
Reviewed-by: Michael Giuffrida <michaelpg@chromium.org>
Commit-Queue: Alex Gough <ajgo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#797783}

Change the loading spinner to show when waiting time is longer than
500ms, and ensure the loading spinner is displayed for at least 500ms.

For simplicity, we also change the name of CCT fragment and use original
flow when the welcome page is going to be skipped.

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

It will create an easy workaround for developers when testing policy
on platforms that have need complicated policy management tools.

Bug: 1113792
Change-Id: Ie0431022a3aba1d5356afb32a9987a91d6ba7929
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2353397
Commit-Queue: Owen Min <zmin@chromium.org>
Reviewed-by: Yann Dago <ydago@chromium.org>
Cr-Commit-Position: refs/heads/master@{#797781}

Change logic:
* The untrusted PaymentRequest interface breaks apart from CPRImpl to
become MojoPaymentRequestGateKeeper. The new class would be responsible
for handling the untrusted mojo calls from the renderer. Doing that,
it can ensure that CPRImpl receives no invalid calls from the renderer.
* Establish the requirements for the users of CPRImpl that the CPRImpl
instances should be set null after BPRImpl#close, CPRImpl#teardown and
PRClient#close. For example, CPRImpl#OnClosedListener is provided for
the callers to nullify the instances.

Note that:
* Although MPRGateKeeper and CPRImpl both have plumbings to pass PR
calls, they are necessary, because going forwards, PRImpl will be
diminished, and eventually the plumbings would only exist between
MPRGateKeeper and CPRImpl.

Code change highlights:
* In CPRImpl#initAndValidate(), null-check the request's raw data
before passing them into BPR, so that BPR doesn't need to add @Nullable
for them.
* In MPRGateKeeper#init, discards CPRImpl (and its PRClient, BPR) when
the raw data are invalid.
* MPRGateKeeper plumbs the PR calls to CPRImpl, so that the calls are
only passed to the CPRImpl when the PaymentRequest data are valid.

Acronym:
CPRImpl = ComponentPaymentRequestImpl
BPR = BrowserPaymentRequest
PRClient = PaymentRequestClient
MPRGateKeeper = MojoPaymentRequestGateKeeper

Bug: 1102522

Change-Id: Iab160b2c3e74608b9b19ba17e454dedf32411193
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2346730
Commit-Queue: Liquan (Max) Gu <maxlg@chromium.org>
Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
Reviewed-by: Danyao Wang <danyao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#797780}

This CL fixes VaapiWrapper::FillProfileInfo_Locked() so that it doesn't
return false when the profile is VAProfileVP9Profile2 and the driver
does not advertise support for VA_RT_FORMAT_YUV420 (and instead only
advertises support for VA_RT_FORMAT_YUV420_10 and
VA_RT_FORMAT_YUV420_12).

More context:

The uprev to iHD 20.2.0 caused TGL to advertise only
VA_RT_FORMAT_YUV420_10 and VA_RT_FORMAT_YUV420_12 for
VAProfileVP9Profile2, probably because of [1]. This seems reasonable
since VP9.2 is intended for high bit depth. Running vainfo -a shows the
following for VP9.2:

VAProfileVP9Profile2/VAEntrypointVLD
    VAConfigAttribRTFormat                 : VA_RT_FORMAT_YUV420_10
                                             VA_RT_FORMAT_YUV420_12
                                             VA_RT_FORMAT_YUV420_10BPP
    VAConfigAttribDecSliceMode             : VA_DEC_SLICE_MODE_NORMAL
                                             VA_DEC_SLICE_MODE_BASE
    VAConfigAttribDecProcessing            : VA_DEC_PROCESSING
    VAConfigAttribMaxPictureWidth          : 16384
    VAConfigAttribMaxPictureHeight         : 16384
    VAConfigAttribProcessingRate           : VA_PROCESSING_RATE_DECODE

The problem is that VaapiWrapper::FillProfileInfo_Locked() returns true
only if one of {VA_RT_FORMAT_YUV420, VA_RT_FORMAT_YUV422,
VA_RT_FORMAT_YUV444} is advertised. Therefore, for iHD 20.2.0, we would
determine that VAProfileVP9Profile2 is unsupported and subsequently fall
back to software.

This CL ensures that we check for the presence of
VA_RT_FORMAT_YUV420_10 (which is the non-deprecated version of
VA_RT_FORMAT_YUV420_10BPP [2]).

[1] https://github.com/intel/media-driver/commit/ca71e10f29ea3b232b883803b31724a8ee0d3e46
[2] https://github.com/intel/libva/blob/2.8.0/va/va.h#L821

Bug: b:161520834
Test: crosvideo.appspot.com w/ VP9.2; checked chrome://media-internals
Change-Id: Id00a0150272cc11640bd21183ee739b005f9d2cf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2303682Reviewed-by: Miguel Casas <mcasas@chromium.org>
Commit-Queue: Andres Calderon Jaramillo <andrescj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#797779}

Wayland Ozone backend uses a platform drag-and-drop session to be able
to support the capabilities required by Chrome's tab dragging.
Particularly, keeping track of the focused window and the current mouse
cursor position while the tab/window is dragged around. Further context
can be found at the design doc [1].

So far, it has been relying only on {Run,End}MoveLoop API to trigger
such DND session. It works, but, as it is called after the (dragged)
windows creation and mapping, it is not possible to take the necessary
actions upon window creation or mapping (e.g: issue some dnd/extension
protocol request to the Wayland compositor), which makes it insufficient
to achieve glitches-free tab/window detaching implementation. Which has
been verified while addressing [2][3], and can be seen at video [4].

To fix it, this patch does:

- Add WaylandExtension platform window extension, with a single method
for now, that makes it possible for the upper layer components to start
the window dragging session explicitly;
- Plumbs up Chrome's Browser{Frame,DWTHLinux} such that it starts a
Wayland drag-and-drop session when the tab drag starts.

[1] https://docs.google.com/document/d/1s6OwTi_WC-pS21WLGQYI39yw2m42ZlVolUXBclljXB4/edit?usp=sharing
[2] https://bugs.chromium.org/p/chromium/issues/detail?id=1099418
[3] https://chromium-review.googlesource.com/c/chromium/src/+/2307653
[4] https://www.youtube.com/watch?v=3sWVyA1OagA

R=sky@chromium.org

Bug: 896640
Test: Covered by ozone_unittests
Change-Id: I5e902caa7b495ae585330bc3e3b431bacb139d1e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2346545
Commit-Queue: Nick Yamane <nickdiego@igalia.com>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Maksim Sisov (GMT+3) <msisov@igalia.com>
Cr-Commit-Position: refs/heads/master@{#797778}

Bug: 1113466
Change-Id: Idc85b749409055f0e9d5bbbc1d0fcb55a12d2df2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2343494
Auto-Submit: Mark Mentovai <mark@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Commit-Queue: Mark Mentovai <mark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#797777}

Also adds a test for documenting what happens when the limit is
reached.

Bug: 1115736
Change-Id: Ie488adb6b874ae47503670514bd7456bef8bfd6f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354536Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Commit-Queue: Robert Ogden <robertogden@chromium.org>
Cr-Commit-Position: refs/heads/master@{#797776}

To ensure the MediaSourceRegistryImpl singleton is available and known
to MediaSourceAttachments before they could possibly be created, moves
the singleton construction to be done during modules initialization
instead of lazily on-demand later. This ensures that the main thread
will own the singleton, since later changes enable first real usage of
the registry to be done from either the main thread or from a dedicated
worker thread.

BUG=878133

Change-Id: Ibc4e0b77ef840d76d6048a46614affae3227c07d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2353534Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Matthew Wolenetz <wolenetz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#797775}

The active profile was not being cleared on the |NearbyProcessManager|
singleton in the unit-test tear down which was causing unit-test
failures.

Change-Id: Iefe1b037beeb23924550c9ae6ccaf1ba0f111b5f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354616
Commit-Queue: James Vecore <vecore@google.com>
Commit-Queue: Ryan Hansberry <hansberry@chromium.org>
Auto-Submit: James Vecore <vecore@google.com>
Reviewed-by: Ryan Hansberry <hansberry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#797774}

disconnects.

Add disconnect handlers to the speech service. If the UI in the browser
disonnects from the service in the renderer, have the speech service stop
transcribing captions. If the service in the renderer disconnects from
the utility process which connects to SODA or the cloud, send a message
to the UI that there was an error and have the UI display the error
message.

Bug: 1055150
Change-Id: I3940cae2cd12503353e105fd612b064908d9951c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2353024Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Alex Gough <ajgo@chromium.org>
Reviewed-by: Evan Liu <evliu@google.com>
Commit-Queue: Abigail Klein <abigailbklein@google.com>
Cr-Commit-Position: refs/heads/master@{#797773}

Implementing AsValueInto method in NavigationRequest allows it to be
used as input into tracing events macros. This CL adds this support and
uses it to log the NavigationRequest in its constructor.

Bug: 1043616
Change-Id: Iac28d6d52944064e448d99fe2734057ad0cf6ac4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2353546
Commit-Queue: Nasko Oskov <nasko@chromium.org>
Reviewed-by: Alexander Timin <altimin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#797772}

This makes it easier to track down and/or change types.

Also renames CallbackList -> RepeatingCallbackList.

Bug: 1113007
Change-Id: I42357489f2c3e7a19b0f4909fe20ca7dc9ff4339
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354225Reviewed-by: Sergio Collazos <sczs@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Maksim Moskvitin <mmoskvitin@google.com>
Reviewed-by: Justin Donnelly <jdonnelly@chromium.org>
Commit-Queue: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#797771}

SerialTest.NavigateWithChooserCrossOrigin fails on Linux Ozone Tester
(X11), https://ci.chromium.org/p/chromium/builders/ci/
Linux%20Ozone%20Tester%20%28X11%29/15780,
disable it for now until it is fixed.

TBR= reillyg@chromium.org

Bug: 1116072
Change-Id: I01e63d9a87ed9e2995db21e158a9d964cf7cd5e4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354712Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Lan Wei <lanwei@chromium.org>
Commit-Queue: Reilly Grant <reillyg@chromium.org>
Commit-Queue: Lan Wei <lanwei@chromium.org>
Auto-Submit: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#797770}

We need to pass switch --use-cras to the audio service so that chrome
will be able to use CRAS on linux.

Bug: 151905045
Change-Id: I7c8acf0f3c976ba40bf492a85a53c56a3254fcfe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2332057Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Reviewed-by: Bo <boliu@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Commit-Queue: Yu-Hsuan Hsu <yuhsuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#797769}

Previously Vulkan extensions VK_KHR_external_memory_fd and
VK_KHR_external_semaphore_fd were not enabled for swiftshader because
they were not supported. They are supported now, so they can be enabled.

Bug: 963988
Change-Id: I4d72fe965038615f19311e1e5bca5600b54035ab
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2353930
Auto-Submit: Sergey Ulanov <sergeyu@chromium.org>
Reviewed-by: Peng Huang <penghuang@chromium.org>
Commit-Queue: Sergey Ulanov <sergeyu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#797768}

When user enters into an overscroll (without fling) and lifts off the
fingers while the scroller is stretched, we can occasionally observe
forward jerks before a bounce back animation plays. This happens due to
stray finger movements. When the finger lifts off, there can be small
velocities that trigger a forward animation (i.e the quick forward
jerk). This CL fixes the issue by preventing the scroller from playing
the bounce forward animation when velocities are really small.

Bug: 1116057
Change-Id: I1f3c53b510172b6d5509e09354db3d97a9814492
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2348009Reviewed-by: Philip Rogers <pdr@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Commit-Queue: Rahul Arakeri <arakeri@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#797767}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/2bc574fa..42ae8f6e

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

https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/f20a184a017f..a22614c51d49

2020-08-13 jacktfranklin@chromium.org Regenerate all bridge files
2020-08-13 alexrudenko@chromium.org Show list of grid elements in Layout pane

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:1109177
Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com
Change-Id: I9dd21c2181ce7c9ac1ea2f0bbc16728961ad1eb9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354474Reviewed-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@{#797765}

Change-Id: I5eedd07b2e3d4b81b3fb573eb70bb543cf6965b4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354591
Auto-Submit: Chris Hamilton <chrisha@chromium.org>
Commit-Queue: Chris Hamilton <chrisha@chromium.org>
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Dirk Pranke <dpranke@google.com>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@google.com>
Cr-Commit-Position: refs/heads/master@{#797764}

Sometimes [ToolbarMediator updateShareMenuForWebState:]
is passed a null WebState, so do nothing if that is the case.

Bug: 
Change-Id: Id083687df59199489a80ca21a9182113e2ad62ae
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354710
Auto-Submit: Chris Lu <thegreenfrog@chromium.org>
Reviewed-by: Sergio Collazos <sczs@chromium.org>
Commit-Queue: Chris Lu <thegreenfrog@chromium.org>
Cr-Commit-Position: refs/heads/master@{#797763}

- We were using the wrong proto message for the response.
  I've made a new discover_actions_service.proto file to
  more closely match the server definitions.
- The response does not have a varint prefix

Added a test, UploadedActionsAreNotSentAgain. It wouldn't
have caught the problem, but looks like a case we weren't quite
testing yet.

Bug: b/163866547
Change-Id: Iab8c11ce3ceb3ab61d2b56cc694af9f127e45b38
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2354245
Commit-Queue: Dan H <harringtond@chromium.org>
Reviewed-by: Ian Wells <iwells@chromium.org>
Cr-Commit-Position: refs/heads/master@{#797762}

- omnibox-autocomplete-titles (m85 -> 95)
- omnibox-drive-suggestions (m85 -> 95)
- omnibox-local-entity-suggestions (m85 -> 88)

Change-Id: I216a56be058155eea666261303f823ed4e7f0247
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2353537Reviewed-by: Tommy Li <tommycli@chromium.org>
Commit-Queue: manuk hovanesian <manukh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#797761}

In order to work around the inability to inspect the contents of
include_dirs when creating an action within the nocompile_test template,
this change adds a dedicated include_dirs parameter to the template.
This allows callers to provide extra include dirs explicitly, which will
e.g. be required once classes in base include Abseil headers, and thus
affecting base's nocompile tests as well.

Bug: None
Change-Id: I2354dd428e5ada8c5a41bb9b2c3e7007a3df9282
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2351772Reviewed-by: Brett Wilson <brettw@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org>
Cr-Commit-Position: refs/heads/master@{#797760}

This removes some unnecessary complexity.

BUG=none
TEST=test only change

Change-Id: Ide08a5af6915c93a9cdf5b06132a3fc47e3138b4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2349788
Commit-Queue: Scott Violet <sky@chromium.org>
Reviewed-by: Peter Kotwicz <pkotwicz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#797759}

Implement a concrete location::nearby::api::BluetoothSocket, created via
a bluetooth::mojom::Socket and Mojo DataPipes supplied by the newly
implemented BluetoothClassicMedium::ConnectToService().

Nearby Connections uses this BluetoothSocket to communicate with a
remote device. At a high-level, it first exchanges frames to encrypt
the connection, then delegates to its caller (e.g., Nearby Share)
to authenticate the connection, and finally expects its caller to
send and receive application-level messages. The following precautions
are taken to handle untrusted bytes received from remote devices:
  * Nearby Connections (including the code being added in this CL) is
    hosted in a Nearby utility process.
  * Whenever Nearby Connections provides bytes received from a remote
    device to its caller, even after it has been authenticated, the
    caller must not trust those bytes, and is responsible for first
    passing those bytes through the trusted NearbyDecoder interface
    (see go/nearby-chrome-mojo). NearbyDecoder is hosted in the same
    Nearby utility process.

api::BluetoothSocket is a synchronous interface, so this
implementation consumes the synchronous signatures of
bluetooth::mojom::Socket methods.

api::BluetoothSocket's subclasses are also synchronous interfaces,
but the Mojo DataPipes they consume only provide asynchronous
interfaces. This is reconciled by blocking on the caller thread when
waiting (via a mojo::SimpleWatcher) for the DataPipes to become
readable or writable (this is expected by the callers of
api::BluetoothSocket's subclasses). Mojo DataPipe operations are
handled on a separate task runner so that blocking on the calling
thread will not deadlock.

Please see design doc go/nearby-chrome-bt for more details.

Bug: b:154849033, b:158848873
Change-Id: I2e945277aa1f75b4ca378d0b961f7682ff25d812
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2322166
Commit-Queue: Ryan Hansberry <hansberry@chromium.org>
Reviewed-by: Alex Chau <alexchau@chromium.org>
Reviewed-by: James Vecore <vecore@google.com>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#797758}

This class tracks whether notification access has been granted by the
user on their phone. Because notification access is a sensitive
permission, this requires the user completing a special setup flow and
is not included with the rest of Phone Hub opt-in.

Note that currently, this class defaults to "false" (i.e., has not yet
granted access). A future CL will set this value based on whether the
phone has sent a message indicating that access has been granted.

Bug: 1106937
Change-Id: Ice4968ef684b96f090ee566013aa39dc8224e4f4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2353709
Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: Dominic Battré <battre@chromium.org>
Reviewed-by: Josh Nohle <nohle@chromium.org>
Cr-Commit-Position: refs/heads/master@{#797757}