GitLab

For remote desktop environment, when Vulkan is used, VANGLE is only used
for WebGL. It is not responsible for rendering to the native windows (we
will not create GLSurfaceEGL for native windows). We will use Vulkan
swapchain to render on native windows. However some Vulkan drivers
(NVIDIA) cannot be initialized successfully, if the $DISPLAY env
variable is set, but the Xserver(remote desktop Xserver) doesn't have
necessary extensions (NV-CONTROL, NV-GLX). To workaround this issue,
this CL unsets the $DISPLAY env variable before initializing VANGLE and
sets it back after it, if the Xserver doesn't support vulkan swapchain.

Change-Id: I528a6f7d2f618123ea519f0ab4f15e788c4dd607
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2424519Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
Reviewed-by: Jonathan Backer <backer@chromium.org>
Commit-Queue: Peng Huang <penghuang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809872}

Bug: 1125150
Test: browser_tests --gtest_filter=DiagnosticsApp*
Change-Id: I98fc3ffa4818417fc02a92407dbf35eff8c8f601
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2424715
Commit-Queue: Zentaro Kavanagh <zentaro@chromium.org>
Reviewed-by: Bailey Berro <baileyberro@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809871}

Add a FlexLayoutView with the various setters and getters for the
FlexLayout exposed as View properties.

Bug: None
Change-Id: Id4380e9353c7f47774ac35a074559dc31492ab77
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2419135Reviewed-by: Allen Bauer <kylixrd@chromium.org>
Commit-Queue: Thomas Lukaszewicz <tluk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809870}

The recipe-side config for the mojo builders has already been copied to
the new builder group.

Bug: 1131163
Change-Id: Id1d01ccdac7f242e347db02586b04bb6927b9e0b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2427123
Auto-Submit: Garrett Beaty <gbeaty@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@google.com>
Commit-Queue: Dirk Pranke <dpranke@google.com>
Cr-Commit-Position: refs/heads/master@{#809869}

The crash is similar to crrev.com/806062.  In this case, both of
|line_width| and |item.InlineOffset()| are saturated to
LayoutUnit::Max(), then later width computation didn't work well.

This CL fixes the crash by checking the saturation, and also adds
vector index checking to prevent similar issues.

Bug: 1129570
Change-Id: I7b019fb09dda68b24a70cc6f4865dfa22a70ded1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2423759
Auto-Submit: Kent Tamura <tkent@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809868}

This implements sending new SCT audit reports to the Safe Browsing
servers for opted-in users. The SCTAuditingCache now sends reports using
a SimpleURLLoader when new reports are sampled for sending to Safe
Browsing. This reporting is configured by the SCTReportingService via a
new NetworkService::ConfigureSCTAuditing() API. This redesign eliminates
the round-trips between the network service and the browser process
entirely by having the SCTReportingService configure which network
context (and URLLoaderFactory) the SCTAuditingCache should use to send
reports (in this case, we use the system network context).

This also:
- Removes the OnSCTReportReady Mojo API.
- Moves the feature flag for opt-in SCT auditing from services/network/
  into chrome/ now.
- Adds the network traffic annotation for opt-in SCT auditing.
- Extends the existing SCTReportingService browser tests to track
  whether reports sent their results to the reporting server.
- Adds unittests covering reports being sent.
- Adds an optimization where empty reports are stored for reports that
  we do not sample (and thus will never be sent to the server), rather
  than storing the full report object.

Bug: 1082860
Change-Id: I29fd0ee1cb9c2d5c850601e0b54203363d4f8282
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2331755Reviewed-by: Matt Menke <mmenke@chromium.org>
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Reviewed-by: Robert Ogden <robertogden@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Reviewed-by: Nicolas Ouellet-Payeur <nicolaso@chromium.org>
Reviewed-by: Mustafa Emre Acer <meacer@chromium.org>
Commit-Queue: Emily Stark <estark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809867}

ZergoQuerySearchBoxColor should be deprecated and
kSearchBoxBackgroundDefault should not be used outside of the
SearchBoxViewBase constructor.

