GitLab

Adds throttling that pauses loading when too much unread data
accumulates, then resumes loading when the backlog clears.

For consistency, switches all EXPECT_CALL() expectations without
argument matchers in url_loader_unittest.cc to the argument-less form.

Fixed: 1099022
Change-Id: Iac02f17bbcac166e92e19611e5ad35786a3c3a2f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2427844
Commit-Queue: K. Moon <kmoon@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#810369}

Release_Notes: http://go/help_app-x20/relnotes/Main/help_app_nightly_202009240800_RC00.html

https://chrome-infra-packages.appspot.com/p/chromeos_internal/apps/help_app/app/+/pmx13oYqsBxVgUj6p9fCwrTtgN1M6INq4nvwNMlYmL4C

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://skia-autoroll.corp.goog/r/help-app-chromium-autoroll
Please CC help-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
Bug: b/153596786
Tbr: help-app@grotations.appspotmail.com
Change-Id: Id05f048c0b4f0491ebfc252f6f509dfad0ec64db
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2429167Reviewed-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@{#810368}

Previously, the size and offset of the grid in the unit test
FixedSizePositioning (added in the following change
https://chromium-review.googlesource.com/c/chromium/src/+/2369673)
differed from the rendered result; the grid's size was 100x400 rather
than 200x200, and the items' offsets in x were 0. This change fixes the
expectation to match the rendered result by deleting the parameters
shrink_to_fit and is_new_formatting_context from the function
ConstructBlockLayoutTestConstraintSpace(). A div was also added to wrap
the grid.

Moreover, the intrinsic_block_size and border_box_size are defined. The
case where the height is auto is a TODO for now because it depends on
final computed row/column sizing, which is still in progress.

Bug: 1045599
Change-Id: I4dbbb093e12aa4aa7cd1a26168212e63e870ebde
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2422277
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Ana Sollano Kim <ansollan@microsoft.com>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Ethan Jimenez <ethavar@microsoft.com>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Kurt Catti-Schmidt <kschmi@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#810367}

When allocating zero-weight views, FlexLayout expects them to be
allocated up to their preferred size in the first pass or dropped out.
However, if the preferred size is zero, they may not yet be visible in
the second (allocate-excess-space) pass.

We had a consistency DCHECK that was failing if the view wasn't visible
the second pass; this is now updated to visible OR zero-preferred-size.

Change-Id: I41368f09bf2fa3056f7676e26ad1b0ba2c895925
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2429647
Commit-Queue: Dana Fried <dfried@chromium.org>
Commit-Queue: Charlene Yan <cyan@chromium.org>
Auto-Submit: Dana Fried <dfried@chromium.org>
Reviewed-by: Charlene Yan <cyan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#810366}

We're getting some crashes that look like either use-after-free or
heap corruption in MediaWebContentsObserver.  This CL adds a quick
check for it, that will abort if it finds either, and tell us which
one it found.  Hopefully, it will help us to narrow down if (a)
use-after-free/corruption is actually what's going on, and (b) if
it's happening as part of the call into MWCO or earlier.

Change-Id: I91edc46af55b9dcbd223b01c3bb80c22b1386903
Bug: 1111291
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2429246Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Commit-Queue: Frank Liberato <liberato@chromium.org>
Cr-Commit-Position: refs/heads/master@{#810365}

As part of moving CT verification to occur within the state machine
of cert verification, move the CTVerifyResult fields into the
CertVerifyResult as appropriate.

As a nice side benefit, this allows CT verification details to be
handled in browser tests using ContentMockCertVerifier.

Bug: 848277, 1016635
Change-Id: I365358ca12ecd9205d8103ed0e3396cdb48144b3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2423060Reviewed-by: Robbie McElrath <rmcelrath@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Reviewed-by: Emily Stark <estark@chromium.org>
Reviewed-by: Ryan Sleevi <rsleevi@chromium.org>
Commit-Queue: Emily Stark <estark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#810364}

https://webrtc.googlesource.com/src.git/+log/afef7a74a796..9e81182f8ea5

2020-09-24 alessiob@webrtc.org RNN VAD build file refactoring: split into separate (private) targets
2020-09-24 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 532b3f34..b70f108b (810021:810146)
2020-09-24 phensman@webrtc.org Remove instance of IP logging in NetworkMonitorAutoDetect

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

Change all files that depends on the existence of the deprecated
global sources assignment filter to explicitly configure it by
importing the deprecated_default_sources_assignment_filter.gni
and calling set_sources_assignment_filter().

This is a preliminary step before removing the global assignment
in //build/config/BUILDCONFIG.gn and incremental migration of
those files from the deprecated feature.

To verify, used a patched version of gn:
https://gn-review.googlesource.com/c/gn/+/6401
And then ran:

    gn gen out/xxx | grep Filtering: | sort

with and without the patch for all configuration
(cross-compiling Windows on Linux).

This is a followup of https://crrev.com/c/2418443 that missed
some of the usages (as not all configuration were tested).

TBR=jochen

Bug: 1018739
Change-Id: I76d38ec4e3720d36de30bb7921148ca76b3d4d01
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2428894Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Commit-Queue: Sylvain Defresne <sdefresne@chromium.org>
Auto-Submit: Sylvain Defresne <sdefresne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#810362}

Components have rules about dependencies of higher vs. lower layers.
Make note that //printing is a lower layer, similar to //gpu.

Change-Id: Ifee3a053561a157ff400e16aeede4452486247da
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2424069Reviewed-by: Lei Zhang <thestig@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Alan Screen <awscreen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#810361}

In [1], the view source document table was changed to word-break:
keep-all, to avoid the slow layout path for word-break:break-all.
The intention there was to not allow word breaking at all, and
have each source line on a single displayed line. The better
(correct) way to achieve that is to use the white-space property,
as pointed out by kojii@ in [1]. This CL changes the white space
property to pre, instead of nowrap (as suggested), to also
preserve white space in the source file.

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

Bug: 920571
Change-Id: I3271dcce2f7f546ea5f8a33997226e2ec4894fd8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2429204
Commit-Queue: Mason Freed <masonfreed@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Auto-Submit: Mason Freed <masonfreed@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#810360}

R=khorimoto@chromium.org

Bug: 1045266
Test: OSSettingsNetworkProxySection*
Change-Id: I3594eadfee74353e4e9b91ced94906baa81d3813
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2429245Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Commit-Queue: James Hawkins <jhawkins@chromium.org>
Cr-Commit-Position: refs/heads/master@{#810359}

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

Quirks mode layout is slower, so change to no-quirks.

Note that this goes against the spec [1], which mandates quirks
mode for text documents. An issue [2] has been raised to change
that, but in the meantime, this seems like a very low (compat)
risk change. For now, however, the WPT test will not be changed,
and a broken expectation will be committed.

[1] https://html.spec.whatwg.org/multipage/browsing-the-web.html#read-text
[2] https://github.com/whatwg/html/issues/5939

Bug: 1131185
Change-Id: If7ac8cbe8b4ec277f2cb288d120698b9bacf773c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2425109
Commit-Queue: Mason Freed <masonfreed@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Auto-Submit: Mason Freed <masonfreed@chromium.org>
Cr-Commit-Position: refs/heads/master@{#810357}

This adds interface to request new metrics
Example of usage: crrev.com/c/2426728
Payload implementation: ag/12668933

BUG=b:169211158
TEST=Locally in prototype

Change-Id: If89cb8ba6e136ac0e1bb7f60b3e078b8624b3639
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2424587Reviewed-by: Dominick Ng <dominickn@chromium.org>
Commit-Queue: Yury Khmel <khmel@google.com>
Auto-Submit: Yury Khmel <khmel@google.com>
Cr-Commit-Position: refs/heads/master@{#810356}

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

The new SharedImage path for VTVideoDecodeAccelerator needs to know
whether or not it is on the passthrough decoder. Plumb this through.

This is prerequisite to enabling SkiaRenderer on macOS.

Bug: 1108909
Change-Id: I79d5f936cd5852ab33938e530fb739a5fb3f3045
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2427212Reviewed-by: Dan Sanders <sandersd@chromium.org>
Commit-Queue: ccameron <ccameron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#810354}

SkiaRenderer SKP mode is not useful anymore, so remove it to make
SkiaRenderer cleaner.
For supporting SW compositing, we should be able to implement a new
SkiaOutputSurface for it.

Bug: 1130976
Change-Id: Id2faadfb9949101378da7e226245a6ffd2a640a4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2422255Reviewed-by: weiliangc <weiliangc@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Jonathan Backer <backer@chromium.org>
Commit-Queue: Peng Huang <penghuang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#810353}

base/allocator/allocator_shim_default_dispatch_to_mac_zoned_malloc.h
is unused.  Removes it.

Change-Id: I26e88508c972b3912849269845ca873e838d3425
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2428289Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Benoit L <lizeb@chromium.org>
Commit-Queue: Yuki Shiino <yukishiino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#810352}

Exclude LayoutText when calculating compositing reasons for SVG
children.

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

The change to notify input method about type change in omnibox during
CJK TIP[1] causes regression that switching to a new tab will change JPN
TIP to English mode instead of Hiragana mode. The reason is that when
input method is notified about the text input type change, Windows input
service is also notified about the change. Therefore, the input mode is
changed from hiragana mode to English mode in JPN TIP.

We should only notify input service if the input type is changed to a
different value. We should also use the cached input type to find the
associated TSF document.

 [1]: I0266d9617277696ccb8bfa42ad76f9cbc3d802f3
      fe7e213c

Bug: 1108845
Bug: 1124612

Change-Id: I9ec643c7d2058695e8bc396d764ba598d6235b88
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2392415Reviewed-by: Michael Wasserman <msw@chromium.org>
Reviewed-by: Siye Liu <siliu@microsoft.com>
Reviewed-by: Yohei Yukawa <yukawa@chromium.org>
Commit-Queue: Siye Liu <siliu@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#810350}

This is a fairly basic test that simply attaches 1000 open and
closed declarative shadow roots.

Bug: 1042130
Change-Id: I8185b2f7f283d8480647a07971812ef62adee1f8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2422154
Auto-Submit: Mason Freed <masonfreed@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: John Chen <johnchen@chromium.org>
Commit-Queue: John Chen <johnchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#810349}

VoiceOver bug.

On MacOS 10.15, there is a Voiceover bug where the webpage reads
automatically, even when the “Automatically speak the webpage” checkbox
in Voiceover Utility isn’t checked. That checkbox is unchecked by
default, so we should make Chrome have the best behavior for the
default. VoiceOver in MacOS 11 (expected launch September/October)
fixes that bug, but introduces many new bugs in both Chrome and Safari.
We would like to fix 10.15 so that users do not need to upgrade to 11
if they do not want to.

The fix: Do not fire any AXLoadComplete events in MacOS 10.15 only.

For a longer explanation of this change, see this document:
https://docs.google.com/document/d/19s6E0hjTyzB9XU44bdCpXNOaQ8c6nbLRnJbR1EsltL4/edit#

Bug: 1049320
Change-Id: I48daf81da431d8965163fe99c7c448dc8f9403f4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2427070Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Commit-Queue: Abigail Klein <abigailbklein@google.com>
Cr-Commit-Position: refs/heads/master@{#810348}

Test: manual
Bug: 1120132
Change-Id: I288ba34d7843dde8077a0c998d02d080b11e5412
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2426466
Commit-Queue: Sammie Quon <sammiequon@chromium.org>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#810347}

This flag is still useful (and relied on for several tests) so we
don't want to remove it yet.  We are working on a second version
of the KeyboardLock spec which will allow callers to specify whether
they want to capture system keyboard events.  Once that spec is
signed off, we plan to implement the feature and remove this flag.

Change-Id: Ifd5d07c7643213eea3060deefe59659d3d0bcce8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2429144
Commit-Queue: Gary Kacmarcik <garykac@chromium.org>
Reviewed-by: Gary Kacmarcik <garykac@chromium.org>
Cr-Commit-Position: refs/heads/master@{#810346}

ExpiryInspectingRecordExpiryDelegate uses Trust Tokens signed redemption
records' associated token issuance verification keys in order to decide
whether a given signed redemption record has expired. This is a little
subtle, because signed redemption records *also* have associated public-
key signatures, verified by "signed redemption record verification keys,"
which are distinct from SRRs' associated token issuance verification
keys.

For the most part, the comments in
expiry_inspecting_record_expiry_delegate.{h,cc} go out of their way to
make the distinction explicit, but there was a comment that mentioned
the SRR's "verification key", rather than its associated token issuance
verification key.

This patch updates the comment in question to be clearer.

Tbr: svaldez@chromium.org
Change-Id: I87f45aa411c9c4462bf7fd4ce00a92ca41056daa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2429304Reviewed-by: Steven Valdez <svaldez@chromium.org>
Reviewed-by: David Van Cleve <davidvc@chromium.org>
Commit-Queue: Steven Valdez <svaldez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#810345}

These tests were disabled on on Window and/or Mac for being
flaky. They passed 3000 iterations on the bots with no
issues.

Bug: 122154, 238733
Change-Id: I4aeeeddcee340837651105c6e703f4100790e6b6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2411405Reviewed-by: Kelvin Jiang <kelvinjiang@chromium.org>
Commit-Queue: David Bertoni <dbertoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#810344}

This renames the mText field to mTextToShare, and mText is then used as the raw text field.
This allows the Sharing Hub to use the shared text by itself.

Bug: 1120093, 1130072
Change-Id: Ieb7972a4ec5b427f71ffacab79406d8fc63f86dc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2415210Reviewed-by: Scott Little <sclittle@chromium.org>
Reviewed-by: Tanya Gupta <tgupta@chromium.org>
Commit-Queue: Sophey Dong <sophey@chromium.org>
Cr-Commit-Position: refs/heads/master@{#810343}

The existing policies specified a couple of owners but that is
a bit fragile.  A better way is to use the OWNERS file in the
//remoting directory since we need to make sure it is kept
up to date.

Change-Id: Ia968c9833275e0a131e87b8c1e7d3e79605897f3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2427140Reviewed-by: Jamie Walch <jamiewalch@chromium.org>
Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Commit-Queue: Joe Downing <joedow@google.com>
Cr-Commit-Position: refs/heads/master@{#810342}

Give `Uri::Pim::kDefaultPorts` a local scope, by moving it inside
Uri::Pim::GetDefaultPorts(). Then it is only initialized on first use
instead on process startup.

Bug: 537099
Change-Id: I66033ca86eb2182ae670351cd53869d988d04c0f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2427034Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
Reviewed-by: Piotr Pawliczek <pawliczek@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#810341}

Returns the correct next expiration time for the stored public
certificates. Because the expirations times were being persisted as a
map using the certificate ID as the key, they were sorted by the ID and
not the expiration time. We now sort by expiration time when retrieving
from prefs.

Changed the fake certificate IDs in the unit tests so tests will fail
if the certificate are not sorted.

Change-Id: Idd546c62939bd4bb4c62be405a3f8d9cec79de70
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2429287
Commit-Queue: Josh Nohle <nohle@chromium.org>
Commit-Queue: James Vecore <vecore@google.com>
Auto-Submit: Josh Nohle <nohle@chromium.org>
Reviewed-by: James Vecore <vecore@google.com>
Cr-Commit-Position: refs/heads/master@{#810340}

The custom scrollbar has been affected by pseudo-class :hover.
However that in the internal popup was not affected :hover.

In this change, Hover styles will be calculated using temporality declared CustomScrollbar.
And that will be appended via AppendOwnerElementPseudoStyles function.

Bug: 1076508
Change-Id: Ic57ca5c36b91b221bb3488292bfe2eb53b988ac2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2418527Reviewed-by: Mason Freed <masonfreed@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Seokho Song <0xdevssh@gmail.com>
Cr-Commit-Position: refs/heads/master@{#810339}

Bug: 1116643
Change-Id: Ie50f656ef08645b53c0841b8efb77abe0fa4ba87
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2425105Reviewed-by: Will Harris <wfh@chromium.org>
Reviewed-by: kylechar <kylechar@chromium.org>
Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Commit-Queue: Jun Liu <yjliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#810338}

Currently, the cursor/hover doesn't update after scroll or layout
changes in an OOPIF, unless a subsequent mouse move is sent. Therefore,
we should check to see whether the mouse hover state should be updated
at BeginMainFrame.

Bug: 1126198
Change-Id: I3bea312d0687a3b7f125eb35553ea58d3dda9247
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2406669Reviewed-by: Robert Flack <flackr@chromium.org>
Reviewed-by: Olga Gerchikov <gerchiko@microsoft.com>
Commit-Queue: Sahir Vellani <sahir.vellani@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#810337}

A bug in older versions of Xcode erroneously marked
backgroundTimeRemaining as thread unsafe.  This has been
fixed in Xcode, so remove the workaround.

Change-Id: I54e5cbe45a97e4081812e71ee86f4df0c36e8c9a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2427630Reviewed-by: Eugene But <eugenebut@chromium.org>
Reviewed-by: John Wu <jzw@chromium.org>
Commit-Queue: Justin Cohen <justincohen@chromium.org>
Auto-Submit: Justin Cohen <justincohen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#810336}

We've recently introduced //chromeos/ui for lacros. I'd like to
minimize the size of //ui/chromeos (or eliminate it) to reduce
confusion.

search_box is only used in ash, so move it there.

This CL just moves the files, minimizing changes so that git's rename
tracking will detect the rename. I'll fix the namespace in a followup.

Bug: 1131641
Test: compiles
Change-Id: Ic7cfaf06fb8b0d683ca7bd15986a01f0dd1d7733
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2429432Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#810335}

Change-Id: I7b49ca07c6366964789fade31114762122b81c83
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2314792Reviewed-by: Max Moroz <mmoroz@chromium.org>
Commit-Queue: Adrian Taylor <adetaylor@chromium.org>
Cr-Commit-Position: refs/heads/master@{#810334}

Adds a histogram that records the time it took
to fetch the data from the server.

BUG=1110373

Change-Id: Ib5a2af78ccd18929bb62571c3fa171c27808af1d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2425170Reviewed-by: Tommy Steimel <steimel@chromium.org>
Reviewed-by: Brian White <bcwhite@chromium.org>
Commit-Queue: Becca Hughes <beccahughes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#810333}

Move from DnsConfig into its own file in /net/dns/public/. Should remove
all net-external dependency on DnsConfig.

Also, while renaming all the SecureDnsMode references, take the
opportunity to rename the values from MACRO_STYLE to kConstStyle as is
more recently required by the Google C++ style guide.

Bug: 1129993
Change-Id: I1d57bba9cd0e40908c500dcfa9c64365885f27b5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2418806Reviewed-by: Dan McArdle <dmcardle@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Esmael Elmoslimany <aee@chromium.org>
Reviewed-by: Ryan Sleevi <rsleevi@chromium.org>
Commit-Queue: Eric Orth <ericorth@chromium.org>
Cr-Commit-Position: refs/heads/master@{#810332}

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 feature policy browser tests to:

  - Use the header to deny, rather than implicitly allow features in
    subframes, when that is the behavior being tested.
  - Use the allow attribute to explicitly allow feaures in subframes,
    when that is the behavior being tested.

These updates will work both before and after the header behavior
change.

Bug: 1095641
Change-Id: I366f23d14f623c13cd9cd0ec130be70d034f6527
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2425004
Commit-Queue: Ian Clelland <iclelland@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#810331}

Let's Encrypt have announced[1] a transition to new intermediates. This
change adds these new intermediates to Tor's pinning set.

[1] https://letsencrypt.org/2020/09/17/new-root-and-intermediates.html

Change-Id: Ib6df959a4fea407eb0e379c507cb2a860ff943d3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2427555
Auto-Submit: Adam Langley <agl@chromium.org>
Commit-Queue: Nick Harper <nharper@chromium.org>
Reviewed-by: Nick Harper <nharper@chromium.org>
Cr-Commit-Position: refs/heads/master@{#810330}