0
Commit Graph

1553053 Commits

Author SHA1 Message Date
129bb5341c [AriaNotify] Scope v1 feature and gate v2 properties behind flag
This CL scopes the ARIA Notify API to accept only a string
`announcement` and a ax::mojom::AriaNotificationPriority `priority`
(values of which can be "high" or "normal", with "normal" being the
default value).

This API shape will serve as V1 of the feature, as agreed upon by the
ARIA working group: https://github.com/w3c/aria/issues/2426

Future versions of the API may include properties of `interrupt` and
`notification_id` (soon to be renamed `type`). More information about
these properties, and the feature in general, can be found in the
explainer:
https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/Accessibility/AriaNotify/explainer.md

This CL gates the use of `interrupt` and `notification_id` behind the
"AriaNotifyV2" feature flag. As part of the process of serializing the
ARIA notification attributes, `notification_id` will be passed to the
AXNodeData as an empty string and `interrupt` will be passed as kNone
unless the AriaNotifyV2 flag is enabled.

We cannot even read the value of the `notification_id` or `interrupt`
properties that may be passed by the web author as a part of V1 -- if we
don't avoid reading the properties, then feature detection for those
properties will be enabled. See more:
https://github.com/w3c/aria/issues/2426#issuecomment-2634700360

This CL also adds new tests that use the AriaNotifyV2 feature flag.

AX-Relnotes: This feature is behind a feature flag so it should not
impact the experience of users who are not enabling the flag.

Bug: 326277796

Change-Id: Id72dab40aea10daab3449bd32d2ab99a3746d76d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6306426
Reviewed-by: Alison Maher <almaher@microsoft.com>
Commit-Queue: Evelynn Kaplan <evelynn.kaplan@microsoft.com>
Reviewed-by: Benjamin Beaudry <benjamin.beaudry@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#1431762}
2025-03-12 14:38:46 -07:00
eacdc6d0f1 Remove info.compatibilityMode in webgpu_test.cc
Bug: 395855516
Change-Id: I9f35717a7d85f737203e5e950a983628f045358e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6349621
Commit-Queue: Shrek Shao <shrekshao@google.com>
Reviewed-by: Brandon Jones <bajones@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1431761}
2025-03-12 14:38:08 -07:00
1c44ce70bc [iOS] Share extension - Text sharing UI
This CL adds the text sharing UI for the new share extension.

Bug: 396326825
Change-Id: Id019c7d90e4dc6adfed437928634d5827416f01d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6343098
Reviewed-by: Olivier Robin <olivierrobin@chromium.org>
Commit-Queue: Elmehdi Rahmaoui <erahmaoui@google.com>
Cr-Commit-Position: refs/heads/main@{#1431760}
2025-03-12 14:34:50 -07:00
e33f048404 GVariantRef improvements
A few cleanups and quality-of-life improvements for GVariantRef:

 * Remove iteration functionality from gvariant::Type. It was not
   entirely obvious what iterating should mean for a type string.
   Explicitly getting a string_view to iterate makes it clear that one
   is iterating characters.
 * Update various usages of pointers to instead use std::string_views or
   base::spans in gvariant::Type.
 * Add GVariantFrom() helper function to infer the GVariant type string
   from the passed C++ types. E.g., GVariantFrom("foo") returns a
   GVariantRef<"s">.
 * Add BoxedRef() and FilledMaybeRef() helper functions to more easily
   wrap a reference to an existing value.
 * Introduce ObjectPathCStr and TypeSignatureCStr, which reference an
   unowned string that is known to be a valid object path or type
   signature, respectively. They can reference a constant string (which
   will be verified at compile time to be valid) or an owned ObjectPath
   or TypeSignature object, and are thus useful as function parameters.

Bug: 378932951
Change-Id: Idf625de0caf5b711c477da12d34a0d2a0a2306b8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6334519
Commit-Queue: Erik Jensen <rkjnsn@chromium.org>
Reviewed-by: Lambros Lambrou <lambroslambrou@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1431759}
2025-03-12 14:30:22 -07:00
93050cc582 Roll Skia from 01ab6ffb7f65 to a52192caecad (1 revision)
https://skia.googlesource.com/skia.git/+log/01ab6ffb7f65..a52192caecad