Bug: 1131223
Change-Id: I1f2497618d3c3bfd0fdb93c6b0f162873a2b2111
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2425623Reviewed-by: Alex Newcomer <newcomer@chromium.org>
Reviewed-by: Yulun Wu <yulunwu@chromium.org>
Commit-Queue: Yulun Wu <yulunwu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809866}

Bug: 1131551
Change-Id: Ia0b99ed3a98680c7add4afe2b4f8e104d5689fda
Tbr: enne@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2425847Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Reviewed-by: enne <enne@chromium.org>
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809865}

This reverts commit 5aca1315.

Reason for revert: TabSearch On Mac was fixed separately not needing this revert.

Original change's description:
> Revert "Remove a few conversion methods on WebWidgetClient."
> 
> This reverts commit 08741021.
> 
> Reason for revert: Breaks TabSearch on Mac. See http://crbug.com/1131162 .
> 
> Original change's description:
> > Remove a few conversion methods on WebWidgetClient.
> > 
> > Use the WidgetBase implementations instead of going via the
> > WebWidgetClient.
> > 
> > BUG=1097816
> > 
> > Change-Id: Ib08b5748806fe3862ac291d354043326d3172282
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2419129
> > Reviewed-by: danakj <danakj@chromium.org>
> > Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#809421}
> 
> TBR=danakj@chromium.org,dtapuska@chromium.org
> 
> Change-Id: I4a5f560c73177acfa6d01464bc37eade2a87af62
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Bug: 1097816, 1131162
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2424494
> Reviewed-by: Robert Liao <robliao@chromium.org>
> Commit-Queue: Robert Liao <robliao@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#809488}

TBR=danakj@chromium.org,robliao@chromium.org,dtapuska@chromium.org

# Not skipping CQ checks because this is a reland.

Bug: 1097816
Bug: 1131162
Change-Id: I6cd02e4003b5f1dfccf3750a601704627e2f2cb1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2425398Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: danakj <danakj@chromium.org>
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Commit-Queue: danakj <danakj@chromium.org>
Commit-Queue: Robert Liao <robliao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809864}

The definition states that the icon to activate is its index, not index +1.

Bug: b/168611883
Change-Id: I83349198e0ca4b555e01e7d0a713d5ce580ef41b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2424138
Auto-Submit: Sandro Maggi <sandromaggi@google.com>
Reviewed-by: Clemens Arbesser <arbesser@google.com>
Commit-Queue: Clemens Arbesser <arbesser@google.com>
Cr-Commit-Position: refs/heads/master@{#809863}

This change adds a new announcement which occurs when chromevox is
enabled and an app list item with a notification badge is focused.

Bug: 1126492
Change-Id: If581feecd46141dfa5027349c6e55575829d6b34
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2423054Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Matthew Mourgos <mmourgos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809862}

The sheet is currently being drawn on a transparent overlay when using
remote Cocoa (e.g. PWA windows), which results in a number of UI issues.
This was exacerbated by
https://chromium-review.googlesource.com/c/chromium/src/+/2324112.

Instead, add a ShowCertificateViewer() Mojo call and move the
implementation to NativeWidgetNSWindowBridge. Along the way, simplify
the implementation. We can now largely rely on Cocoa's built-in lifetime
management for the SFCertificatePanel.

Bug: 916815, 1130490
Change-Id: Ia33102417510d7c0fc6fb09cf55d9fa61efdfdff
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2421633Reviewed-by: ccameron <ccameron@chromium.org>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Commit-Queue: David Benjamin <davidben@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809861}

Bug: 1125150
Test: browser_tests --gtest_filter=DiagnosticsApp*
Change-Id: I9c3b6f06e7fd5c9e1bec009e0845bbbe2668bf67
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2424886
Commit-Queue: Zentaro Kavanagh <zentaro@chromium.org>
Reviewed-by: Bailey Berro <baileyberro@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809860}

Changing fonts to fix the glitch on the welcome screen, as Google Sans
might be not available yet for the first screen.

