Update mutter to include fixes made on the compositor side:
https://crrev.com/c/6318620https://crrev.com/c/6371819
Add a couple fixes to tab_drag_controller_interactive_uitest.cc:
- Prevent `BrowserChangeWaiter` from not running the closure in case
quit is called another time before the closure gets to run.
- In `DragAllToSeparateWindow` add a similar step as
`DragToSeparateWindow` to ensure the tabs are dragged to the end of the
tab strip.
Use 1920x1200 display size in xvfb.py when running tests with mutter.
This ensures the tab drag tests request a valid size which is more than
the minimum size of a chrome window.
Update the test filter based on tests that are now passing with the
mutter changes, and add 2 new exclusions for tests that are flaky or
broken on mutter.
See the attached bug for more details.
Bug: 391907155
Change-Id: Ieb46a7209adfcd2a11ff04e8cb738b71b6c3e34a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6310437
Reviewed-by: David Pennington <dpenning@chromium.org>
Reviewed-by: Max Ihlenfeldt <max@igalia.com>
Reviewed-by: Ben Pastene <bpastene@chromium.org>
Commit-Queue: Orko Garai <orko@igalia.com>
Cr-Commit-Position: refs/heads/main@{#1436130}
Updates the unexpected finder code and all of its users to support
full wildcards in expectations. Whether this or the older, trailing-only
wildcards are used is determined by the typ code being added in
crrev.com/c/6340368.
This should not result in any functional changes unless an
expectation file specifies full_wildcard_support: true.
Bug: 377660080
Change-Id: Iad2646a2afca8aeb7a56aa8b6060cc372495562a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6349402
Reviewed-by: Ben Pastene <bpastene@chromium.org>
Commit-Queue: Brian Sheedy <bsheedy@chromium.org>
Reviewed-by: Yuly Novikov <ynovikov@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1436119}
Create a new feature flag - `CrosGeoApiKey`. Behind this flag will be
developed the changes to migrate ChromeOS system services and
Chrome-on-ChromeOS to use a different GCP endpoint for location
resolution.
For more details go/new-api-keys-for-cros-geo.
Bug: 403537535
Change-Id: I0fac327f97ee47f5e97669144c6bab75e88e2d65
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6355829
Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Zauri Meshveliani <zauri@chromium.org>
Auto-Submit: Zauri Meshveliani <zauri@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1436027}
This CL adds ProgramTemplates to the generated `ChromiumProfile.swift`
for fuzzilli to test specifically APIs called with the V8 fast API.
Bug: 41492790
Change-Id: Ia0e34e526ea679eac7c3e60109f8300ef35e03c1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6366774
Commit-Queue: Andreas Haas <ahaas@chromium.org>
Reviewed-by: Paul Semel <paulsemel@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1435940}
Update the field trial testing config for WinPlatformLocationProvider to
include enabling feature WinSystemLocationPermission and remove config
for WinSystemLocationPermission study.
Change-Id: Ie0befcedc199f91a77db37666983adb62f17d674
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6377982
Commit-Queue: Jack Hsieh <chengweih@chromium.org>
Reviewed-by: Alvin Ji <alvinji@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1435619}
This CL enables kSetUpListShortenedDuration and
kSetUpListWithoutSignInItem by default, removes the fieldtrial configs,
and removes/fixes no longer relevant unit tests.
Bug: 383567901, 383566934
Change-Id: Idb299eab3c525be34e15f3824d06437265c21a79
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6373544
Reviewed-by: Scott Yoder <scottyoder@google.com>
Commit-Queue: Hira Mahmood <hiramahmood@google.com>
Cr-Commit-Position: refs/heads/main@{#1435568}
android_browsertests on android-x64-rel was not sharded enough due to a
bad overhead calculation. It looks like the suite was just stuck in an
unforunate set of shardings which made the overhead look far worse than
it really was (~10mins). To address cases like this, clamp the overhead
calculation to approximately the current min and max overheads. In the
long term we should use more than 1 shard configuration.
Bug: None
Change-Id: I5470efc7afcd6aeaa8a9cc28c09ec207cb3bb57c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6374266
Reviewed-by: Benjamin Joyce (Ben) <bjoyce@chromium.org>
Commit-Queue: Struan Shrimpton <sshrimp@google.com>
Cr-Commit-Position: refs/heads/main@{#1435477}
This change enables several cc_unittests that rely on
DisplayReceivedCompositorFrame to pass, and also exposes a few tests that
fail because of missing data in the produced frame. Issues have been
filed for the remaining failures.
Bug: 404941414
Change-Id: I804ab79fcafecf64dba8bc775167d6d804a43c7d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6369932
Auto-Submit: Victor Miura <vmiura@chromium.org>
Commit-Queue: Colin Blundell <blundell@chromium.org>
Reviewed-by: Colin Blundell <blundell@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1435284}
Add field trial testing config for enabling WinPlatformLocationProvider that is to use a new geolocation backend backed by the platform location provider on Windows.
Change-Id: Ide3005af1f83b62fda5f3e70db6580c4bd3a2295
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5891631
Reviewed-by: Matt Reynolds <mattreynolds@chromium.org>
Commit-Queue: Jack Hsieh <chengweih@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1435231}
We were disabling TreesInViz mode for trees that don't use
'use_layer_lists' mode. The real intent was to disable TreesInViz for
UI.
This change enables TreesInViz for '!use_layer_lists' and excludes
'is_layer_tree_for_ui' instead.
Bug: 404813701
Change-Id: I45b4a1e2c65fa7bca503a86c1a48f50fca562227
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6371884
Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Commit-Queue: Victor Miura <vmiura@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1435032}
Windows sandbox restrictions cause DirectReceiver's ThreadLocalNode to
crash in Transport::CreatePair. As a workaround create a transport for
the thread that's expected to use DirectReceiver before the sandbox
is locked down (which is still in single threaded context), and pass
it to ThreadLocalNode when it's assigned to the thread.
Bug: 40266729
Change-Id: Ic881eac9cf570d023a362b2cfc12f8234d706eb5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6332336
Reviewed-by: Alex Gough <ajgo@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Joe Mason <joenotcharles@google.com>
Cr-Commit-Position: refs/heads/main@{#1434954}
This CL cleans up EnableScreenshotProtection and also addresses
crbug.com/378132592 by cleaning up `IsDataProtectionEnabled()`.
The `SkipUrl()` call in `ApplyDataProtectionSettings()` is kept since
it's a static function that might be called even if a
`DataProtectionNavigationController` hasn't been initialized.
The `IsInPrimaryMainFrame()` call in `DidFinishNavigation()` is kept,
see the comment in that function for details.
Bug: 378132592
Change-Id: Iec133a4179ab27d58e09a2e1ae9d092bef72bba9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6361985
Reviewed-by: Caroline Rising <corising@chromium.org>
Reviewed-by: Nasser Al-shawwa <alshawwa@chromium.org>
Auto-Submit: Dominique Fauteux-Chapleau <domfc@chromium.org>
Commit-Queue: Caroline Rising <corising@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1434872}
For the Android WebView to properly handle edge-to-edge mode, the
safe-area-inset values need to account for not only the display cutout
but also the system bars.
Bug: 40699457
Change-Id: I68f6e541b55ff0909f690511e6ac80409ed9faf4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6295663
Commit-Queue: Peter Conn <peconn@chromium.org>
Reviewed-by: Peter Conn <peconn@chromium.org>
Reviewed-by: Richard (Torne) Coles <torne@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1434844}