2025-03-12 skia-autoroll@skia-public.iam.gserviceaccount.com Roll debugger-app-base from bfb2f80c0482 to 02aefa9619f3

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/skia-autoroll
Please CC danieldilan@google.com,skiabot@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Skia: https://bugs.chromium.org/p/skia/issues/entry
To file a bug in Chromium: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:gpu-fyi-cq-android-arm64;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Cq-Do-Not-Cancel-Tryjobs: true
Bug: None
Tbr: danieldilan@google.com
Change-Id: I71000b229953a404801f7178f32acfe1358d6261
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6349469
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1431758}
2025-03-12 14:29:43 -07:00
245102c9c4 Enable WebAuthn forwarding for Linux and Windows hosts
Change-Id: Ie92efb56e9fba0f6990ea8ec190fb0d879255cdc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6349779
Auto-Submit: Joe Downing <joedow@chromium.org>
Reviewed-by: Yuwei Huang <yuweih@chromium.org>
Commit-Queue: Joe Downing <joedow@chromium.org>
Commit-Queue: Yuwei Huang <yuweih@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1431757}
2025-03-12 14:28:51 -07:00
d25bb2f9eb update_client: Introduce a helper function to make timeout callbacks.
This wrapper guarantees that the callback will eventually be called even
if the recipient of the callback forgets about it.

Bug: 402773563
Change-Id: I48d23681d8b570972537d40c56d03591edea4e85
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4282299
Auto-Submit: Joshua Pawlicki <waffles@chromium.org>
Commit-Queue: Joshua Pawlicki <waffles@chromium.org>
Reviewed-by: Sorin Jianu <sorin@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1431756}
2025-03-12 14:26:13 -07:00
463e0d9dde [MaliciousApkDownloadCheck] Specify sampled ping behavior
This is part 2 of 6 of relanding code that was originally landed in
crrev.com/c/6309053 but was reverted.

This CL adds methods to the DownloadProtectionDelegate interface to
allow the delegate to specify platform-specific behavior for
1) sampled pings for allowlisted downloads, and 2) sampled pings for
unsupported file types.

For Android download protection, these are both disabled:
1) sampling allowlisted downloads does not yet make sense because the
allowlist check is not yet implemented for Android download protection
(it will be in the future);
2) sampled pings for unsupported file types are not supported.

There is no behavior change for download protection on desktop
platforms.

Bug: 397407934
Change-Id: Id61a148fa6a2a88ada60c05a4193510fa01c532d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6341930
Commit-Queue: Lily Chen <chlily@chromium.org>
Reviewed-by: Daniel Rubery <drubery@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1431755}
2025-03-12 14:25:50 -07:00
e2e7f23f6e Add @NullMarked to //com/credential_management/android
R=hnakashima@chromium.org

Bug: 389129271
Change-Id: Idf41daabb160b2fce6e879da293c2fade453cfcc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6347838
Owners-Override: Peter Wen <wnwen@chromium.org>
Reviewed-by: Henrique Nakashima <hnakashima@chromium.org>
Auto-Submit: Peter Wen <wnwen@chromium.org>
Commit-Queue: Peter Wen <wnwen@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1431754}
2025-03-12 14:24:34 -07:00
294f5615cc [cc/tiles] Avoid thread hops when there is no raster required
During scrolling, it is very common to have a compositor frame that
needs no raster. This is the case for instance when the page is static,
and we do not need a new prepaint tile. In this case, we still add three
completion tasks to the task graph, and run them on the thread pool (on
a single thread, because they are NONCONCURRENT).

This CL runs the tasks directly if they are the only required
tasks. This saves quite a bit of overhead, and 2 thread hops (compositor
-> thread pool -> compositor) per frame. From local testing, this back
and forth often takes 800us-1ms even on a relatively simple page.

Change-Id: Ic889eddbc0d121770563fb6b0fa01f4194564972
Bug: 40419088
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6330735
Reviewed-by: Jonathan Ross <jonross@chromium.org>
Reviewed-by: Victor Miura <vmiura@chromium.org>
Commit-Queue: Benoit Lize <lizeb@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1431753}
2025-03-12 14:24:22 -07:00
f515cfc2e2 Roll clank/internal/apps from ed98be9a45b5 to 6ab29df4ad88 (1 revision)
ed98be9a45..6ab29df4ad

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://skia-autoroll.corp.goog/r/clank-apps-chromium-autoroll
Please CC chrome-brapp-engprod@google.com,mheikal@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://issues.skia.org/issues/new?component=1389291&template=1850622

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Bug: None
Tbr: mheikal@google.com
No-Try: true
Change-Id: Ia00ebe4d57165611f1de3f31c620f4fbdb366165
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6350097
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Bot-Commit: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1431752}
2025-03-12 14:23:00 -07:00
34ff8f4819 Roll src/chrome/browser/glic/test/internal/ be1c3b4dc..fc133b9cd (3 commits)
be1c3b4dc8..fc133b9cd4

Created with:
  roll-dep src/chrome/browser/glic/test/internal