Bug: 1119990
Change-Id: Ia0e939c651b105357215357db6038ab2d10a5031
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2425383
Commit-Queue: Wenyu Fu <wenyufu@chromium.org>
Reviewed-by: Lijin Shen <lazzzis@google.com>
Reviewed-by: Sky Malice <skym@chromium.org>
Reviewed-by: Theresa  <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809859}

Previously, blanket suppressions were added due to lint not working. Now
that android lint is working well again, we no longer need these blanket
suppressions. They have been removed/fixed/or moved to the specific
files that require them.

Bug: 1044658,1116130
Change-Id: I249afb500c49c13f35880311d04c51391ed8cbfa
Fixed: 1044658
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2424543
Commit-Queue: Peter Wen <wnwen@chromium.org>
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Reviewed-by: Finnur Thorarinsson <finnur@chromium.org>
Auto-Submit: Peter Wen <wnwen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809858}

Extend expiration milestone for InertialSensor.*
histograms.

BUG=1088842

Change-Id: I890a9c2a139d123d4a9fca281067b219f5fb3997
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2424087Reviewed-by: Brian White <bcwhite@chromium.org>
Commit-Queue: Tim Volodine <timvolodine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809857}

Bug: 1125150
Test: browser_tests --gtest_filter=DiagnosticsApp*
Change-Id: I627e1f0156ad7fbefadd58d832e67d121a28dc13
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2424505
Commit-Queue: Zentaro Kavanagh <zentaro@chromium.org>
Reviewed-by: Bailey Berro <baileyberro@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809856}

This change migrates Callbacks in extensions::Blocklist to OnceCallbacks.

Bug: 1007786
Change-Id: If463e8b8fb776bfd1b5fdaae5b415c0216f6419e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2425863
Auto-Submit: Alan Cutter <alancutter@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Commit-Queue: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809855}

Test: added
Bug: 1111445
Change-Id: I0f79be1c09d4ef0eeff276e3c50f491efbe56244
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2380517Reviewed-by: Khushal <khushalsagar@chromium.org>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Commit-Queue: Sammie Quon <sammiequon@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809854}

This does not implement any support for 5G detection, but merely
introduces the new enum value and ensures that consumers of the
ConnectionType enum are aware of its existence.

Bug: 1127134
Change-Id: I7fcc214958ad8a8132ac5b062b8af3559622b7ba
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2425164Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Zhongyi Shi <zhongyi@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Reviewed-by: Min Qin <qinmin@chromium.org>
Reviewed-by: Clark DuVall <cduvall@chromium.org>
Commit-Queue: Ken Rockot <rockot@google.com>
Cr-Commit-Position: refs/heads/master@{#809853}

Bug: 1125150
Test: browser_tests --gtest_filter=DiagnosticsApp*
Change-Id: I39f8d765f841aae135ed543f9fc2238ec8a1837e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2422184
Commit-Queue: Zentaro Kavanagh <zentaro@chromium.org>
Reviewed-by: Bailey Berro <baileyberro@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809852}

With an upcoming change to Feature/Permissions Policy, the header
alone will no longer be sufficient to delegate permissions to use
powerful features in subframes. The iframe allow attribute must
be used in conjunction with it. The header can still be used to
block delegation.

This change updates the screen wake lock WPTs to use the allow
attribute for delegation.

Bug: 1095641
Change-Id: Iecc6d0ce8840013c9dc570e76b1c02510eb89fef
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2424633
Commit-Queue: Ian Clelland <iclelland@chromium.org>
Auto-Submit: Ian Clelland <iclelland@chromium.org>
Reviewed-by: Charlie Hu <chenleihu@google.com>
Cr-Commit-Position: refs/heads/master@{#809851}

Bug: 1127055
Change-Id: I3d44e0aecc593e4cb385c65461731d0f4a461bfd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2425459Reviewed-by: Erik Staab <estaab@chromium.org>
Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809850}

to support Preserve mode correctly.