Bug: b:396188171
Change-Id: Ia227e9c645cda91f7c6c311c013904be48bbaa8e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6348158
Auto-Submit: Zhaoyang Li <zhaoyangli@chromium.org>
Reviewed-by: Carlos Knippschild <carlosk@chromium.org>
Commit-Queue: Zhaoyang Li <zhaoyangli@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1431751}
2025-03-12 14:21:54 -07:00
6c41d3f32d [Collaboration] Add more test cases for url interception
Bug: 340932804
Change-Id: If0492a5c4b4d3d177a665c79ba9961f5d0df65cc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6329911
Reviewed-by: Siddhartha S <ssid@chromium.org>
Commit-Queue: Hailey Wang <haileywang@google.com>
Cr-Commit-Position: refs/heads/main@{#1431750}
2025-03-12 14:20:51 -07:00
0a3954d5d2 Roll Chrome Mac PGO Profile
Roll Chrome Mac PGO profile from chrome-mac-main-1741780748-8fdebc732578350ec1c0b4e5e3d5b64556e164a8-56cfc4af1dc0afe87bc582e9f0a642ac1e4cb8fc.profdata to chrome-mac-main-1741802349-358ad4f79d648b83f55d2e67fef0ca8a575971f4-d978d40415d40f96a628e89e24134924505c336e.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-mac-chromium
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium main branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Cq-Include-Trybots: luci.chrome.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Merge-Approval-Bypass: Chrome autoroller
Change-Id: I9fb1635de1bd38a8409467139616858a4127acff
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6349381
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1431749}
2025-03-12 14:18:14 -07:00
c486b638ae Roll ios_internal from e131251db849 to 28bf7f599bb6
e131251db8..28bf7f599b

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://skia-autoroll.corp.goog/r/ios-internal-chromium-autoroll
Please CC chrome-brapp-engprod@google.com,rkgibson@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://issues.skia.org/issues/new?component=1389291&template=1850622

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Bug: None
Change-Id: I5e542d47ad5915bcfa108a081b4ad0b86d7fd467
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6349742
Bot-Commit: 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/main@{#1431748}
2025-03-12 14:17:20 -07:00
4fc825076b [Gap Decorations]: Use GapIntersections to paint simple gap cases
This CL uses `GapIntersections` set up from crrev.com/c/6313080 to paint
gap decorations within grid. Gap decorations are painted based on
(start, end) pairs of GapIntersection points. Hence, this change uses
these intersection points stored in the gap geometry for painting.

Currently, this CL does not account for the `*-rule-break` and
`*-rule-outset` properties, meaning gap decorations are painted from the
first intersection to the last intersection within a gap (i.e.
rule-break: none).

Tests that exercise this CL were added in crrev.com/c/6101656 and
augmented in crrev.com/c/6300029.

Subsequent CLs will augment the paint code to factor in `rule-break` and
`rule-outset` properties and eventually clean up the old implementation
of gap geometry.

Bug: 357648037
Change-Id: Ice50a0cf2bb9281c44fb0517f83ad07167bb0516
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6321085
Reviewed-by: Kevin Babbitt <kbabbitt@microsoft.com>
Reviewed-by: Alison Maher <almaher@microsoft.com>
Commit-Queue: Sam Davis Omekara <samomekarajr@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#1431747}
2025-03-12 14:17:05 -07:00
a20655734d Roll DevTools Frontend from d85bddcbf446 to 2f89fb20f460 (1 revision)
d85bddcbf4..2f89fb20f4

2025-03-12 nancyly@chromium.org [RPP insight] show highlight effect  for all network request in the network tree

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@rotations.google.com,liviurau@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://issues.skia.org/issues/new?component=1389291&template=1850622

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Bug: None
Change-Id: I13334f76aa5711c5c0f0b911256a90f60b40fc8f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6349887
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1431746}
2025-03-12 14:16:05 -07:00
fd56ed7d4d Updating XTBs based on .GRDs from branch main
Change-Id: I63187ab6caec6de626eb3de36b7d29e3d41326cc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6349976
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Auto-Submit: Ben Mason <benmason@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1431745}
2025-03-12 14:15:44 -07:00
e3eb36085b Roll V8 from 03c477fa6f79 to 5fb698168a16 (13 revisions)
03c477fa6f..5fb698168a

2025-03-12 v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Version 13.6.49
2025-03-12 mliedtke@chromium.org Revert "[inspector][test] Fix tests assuming precise GC control"
2025-03-12 fgm@chromium.org Revert "[heap] Do not reset allocation limit with initial old gen size"
2025-03-12 clemensb@chromium.org [wasm] Fix crash with --single-threaded
2025-03-12 omerkatz@chromium.org [heap] Introduce precise pinning for full GC
2025-03-12 paolosev@microsoft.com [wasm] Add fuzzers for the Wasm interpreter
2025-03-12 irezvov@chromium.org [wasm][growable-stacks] Spill uncompressed pointers on callers frame
2025-03-12 v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update V8 DEPS (trusted)
2025-03-12 dinfuehr@chromium.org [heap] Do not reset allocation limit with initial old gen size
2025-03-12 mliedtke@chromium.org [fuzzer][wasm] Disable liftoff code flushing
2025-03-12 nikolaos@chromium.org [inspector][test] Fix tests assuming precise GC control
2025-03-12 pthier@chromium.org [json] Micro-optimize stringify fast-path
2025-03-12 victorgomes@chromium.org [maglev] Always iterate vobjects before analyse phase

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/v8-chromium-autoroll
Please CC liviurau@google.com,machenbach@google.com,v8-waterfall-gardener@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://issues.skia.org/issues/new?component=1389291&template=1850622

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Cq-Include-Trybots: luci.chromium.try:linux-blink-rel;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:android_optional_gpu_tests_rel;luci.chromium.try:dawn-linux-x64-deps-rel
Change-Id: I14f6ad70ddc73cec680baf487d571edfff00d932
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6349885
Bot-Commit: 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/main@{#1431744}
2025-03-12 14:11:17 -07:00
a8b4cbac46 Allow Cloud hosts to forward WebAuthn requests
Bug: 401269925, 389154295
Change-Id: Ifc0f0d47f168fc3edb4551f126e666df9afb29e7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6349219
Commit-Queue: Joe Downing <joedow@chromium.org>
Reviewed-by: Yuwei Huang <yuweih@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1431743}
2025-03-12 14:10:17 -07:00
ff9c41bbc1 Roll ANGLE from 9f9a0dfd2a35 to 354a54638f2f (3 revisions)
9f9a0dfd2a..354a54638f

2025-03-12 i.nazarov@samsung.com Vulkan: Remove recreateSwapchain ContextVk dependency
2025-03-12 cnorthrop@google.com Reland "Add GL_BGRA_EXT as a sized renderable format"
2025-03-12 kkinnunen@apple.com Metal: Fix line loop indexes for primitive restart

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/angle-chromium-autoroll
Please CC angle-team@google.com,geofflang@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in ANGLE: https://bugs.chromium.org/p/angleproject/issues/entry
To file a bug in Chromium: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;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: geofflang@google.com
Change-Id: I281f996b4b2709156c4eb11a9b132b9532d2d36a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6349388
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1431742}
2025-03-12 14:10:07 -07:00
0acb6c7759 Add feature flag for making the glic window user-resizable
This only works for Mac; more changes are needed for Windows.

No attempt is made yet to prevent automatic bounds changes during
manual resizing, nor to enforce minimum or maximum sizes.

Bug: 402795394
Change-Id: I1fdea39e1a54887775a7c7d39c6671a25221bcd0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6349300
Commit-Queue: Ian Wells <iwells@chromium.org>
Reviewed-by: Erik Chen <erikchen@chromium.org>
Auto-Submit: Ian Wells <iwells@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1431741}
2025-03-12 14:09:09 -07:00
f7b0336ac8 [History] Don't run query history continuation if it is not set
query_history_continuation_ should always be set when it is run as it
runs onScrolledToBotton of the History UI and is set during the init.
However, sometimes it is not. While this doesn't fix the root cause it
should prevent the crashes.

Bug: 401529290
Change-Id: I1c38f7cee3d2c00d0dd66dac81cd766a992a934b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6347837
Reviewed-by: John Lee <johntlee@chromium.org>
Commit-Queue: Marlon Facey <mfacey@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1431740}
2025-03-12 14:08:58 -07:00
3d74dc4115 Add @NullMarked to //com/data_sharing/internal
R=martinkong@google.com