Bug: 1122988
Change-Id: I2ec59f32a0e8c7b050300b78fe6336c1b12c2c56
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2395403
Commit-Queue: Diana Zagidullina <dizg@google.com>
Reviewed-by: Monica Basta <msalama@chromium.org>
Reviewed-by: David Roger <droger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809849}

Delayed Warnings feature delays certain interstitials until the user
presses a key. It presently ignores ESC key as it can be used to exit
from fullscreen mode.

The user can also use browser shortcuts such as Control+T to open a
new tab. This CL allows modifier keys (Control, Alt etc) so that browser
shortcuts don't show the interstitial.

There are two exceptions made by the CL:
- Shift pressed with other character keys still show the interstitial as
the user may be typing uppercase letters.
- Ctrl+C and Ctrl+V still show the interstitial as they are shortcuts
for copy & paste.

Bug: 1131149
Change-Id: I5d3532b9296beef783e01e18d14e0b7a53309fe2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2425206Reviewed-by: Daniel Rubery <drubery@chromium.org>
Reviewed-by: Emily Stark <estark@chromium.org>
Commit-Queue: Mustafa Emre Acer <meacer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809848}

This cl causes the bindings generator to automatically collect UKM when
these attributes are accessed. This will be used to analyze how much
entropy leaked by this API can be used for cross-site tracking.

Bug: 973801
Change-Id: I29ea7ee1796c8152cab9f004229282b1b728b173
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2421638
Commit-Queue: Chris Fredrickson <cfredric@google.com>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809847}

The Convert*ToDIP() and Convert*ToPixel() functions are problematic in
that they hide what decision is being taken in the underlying code
when moving from floating point to integer, and consumers should be
thinking about what they want for correctness. They also act in
inconsistent ways when converting a Rect vs its components. This
removes the functions that perform float->int conversions in order to
have callers show what they intend to happen and make it clear that
data is being lost in some fashion.

R=sky@chromium.org

Bug: 1130050
Change-Id: I21eb1070750c92f59e89f288f63e385570dc966c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2419621
Commit-Queue: danakj <danakj@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: ccameron <ccameron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809846}

With an upcoming change to Feature/Permissions Policy, the header
alone will no longer be sufficient to delegate permissions to use
powerful features in subframes. The iframe allow attribute must
be used in conjunction with it. The header can still be used to
block delegation.

This change updates the generic sensor WPTs to use the allow
attribute for delegation.

Bug: 1095641
Change-Id: I7ba5512c755816e5072dcb4aade3e13f4904456f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2424654
Commit-Queue: Ian Clelland <iclelland@chromium.org>
Auto-Submit: Ian Clelland <iclelland@chromium.org>
Reviewed-by: Charlie Hu <chenleihu@google.com>
Cr-Commit-Position: refs/heads/master@{#809845}

If one of the Lengths was 'auto' while the other was a percentage or
calc(...), the 'auto' Length would resolve to the corresponding viewport
dimension (i.e like if it was 100%) rather than 0.

Fixed: 1131324
Change-Id: Iec4e406d74b29551f417ab32caf3ef6cc627909b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2426483Reviewed-by: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#809844}

They fail consistently on chromeos-kevin-rel.

Bug: 1131304
Change-Id: Id26ed4a30fb7b27d2326d92ac6f7baa9f61395e9
Tbr: batrapranav@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2426346
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809843}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/80f8eba22fbb..faa49d773432

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 rogerta@google.com,tschumann@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:linux-chromeos-chrome
Bug: None
Tbr: rogerta@google.com,tschumann@google.com
Change-Id: I48a768699c56e0c9c2af0fb9ec2eda54cca04331
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2426291Reviewed-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@{#809842}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/e0d5b2a8..399a0eba

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

The state of WebApks is split across android settings and chrome
site settings. This change adds a dynamic android shortcut into
WebApks to make site settings more accessible.

The ManageDataLauncherActivity adds functionality for adding the
shortcut, checking whether the version of Chrome supports site settings,
and launching site settings through the chrome
ManageTrustedWebActivityLauncherActivity.
ManageTrustedWebActivityLauncherActivity was modified to include support
for WebApk verification.

Bug: 1119727
Change-Id: I90720ac83c4edf90056cc7b2692be1079b8643a4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2387764Reviewed-by: Peter Kotwicz <pkotwicz@chromium.org>
Reviewed-by: Peter Conn <peconn@chromium.org>
Commit-Queue: Pavol Drotár <pavoldrotar@google.com>
Auto-Submit: Pavol Drotár <pavoldrotar@google.com>
Cr-Commit-Position: refs/heads/master@{#809840}

* Allow focus on snoozable bubble.
* Adjust focused button text and background color according to
  UX spec: go/desktop-iph-snooze-ux-spec

The spec also stipulates a new set of font sizes and text alignment.
I will submit a separate CL to address them.

Bug: 1121399
Change-Id: Ifeb9caf51ba328697b930b4eba19106e83664f48
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2423307Reviewed-by: Collin Baker <collinbaker@chromium.org>
Commit-Queue: Keren Zhu <kerenzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809839}

This patch applies hanging trailing spaces logic to inline
boxes.

When `white-space: pre-wrap`, trailing spaces can hang. They
should not affect scroll (layout) overflow though.

This was fixed for LayoutNG in crbug.com/966773. When the fix
was ported to FragmentItem, it was applied only to text runs.
It should be applied to inline boxes too, because inline
boxes that contain hanging trailing spaces can also hang.

Bug: 1130310
Change-Id: Ie03e178eb26b2c7270f536974cd617feb38c9169
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2425553Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809838}