Bug: 389129271
Change-Id: I935097d4f7ce6d9a98faa109fb241b82773bebcd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6347762
Commit-Queue: Peter Wen <wnwen@chromium.org>
Auto-Submit: Peter Wen <wnwen@chromium.org>
Reviewed-by: Martin Kong <martinkong@google.com>
Owners-Override: Peter Wen <wnwen@chromium.org>
Commit-Queue: Martin Kong <martinkong@google.com>
Cr-Commit-Position: refs/heads/main@{#1431739}
2025-03-12 14:08:00 -07:00
8173f02e19 Update defaults for cueing nudge cap params
Change-Id: I1f21d88e9c01590cfcb5614c107e00178a08afa6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6343482
Auto-Submit: Sophie Chang <sophiechang@chromium.org>
Commit-Queue: Raj T <rajendrant@chromium.org>
Reviewed-by: Raj T <rajendrant@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1431738}
2025-03-12 14:07:49 -07:00
c80c788625 Roll Perfetto Trace Processor Win from ae4889e8d142 to 97c9ad19b7fe
ae4889e8d1..97c9ad19b7

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/perfetto-trace-processor-win-chromium
Please CC chrometto-team@google.com,perfetto-bugs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Tbr: perfetto-bugs@google.com
Change-Id: I15b1889cb42eb36ba81452435210611d8b7457af
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6349778
Bot-Commit: 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/main@{#1431737}
2025-03-12 14:06:52 -07:00
58d15af681 Revert "[Desktop Android] Compile ExtensionApiTest on Desktop Android"
This reverts commit 02682ddc48.

Reason for revert:
LUCI Bisection has identified this change as the culprit of a build failure. See the analysis: https://ci.chromium.org/ui/p/chromium/bisection/compile-analysis/b/8720572648125296145

Sample failed build: https://ci.chromium.org/b/8720572648125296145

If this is a false positive, please report it at http://b.corp.google.com/createIssue?component=1199205&description=Analysis%3A+https%3A%2F%2Fchromium-review.googlesource.com%2Fc%2Fchromium%2Fsrc%2F%2B%2F6335690&format=PLAIN&priority=P3&title=Wrongly+blamed+https%3A%2F%2Fci.chromium.org%2Fui%2Fp%2Fchromium%2Fbisection%2Fcompile-analysis%2Fb%2F8720572648125296145&type=BUG

Original change's description:
> [Desktop Android] Compile ExtensionApiTest on Desktop Android
>
> Right now, there are two ExtensionApiTest implementations, which are
> nearly identical. Compile the "main" ExtensionApiTest implementation on
> Desktop Android.
>
> One complication here is that the subclasses of ExtensionApiTest (i.e.,
> individual test suites) may rely on functionality in
> ExtensionBrowserTest, which is still unavailable in Android. Solve this
> by having ExtensionApiTest inherit from ExtensionPlatformBrowserTest on
> Desktop Android builds, and ExtensionBrowserTest on other builds. While
> this does make the inheritance tree a little more complex, in practice,
> this is what users on ExtensionPlatformApiTest are already doing (since
> ExtensionApiTest inherits from ExtensionBrowserTest, while
> ExtensionPlatformApiTest inherits from ExtensionPlatformBrowserTest).
>
> After this inheritance change, modifying the rest of ExtensionApiTest
> to compile is fairly straightforward, either compiling with no
> changes or trivial modifications, or being cleanly separated by other
> features (like platform apps). The one exception to this is the method
> to open a URL, which has different implementations on desktop android
> and other platforms. To accommodate this, introduce an
> ExtensionBrowserTestPlatformDelegate, which can be responsible for
> handling these so that we isolate the platform-specific code and avoid
> adding lots of if-defs in the other test classes. In the future, this
> can be used in ExtensionPlatformBrowserTest to clean it up a bit.
>
> This CL paves the way for getting rid of DesktopAndroidExtensionApiTest.
>
> Bug: 401522580
> Change-Id: I9ff3d1deb9f5fdb0b09c65392d1928286fdbe791
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6335690
> Reviewed-by: David Bertoni <dbertoni@chromium.org>
> Commit-Queue: Devlin Cronin <rdevlin.cronin@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1431718}
>

Bug: 401522580
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Change-Id: I326fcd631eb0b9e204081c9f53ec394a71a55777
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6349400
Commit-Queue: luci-bisection@appspot.gserviceaccount.com <luci-bisection@appspot.gserviceaccount.com>
Bot-Commit: luci-bisection@appspot.gserviceaccount.com <luci-bisection@appspot.gserviceaccount.com>
Owners-Override: luci-bisection@appspot.gserviceaccount.com <luci-bisection@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1431736}
2025-03-12 14:06:37 -07:00
548d7c3f70 Change base::expected to use std::variant under the hood
It previously used absl::variant, which appears not to be as constexpr
friendly. E.g., it is possible for a constexpr function to return
base::expected<void, std::string> when using std::variant, but not when
using absl::variant.

Additionally adds the include for absl::variant to a few files that were
previously relying on it being included transitively via
base/types/expected.h so they continue to compile, and removes one
instance of an unused variable that the compiler can properly detect now
that std::variant is used.

Change-Id: Ibab13382202c69fd45c5aff318e8f56b3ac0d30f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6345816
Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Erik Jensen <rkjnsn@chromium.org>
Owners-Override: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1431735}
2025-03-12 13:59:06 -07:00
bd53fe1602 Roll clank/internal/apps from 0fc6caf5d502 to ed98be9a45b5 (1 revision)
0fc6caf5d5..ed98be9a45

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://skia-autoroll.corp.goog/r/clank-apps-chromium-autoroll
Please CC chrome-brapp-engprod@google.com,mheikal@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://issues.skia.org/issues/new?component=1389291&template=1850622

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Bug: None
Tbr: mheikal@google.com
No-Try: true
Change-Id: If667b408bd2c314d19b9872400078f690a1d9ab0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6349744
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Bot-Commit: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1431734}
2025-03-12 13:55:50 -07:00
5632c8863d [Read anything] Lit migration- line spacing menu
Bug: 352583619
Change-Id: Ice243378c91510f36c8fa6f413d8d3e2c54b14ac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6347011
Commit-Queue: Eitan Goldberger <eitang@google.com>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1431733}
2025-03-12 13:52:43 -07:00
038d5e4a97 Add @NullMarked to //c/b/tab:java
Kept an instance of NullUnmarked for MockPersistedTabData as it passes
null for a callback that production code expects to be non-null. This
should likely be fixed in the test instead of adding a ton of
unnecessary null checks in production code.

Patch 1: automated annotator
Patch 2: manual changes
Patch 3: formatting
Patch 4: commit description update
Patch 5: add a ton of manual fixes
Patch 6: fix a test
Patch 7: commit description update