Don't advance past the inner-most resource container and don't consider
a resource container itself to be a <clipPath> descendant.

Bug: 109224, 1131088
Change-Id: I87e766f6247e868b31eefba90ca35bf8b1a7bdac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2425055Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#809837}

This CL replaces the enable_soda GN flag with the kUseSodaForLiveCaption
feature flag.

Bug: 1128723
Change-Id: I8f46c85808d5744cfedca9b0141b5a8bcf1414ce
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2419138Reviewed-by: Colin Blundell <blundell@chromium.org>
Reviewed-by: Alex Gough <ajgo@chromium.org>
Reviewed-by: Joshua Pawlicki <waffles@chromium.org>
Commit-Queue: Evan Liu <evliu@google.com>
Cr-Commit-Position: refs/heads/master@{#809836}

If set call AccessibilityNodeInfo.setLiveRegion on an ARIA Live
Region, TalkBack will announce changes to that portion of the screen.
Unfortunately it always speaks the entire contents, which is often
not the correct behavior.

Instead, just use Chrome's own live region handling, which tells
TalkBack what text to speak, and correctly only announces new text
added to a live region.

Long-term, more changes are needed to complete Chrome's live region
handling, but this is an improvement for some important real-world
live regions.

would speak the entire region rather than only what was added

Bug: 1042893, 1128193
AX-Relnotes: fixes issue where ARIA live regions on Android
Change-Id: Icd8a0ec8247681862313f1620bbd5aa6567e4e6e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2425747Reviewed-by: Mark Schillaci <mschillaci@google.com>
Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809835}

With an upcoming change to Feature/Permissions Policy, the header
alone will no longer be sufficient to delegate permissions to use
powerful features in subframes. The iframe allow attribute must
be used in conjunction with it. The header can still be used to
block delegation.

This change updates the WebSerial WPTs to use the allow attribute
for delegation.

Bug: 1095641
Change-Id: I810cd5df06b89b0b5b2f2c160e0f9eac19dd67f3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2424655
Commit-Queue: Ian Clelland <iclelland@chromium.org>
Auto-Submit: Ian Clelland <iclelland@chromium.org>
Reviewed-by: Charlie Hu <chenleihu@google.com>
Cr-Commit-Position: refs/heads/master@{#809834}

Change-Id: I87a6a19fba49d8d8719d189ea4be026eb36261bd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2425128Reviewed-by: Brandon Jones <bajones@chromium.org>
Commit-Queue: Piotr Bialecki <bialpio@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809833}