Bug: 389129271
Change-Id: I4081876927bcd87ccbe1baa34004b093937d378a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6344014
Auto-Submit: Peter Wen <wnwen@chromium.org>
Owners-Override: Peter Wen <wnwen@chromium.org>
Reviewed-by: Martin Kong <martinkong@google.com>
Commit-Queue: Peter Wen <wnwen@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1431732}
2025-03-12 13:47:09 -07:00
c77e08f332 Roll Chrome Mac Arm PGO Profile
Roll Chrome Mac Arm PGO profile from chrome-mac-arm-main-1741802349-e6961a8c244f11e8c9a1e5ab0c4b3234b0f370fc-d978d40415d40f96a628e89e24134924505c336e.profdata to chrome-mac-arm-main-1741809585-ddc162788a940ba3a926bd673c00a2572f2b53be-27da9af6772797acf18dfef51b954e33ff1bbb4b.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-mac-arm-chromium
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium main branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Cq-Include-Trybots: luci.chrome.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Merge-Approval-Bypass: Chrome autoroller
Change-Id: Iac583de52d88a3bd5a1918bd9cbee69f6e5160c1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6349743
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1431731}
2025-03-12 13:46:32 -07:00
54a764759e Fix uninitialized PRT in test
Bug: 402425762
Change-Id: I20288efe82dfc0a4f0151270d9614c970a820f54
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6347271
Commit-Queue: Aykut Bulut <aykutb@google.com>
Reviewed-by: Ryan Kalla <ryankalla@google.com>
Reviewed-by: Andrew Williams <awillia@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1431730}
2025-03-12 13:44:40 -07:00
4072eb195f [RWS] Update page info entrypoint a11y label
Bug: b:396463421
Change-Id: I974a7cca0e5a64f1adc2209065b7eac36b541eca
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6349158
Commit-Queue: Fiona Macintosh <fmacintosh@google.com>
Reviewed-by: Maggie Jennings <mjenn@google.com>
Auto-Submit: Fiona Macintosh <fmacintosh@google.com>
Commit-Queue: Maggie Jennings <mjenn@google.com>
Cr-Commit-Position: refs/heads/main@{#1431729}
2025-03-12 13:43:02 -07:00
426f4ac498 android: Ignore support_lib_boundary in stats
Since the target that defines these files in the org.chromium package
also define chromium_code=false, the annotator does not annotate them,
so we can ignore them for the time being as potential targets to
annotate.

Add various levels of verbosity and documentation printed at the end of
each run to make it easier to understand what the numbers mean.

R=martinkong@google.com

Bug: 389129271
Change-Id: I1f0fa8c102126f6d8d69ec18f4c18cdcaa5c2145
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6347918
Auto-Submit: Peter Wen <wnwen@chromium.org>
Commit-Queue: Martin Kong <martinkong@google.com>
Reviewed-by: Martin Kong <martinkong@google.com>
Cr-Commit-Position: refs/heads/main@{#1431728}
2025-03-12 13:39:40 -07:00
38787882df Add accessible title for Glic window
Bug: 392210875
Change-Id: I797d8800131a2ddb7d191a6f125c4feacaed4247
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6344554
Commit-Queue: Tzarial <zork@chromium.org>
Reviewed-by: Ian Vollick <vollick@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1431727}
2025-03-12 13:39:29 -07:00
f1b2f63787 Roll Chrome Android ARM64 PGO Profile
Roll Chrome Android ARM64 PGO profile from chrome-android64-main-1741798378-d63a3df9763ac82bf4d3f0dbbd70b09c5bd5cbab-9da988b396d1a8723637c732b45205b09360971b.profdata to chrome-android64-main-1741803135-f64a770ae719a081a697509246d2c2ead5ba0eeb-65a9b7556e9283325448e451a470b5abdaf7ff2d.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-android-arm64-chromium
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium main branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Tbr: pgo-profile-sheriffs@google.com
Merge-Approval-Bypass: Chrome autoroller
Change-Id: I4c58175d885d4239cbc526364143eb21cab3fd6e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6349882
Bot-Commit: 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/main@{#1431726}
2025-03-12 13:37:33 -07:00
84e3c2b112 Fix bug where send tab to self bubble was not appearing.
The SendTabToSelfToolbarIconController was previously only created when
retrieved for the first time, prior to the toolbar pinning clean up this
was not a problem since the SendTabToSelfToolbarIconView retrieved it in
its constructor. When the SendTabToSelfToolbarIconView was deleted the
controller was no longer being created, since it acts as the
BrowserListObserver and triggers the bubble/button to show this meant
that they were not being triggered to show. This cl forces the
controller to be created for all applicable browsers and adds a
regression test.

Bug: 402388541
Change-Id: Ic202a41dca0fa29e4cc9242e876f27d79759af39
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6345733
Reviewed-by: Victor Vianna <victorvianna@google.com>
Commit-Queue: Caroline Rising <corising@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1431725}
2025-03-12 13:37:26 -07:00
1d7d16a0c8 [Gardener] Set test expectations for failing webaudio/Oscillator tests
Bug: 402796552
Change-Id: I0ef12c4b6e7a08a5963498cd51176501c211bce2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6349756
Reviewed-by: Jian Li <jianli@chromium.org>
Auto-Submit: Zachary Tan <tanzachary@chromium.org>
Commit-Queue: Zachary Tan <tanzachary@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1431724}
2025-03-12 13:36:19 -07:00
15979fbb8b Roll src-internal from 2b644d8883a0 to 597191968d66 (1 revision)
2b644d8883..597191968d

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 chrome-browser-infra-team,jianli@google.com,tanzachary@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://issues.skia.org/issues/new?component=1389291&template=1850622

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome
Bug: None
Tbr: jianli@google.com,tanzachary@google.com
Change-Id: Id023a4e5135e8741d7fcb371860e7e684f9f037a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6349365
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Bot-Commit: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1431723}
2025-03-12 13:35:13 -07:00
5377db24d2 Remove and clean upDefault Browser Role Manager Feature flag
The feature has been default enabled for over a year.
Remove the feature flag and clean up the feature params

Change-Id: I5ec3241c405eb27259f0ceb9283382409d9473dc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6330636
Auto-Submit: Ella Ge <eirage@chromium.org>
Reviewed-by: Lijin Shen <lazzzis@google.com>
Commit-Queue: Lijin Shen <lazzzis@google.com>
Cr-Commit-Position: refs/heads/main@{#1431722}
2025-03-12 13:33:00 -07:00
6b48372681 media: Update max for MediaCodecStatus enum
The max wasn't updated.

Bug: 376720476
Change-Id: Id15be99cc200f8ae7b11bf352c0e555f900c2f59
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6343654
Auto-Submit: Vikram Pasupathy <vpasupathy@chromium.org>
Reviewed-by: Ted (Chromium) Meyer <tmathmeyer@chromium.org>
Commit-Queue: Ted (Chromium) Meyer <tmathmeyer@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1431721}
2025-03-12 13:28:46 -07:00
370dbf63eb Fix feature enabling on linux-oi-rel
When the bot was initially configured, "--enable-feature" was
incorrectly used when it should have been "--enable-features". This CL
fixes that. Since it's possible the bot won't stay green with this
change, temporarily disable its ability to close the tree.

Bug: 40259221
Change-Id: Ida766b469d92a624bdc53610f16f504bac2bbe37
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6347936
Commit-Queue: James Maclean <wjmaclean@chromium.org>
Reviewed-by: Ben Pastene <bpastene@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1431720}
2025-03-12 13:28:34 -07:00
3ec51267f5 Add about flag for kGlicDetached
Bug: 402233577
Change-Id: I4d89c5fbb69358cfecaf5b5294dfce220b4f1088
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6349836
Reviewed-by: Andrea Gomez <andreaxg@google.com>
Commit-Queue: Trevor Perrier <perrier@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1431719}
2025-03-12 13:26:07 -07:00
02682ddc48 [Desktop Android] Compile ExtensionApiTest on Desktop Android
Right now, there are two ExtensionApiTest implementations, which are
nearly identical. Compile the "main" ExtensionApiTest implementation on
Desktop Android.

One complication here is that the subclasses of ExtensionApiTest (i.e.,
individual test suites) may rely on functionality in
ExtensionBrowserTest, which is still unavailable in Android. Solve this
by having ExtensionApiTest inherit from ExtensionPlatformBrowserTest on
Desktop Android builds, and ExtensionBrowserTest on other builds. While
this does make the inheritance tree a little more complex, in practice,
this is what users on ExtensionPlatformApiTest are already doing (since
ExtensionApiTest inherits from ExtensionBrowserTest, while
ExtensionPlatformApiTest inherits from ExtensionPlatformBrowserTest).

After this inheritance change, modifying the rest of ExtensionApiTest
to compile is fairly straightforward, either compiling with no
changes or trivial modifications, or being cleanly separated by other
features (like platform apps). The one exception to this is the method
to open a URL, which has different implementations on desktop android
and other platforms. To accommodate this, introduce an
ExtensionBrowserTestPlatformDelegate, which can be responsible for
handling these so that we isolate the platform-specific code and avoid
adding lots of if-defs in the other test classes. In the future, this
can be used in ExtensionPlatformBrowserTest to clean it up a bit.

This CL paves the way for getting rid of DesktopAndroidExtensionApiTest.

Bug: 401522580
Change-Id: I9ff3d1deb9f5fdb0b09c65392d1928286fdbe791
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6335690
Reviewed-by: David Bertoni <dbertoni@chromium.org>
Commit-Queue: Devlin Cronin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1431718}
2025-03-12 13:17:45 -07:00
3906268e54 Extend safe_browsing histogram expiry
Extend SafeBrowsing.RT.Request.HadCookie expiration date for 6 months.

Fixed: 392616194
Change-Id: I26e7856b39bf255790a34b14d2ab7bfbf77164b1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6347270
Reviewed-by: Lily Chen <chlily@chromium.org>
Auto-Submit: Zack Han <zackhan@chromium.org>
Reviewed-by: thefrog <thefrog@chromium.org>
Commit-Queue: thefrog <thefrog@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1431717}
2025-03-12 13:17:02 -07:00
9b48bd18f6 [Frameworks roll] Roll to 736214002 piper revision
Change-Id: I8721275aba5fbc06421a64ba4700477e4aef42f5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6349277
Commit-Queue: Internal Frameworks Autoroller <bling-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Internal Frameworks Autoroller <bling-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1431716}
2025-03-12 13:14:48 -07:00
f120c8f7ba [Enhanced Events] Populate device_fqdn and network_name for URLF and deep scan requests.
Bug: 397738537
Change-Id: Idee1e8425de25a4ef6229f5f92082f8ab9b0038d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6310517
Reviewed-by: Dominique Fauteux-Chapleau <domfc@chromium.org>
Reviewed-by: Nancy Xiao <nancylanxiao@google.com>
Commit-Queue: Lina Ismail <ismaill@google.com>
Cr-Commit-Position: refs/heads/main@{#1431715}
2025-03-12 13:07:18 -07:00
5712b22242 [gpu] Remove SharedImageInterface::Flush
All callsites of SharedImageInterface::Flush have been removed since
the Flush now happens as a delayed post task when the client shared
image is destroyed.

This change removes SharedImageInterface::Flush and its associated
implementations.

Bug: 399387909
Change-Id: Iffc41457a39cfef13de6e92efe7e7e327bea63d3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6348176
Commit-Queue: Saifuddin Hitawala <hitawala@chromium.org>
Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1431714}
2025-03-12 13:06:49 -07:00
f7e1483a70 [Collaboration] Android entreprise can change dynamically
Fix android code to check flag on construction rather than on init with
profile.

Bug: 402144079
Change-Id: I1cb776516662d510f2d58ebb20fb0890f7d81225
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6341450
Reviewed-by: Siddhartha S <ssid@chromium.org>
Commit-Queue: Hailey Wang <haileywang@google.com>
Reviewed-by: Sky Malice <skym@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1431713}
2025-03-12 13:06:01 -07:00