chromium
Legend: | Passed | Failed | Running | Exception |
[geo] Rename CanBeAutoRevoked to IsAnyPermissionAllowed
The function will be useful for pageinfo as well.
Bug: 418938557
Change-Id: Ic1a3784f396a52eb4470c6952871f8920f4217b8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781045
Auto-Submit: Christian Dullweber <dullweber@chromium.org>
Reviewed-by: Nicola Tommasi <tommasin@chromium.org>
Commit-Queue: Nicola Tommasi <tommasin@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491053}
[Clank][widget] Adjust RichRadioButton dimensions to match the mocks
This CL just fixes some RichRadioButton padding / margins to match the
mocks.
Mocks: https://screenshot.googleplex.com/6KCN76cdddMHctV
Bug: 432411749
Change-Id: I1e71ccc96680510dc0f8bf6cfc2e9e70324bd127
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6765323
Commit-Queue: Nicola Tommasi <tommasin@chromium.org>
Reviewed-by: Wenyu Fu <wenyufu@chromium.org>
Reviewed-by: Christian Dullweber <dullweber@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491052}
Roll Updater chrome_win_x86 from 2@132.0.6833.0 to 2@140.0.7273.0
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/updater-chrome-win-x86-chromium
Please CC omaha-reviews@google.com,omaha-team@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in Chromium: https://g-issues.chromium.org/issues/new?component=1516667&template=0
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:win-updater-try-builder-rel;luci.chromium.try:linux-updater-try-builder-rel;luci.chromium.try:mac-updater-try-builder-rel;luci.chromium.try:win-updater-try-builder-rel
Tbr: omaha-reviews@google.com
Change-Id: I1e029fc358e08eda0aac858c1558e9a806f79586
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781803
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@{#1491051}
Roll Updater chrome_win_arm64 from 2@132.0.6833.0 to 2@140.0.7273.0
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/updater-chrome-win-arm64-chromium
Please CC omaha-reviews@google.com,omaha-team@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in Chromium: https://g-issues.chromium.org/issues/new?component=1516667&template=0
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:win-updater-try-builder-rel;luci.chromium.try:linux-updater-try-builder-rel;luci.chromium.try:mac-updater-try-builder-rel;luci.chromium.try:win-updater-try-builder-rel
Tbr: omaha-reviews@google.com
Change-Id: Id36da3937786eb146aefafcd04367f2f00681f74
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781557
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@{#1491050}
Roll Updater chrome_win_x86_64 from 2@132.0.6833.0 to 2@140.0.7273.0
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/updater-chrome-win-x86-64-chromium
Please CC omaha-reviews@google.com,omaha-team@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in Chromium: https://g-issues.chromium.org/issues/new?component=1516667&template=0
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:win-updater-try-builder-rel;luci.chromium.try:linux-updater-try-builder-rel;luci.chromium.try:mac-updater-try-builder-rel;luci.chromium.try:win-updater-try-builder-rel
Tbr: omaha-reviews@google.com
Change-Id: Ife07609acc8a3f20fea3140c16571dff79610730
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781802
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@{#1491049}
Roll Updater chrome_mac_universal from 2@119.0.5999.0 to 2@140.0.7273.0
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/updater-chrome-mac-universal-chromium
Please CC omaha-reviews@google.com,omaha-team@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in Chromium: https://g-issues.chromium.org/issues/new?component=1516667&template=0
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:win-updater-try-builder-rel;luci.chromium.try:linux-updater-try-builder-rel;luci.chromium.try:mac-updater-try-builder-rel;luci.chromium.try:win-updater-try-builder-rel
Tbr: omaha-reviews@google.com
Change-Id: Iaf32113870570346294841021fd2e6ea57a6b148
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781800
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@{#1491048}
Roll PDFium from 20159328af8c to 7f80ad7406e3 (3 revisions)
https://pdfium.googlesource.com/pdfium.git/+log/20159328af8c..7f80ad7406e3
2025-07-22 thestig@chromium.org Rename "pDoc" instances to "doc" in //fxjs and //testing
2025-07-22 clemensb@chromium.org Avoid calls to deprecated GetIsolate methods
2025-07-22 thestig@chromium.org Rename "pDoc" instances to "doc" or "document" in //fpdfsdk and //xfa
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pdfium-autoroll
Please CC andyphan@google.com,dhoss@chromium.org,thestig@chromium.org on the revert to ensure that a human
is aware of the problem.
To file a bug in PDFium: https://bugs.chromium.org/p/pdfium/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
Bug: chromium:42271580,chromium:427885584
Tbr: andyphan@google.com
Change-Id: Id9898aa6c277d938cf316de6f1dd5ff66612e9fd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781807
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@{#1491047}
[Read aloud] Fix highlight granularity enum for read aloud.
This is a similar fix to the one put forward in
https://chromium-review.googlesource.com/c/chromium/src/+/6771446
but we realized that the implementation was already in place and the
enum was the only issue.
NO_IFTTT=first creation of this clause.
Bug: 406018562
Change-Id: I517a98744f1ad6493a1de43a3fdadcea112796ae
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6775264
Commit-Queue: Andres Munoz Medina <ammedina@google.com>
Reviewed-by: Luc Nguyen <lucnguyen@google.com>
Reviewed-by: Lauren Winston <lwinston@google.com>
Reviewed-by: Kristi Saney <kristislee@google.com>
Cr-Commit-Position: refs/heads/main@{#1491046}
[ntp-composebox] Make file upload tooltip more specific.
Replaces "Upload a file" with "Upload a PDF".
This is not translatable (like a decent amount of other composebox
strings), because it will only be used by en-US for now.
screen/6QxBkBwRowAkD6W
Change-Id: I12d952a2fc777ff76d8ba02f40897ec5eb86df45
Bug: 433757722
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6777752
Commit-Queue: Paul Adedeji <pauladedeji@google.com>
Reviewed-by: Roman Arora <romanarora@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491045}
Make Cloud host session reauthorization optional
Unlike Corp hosts, some Cloud host admins may not want to pay the
resource costs of frequent reauthorization. In that case, they can
choose a relaxed reauthz schedule or disable it completely.
Change-Id: Ie2200939cf51866ad82340a2dbc208c277e83381
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781005
Commit-Queue: Joe Downing <joedow@chromium.org>
Reviewed-by: Yuwei Huang <yuweih@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491044}
[CLAMS] Add an initial implementation of OnDeviceModel backend on Android
This change adds initial Java glue code for handling the on device model
service using AiCore on Android. It includes a default impl that will
return hardcoded results if the Java implementation is not found.
Low-Coverage-Reason: Java code coverage from C++ tests is not counted https://crbug.com/40269621
Bug: 425408635
Change-Id: I333ac9fa842060852122a0bf680e5441b6f12dbe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6767761
Reviewed-by: Colin Blundell <blundell@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Xinghui Lu <xinghuilu@chromium.org>
Reviewed-by: Clark DuVall <cduvall@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491043}
Map session ids to TabInterface handles
This updates TabInterface to derive from SupportsTabHandles (recently
added in http://crrev.com/c/6728576) instead of the default
SupportsHandles<TabInterface>, and allowing it to map its TabHandle to
its session ID.
The TabModel and TabAndroid implementations are updated to set this
mapping, with unit tests added.
Bug: 428721699
Change-Id: I4c3ae12f0c954630420cd5ec54994d4cbadbca08
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6756981
Commit-Queue: Kaan Alsan <alsan@chromium.org>
Reviewed-by: Dana Fried <dfried@chromium.org>
Reviewed-by: Calder Kitagawa <ckitagawa@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491042}
Roll Perfetto Trace Processor Linux from 0bb55df38193 to dc3cfc940d5a
https://android.googlesource.com/platform/external/perfetto.git/+log/0bb55df38193..dc3cfc940d5a
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-linux-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: Ic7acbbb7c0fe8217f40f44d73c3d1da68daedce6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781008
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@{#1491041}
Reland "[fuchsia] Use deny_bad_handles policy in components"
This is a reland of commit 8d976743d60fb286874d60f4b2c1d9b2574f7285
now that the platform issue has been resolved, and images rolled.
Original change's description:
> [fuchsia] Use deny_bad_handles policy in components
>
> deny_bad_handles causes an exception to be raised if the
> component program attempts to use a bad handle, rather
> than simply failing the call.
>
> Bug: fuchsia:296292725
> Cq-Include-Trybots: luci.chrome.try:fuchsia-fyi-sherlock-qemu
> Change-Id: I7567d9b4d605a125f3d0b91762e83f883faa7eae
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6662725
> Reviewed-by: David Dorwin <ddorwin@chromium.org>
> Auto-Submit: Wez <wez@chromium.org>
> Commit-Queue: Wez <wez@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1482121}
Bug: fuchsia:296292725
Cq-Include-Trybots: luci.chrome.try:fuchsia-smoke-sherlock
Change-Id: I9eeed96d4eed966d7965e7b80de6264d2fce0f83
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6780283
Auto-Submit: Wez <wez@chromium.org>
Reviewed-by: David Dorwin <ddorwin@chromium.org>
Reviewed-by: Zijie He <zijiehe@google.com>
Commit-Queue: Zijie He <zijiehe@google.com>
Cr-Commit-Position: refs/heads/main@{#1491040}
Roll optimization-guide from add14b26475a to 23d2ce9848ac
https://chrome-internal.googlesource.com/chrome/components/optimization_guide.git/+log/add14b26475a..23d2ce9848ac
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://skia-autoroll.corp.goog/r/optimization-guide-chromium
Please CC chrome-ai-ondevice-eng-core@google.com,chrome-ai-ondevice-eng@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: I2d82e805d4995f47b7013b0eeef3112850edf2ae
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781633
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@{#1491039}
Implement non milestone update toast
Implement non milestone update toast under a feature flag. The
localization string will be updated in a follow up CL.
Bug: 357930023
Change-Id: I3d3020bd0957488784072cf8ed4c5268f7d4ef49
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6758178
Reviewed-by: Alison Gale <agale@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Commit-Queue: Yuheng Huang <yuhengh@chromium.org>
Reviewed-by: Nicolas Ouellet-Payeur <nicolaso@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491038}
Glic actor: Notify client of actor task state changes
We notify the client when the state of an actor task changes.
The glic API exposes the state as an observable.
See doc in the associated bug for details.
Bug: 430643846
Change-Id: I9b4dbf415be17b91a0294010dd993e7ab20bce92
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6771368
Auto-Submit: Kevin McNee <mcnee@chromium.org>
Reviewed-by: Dan Harrington <harringtond@chromium.org>
Commit-Queue: Kevin McNee <mcnee@chromium.org>
Commit-Queue: Dan Harrington <harringtond@chromium.org>
Reviewed-by: Erik Chen <erikchen@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491037}
Roll src-internal from f3a8e2caab00 to 286dd0eb8ac6 (3 revisions)
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/f3a8e2caab00..286dd0eb8ac6
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 birnie@google.com,chrome-browser-infra-team,liviutinta@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: chromium:390426442
Tbr: birnie@google.com,liviutinta@google.com
Change-Id: Ia04b729731f54a0806cd98b3bb0aba7ab3f09614
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781820
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@{#1491036}
Fix source email for clipboard reports
The code was mistakenly attaching the same active user as the paste
destination active user.
Change-Id: I783bc2bdd9bc2071508fd479bedbbceff914b8f0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6777796
Auto-Submit: Dominique Fauteux-Chapleau <domfc@chromium.org>
Reviewed-by: Nancy Xiao <nancylanxiao@google.com>
Commit-Queue: Dominique Fauteux-Chapleau <domfc@chromium.org>
Commit-Queue: Nancy Xiao <nancylanxiao@google.com>
Cr-Commit-Position: refs/heads/main@{#1491035}
NTP Promos: Add completed promo ordering to order policy
A follow-on CL will plug this into the controller.
Bug: 428035923
Change-Id: I3415b194eb4d12028e398d49f6a2b7c4045ac0b2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6757556
Commit-Queue: Christopher Grant <cjgrant@chromium.org>
Reviewed-by: Dana Fried <dfried@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491034}
[MVT Customization] Make "divider gap" same as "tile gap".
MVTs consist of Custom Tiles (CTs) and Top Sites Tiles (TSTs). The
divider is found between the last CT and the first TST. Let "tile gap"
be the common icon distance between adjacent CTs and adjacent TSTs. Let
"divider gap" be the icon distance between the last CT and the first
TST (across the divider).
"Tile gap" arises from each tile's internal spacing and assigned
"internal margin", which is applied (as start margin) to all but the
first tile in TilesLinearLayout.setIntervalMargins().
For uniformity, the divider was given the same "internal margin". We
then chose divider width (R.dimen.tile_view_divider_width = 8bp) to fit
the UI mock. As a result, the "divider gap" is larger than "tile gap" --
but this looks great when the divider is always present.
In crrev.com/c/6774848 we hide the divider hidden by default, and only
show it briefly with animation (adjusts alpha) on CT update. But without
the divider, the "divider gap" is noticeably bigger than "tile gap",
especially in landscape mode!
This CL fixes the issue by making "divider gap" same as "tile gap". The
trade-off is that when the divider is shown it looks a bit cramped --
but this is fine since the divider is transient anyway.
Details:
* TileLinearLayout: Make updateView{Start,End}Margin() protected.
* MostVisitedTilesLayout:
* Cache `mTileViewDividerWidth`.
* The divider width is now arbitrary -- but we keep it anyway.
* Store `mDividerIndex` along with `mTileViewDividerWidth`.
* Override setIntervalMargins(): If the divider is present, calculate
adjusted margin, and assign it as the start margin to the divider
and its next sibling.
Bug: 433272602, 388782412
Change-Id: I1d00be64b20d0b9f6a4f857d7b439fa615b28d71
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6780677
Reviewed-by: Calder Kitagawa <ckitagawa@chromium.org>
Commit-Queue: Samuel Huang <huangs@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491033}
Remove file-wide unsafe buffers pragma from chrome/
Automated CL from scripts in tools/clang/unsafe_pragma_rewriter.
Bug: 409340989
Change-Id: I554139daf2b8fa6d1fe159abd16a9d079eb33671
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6778035
Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Tom Sepez <tsepez@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491032}
[lensoverlay] Fix focus behavior when showing and hiding overlay.
This change ensures that, when the overlay is shown, focus is taken by
the overlay view prior to the tab contents web view being disabled, and
when the overlay is hidden, focus is taken by the tab contents web
view prior to the overlay view being disabled. This avoids focus being
moved elsewhere in between. On Mac, the tab strip was taking focus,
causing the hovercard of the first tab in the strip to appear
momentarily when the overlay was invoked from the homework action chip,
or when switching between the overlay tab and other tabs.
Bug: 432499615
Change-Id: Id744785499500cecfcfb1549f71a79c902b6a416
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6779016
Reviewed-by: Duncan Mercer <mercerd@google.com>
Reviewed-by: Juan Mojica <juanmojica@google.com>
Commit-Queue: Bryan Nguyen <nguyenbryan@google.com>
Cr-Commit-Position: refs/heads/main@{#1491031}
[Desktop Android] Port tabs zoom-related APIs
Port the zoom-related APIs on the tabs API to the experimental desktop
android platform. This includes:
* tabs.setZoom()
* tabs.getZoom()
* tabs.setZoomSettings()
* tabs.getZoomSettings()
No behavior changes are expected on classic desktop platforms.
Bug: 371432155
Change-Id: I4d4b0231536657e4b982d4f145b2c9a08af360c6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6777950
Reviewed-by: James Cook <jamescook@chromium.org>
Auto-Submit: Devlin Cronin <rdevlin.cronin@chromium.org>
Commit-Queue: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491030}
Revert "[ozone/wayland] Fix dangling pointer in `WaylandCursor`"
This reverts commit 827a0cad64063079cf97d3aabfbdd9dbe620eeec.
Reason for revert: Causing many Linux MSAN test failures: https://ci.chromium.org/ui/p/chromium/builders/ci/Linux%20MSan%20Tests/57522/overview
Bug: 324294360
Original change's description:
> [ozone/wayland] Fix dangling pointer in `WaylandCursor`
>
> Declare `seat_` before `cursor_` to prevent a dangling pointer issue.
> This issue happens because the `cursor_` member holds a pointer to
> `seat_->pointer_`, so `seat_` must be declared first to ensure it will
> be destroyed last.
>
> Reset `cursor_` in WaylandPointer's destructor to prevent dangling
> references.
>
> Bug: 324294360
> Change-Id: I0801545c62ad121349e05a4a39cbad0fc2105c20
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6757952
> Reviewed-by: Orko Garai <orko@igalia.com>
> Reviewed-by: Max Ihlenfeldt <max@igalia.com>
> Commit-Queue: AbdAlRahman Gad <agad@igalia.com>
> Cr-Commit-Position: refs/heads/main@{#1490739}
Bug: 324294360
Change-Id: I73993212ecd6eb699fd0aba32eb36b12cc94feb8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6778487
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Reviewed-by: Nick Birnie <birnie@google.com>
Owners-Override: Nick Birnie <birnie@google.com>
Commit-Queue: Nick Birnie <birnie@google.com>
Cr-Commit-Position: refs/heads/main@{#1491029}
Roll V8 from 65e1f08f4b8f to 0746b1dd75ff (5 revisions)
https://chromium.googlesource.com/v8/v8.git/+log/65e1f08f4b8f..0746b1dd75ff
2025-07-23 v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Version 14.0.297
2025-07-23 rezvan@chromium.org [base64] Fix test262 failure
2025-07-23 etiennep@chromium.org [GC] Move consumed memory metrics to StartCycle
2025-07-23 victorgomes@chromium.org [test] --jit-fuzzing now implies lazy
2025-07-23 jkummerow@chromium.org [wasm] Optimize handling of elem segments
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;luci.chrome.try:linux-perf-trigger
Change-Id: I972ffe40d14c5ce901a8822c0adaaaed53f99160
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781549
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@{#1491028}
PaymentsWindow(Bridge|Coordinator) Skeleton
This CL adds the skeleton classes for PaymentsWindowBridge and
PaymentsWindowCoordinator, which will be the classes used to connect to
the native C++ code and coordinate payments window flows.
Bug: 430575808
Change-Id: I5f3602f0360b95ef130e1d8920027d86e05f1bfb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6759110
Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
Commit-Queue: Viplav Kadam <viplavkadam@google.com>
Cr-Commit-Position: refs/heads/main@{#1491027}
[4/4] Improve WPT Drag and Drop images/ tests (023 -> 024)
This CL cleans up tests 23 and 24 in the WPT drag and drop images/
directory.
The tests were verifying that the <object> received an ondrop event, but
did not verify that the html page contained within the object received
the ondrop event. I fixed the tests, but since the behavior is not
working, I had to disable them.
Bug: 40216874, 426054999
Change-Id: I890a3146dd9d52e952b17075d9636b52f8fa4c06
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6664881
Reviewed-by: Mustaq Ahmed <mustaq@chromium.org>
Commit-Queue: Gaston Rodriguez <gastonr@microsoft.com>
Reviewed-by: Olga Gerchikov <gerchiko@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#1491026}
[ios] Disable disableAccountTests tests
Bug: 433726717
Change-Id: Id009d985908641a69195386ec1f2ea853ede1bc2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781371
Auto-Submit: Chris Lu <thegreenfrog@chromium.org>
Owners-Override: Chris Lu <thegreenfrog@chromium.org>
Reviewed-by: Ginny Huang <ginnyhuang@chromium.org>
Commit-Queue: Chris Lu <thegreenfrog@chromium.org>
Reviewed-by: Robbie Gibson <rkgibson@google.com>
Commit-Queue: Robbie Gibson <rkgibson@google.com>
Cr-Commit-Position: refs/heads/main@{#1491025}
Disable Fetch.getResponseBody test on Win11-arm64
Bug: 433756870
Change-Id: I1455c15eaace80f0d8e1baca81bc461877c8a2ea
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781369
Reviewed-by: Liviu Tinta <liviutinta@chromium.org>
Commit-Queue: Liviu Tinta <liviutinta@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491024}
Manually NullMark media files
Bug: 389129271
Change-Id: I956b015dd53c455e7a511100e09f6d9a12728df4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6777883
Reviewed-by: Thomas Guilbert <tguilbert@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Commit-Queue: Jenna Himawan <jhimawan@google.com>
Reviewed-by: Calder Kitagawa <ckitagawa@chromium.org>
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491023}
Enable LocalIpAddressInEvents experiment by default at ToT.
Bug: 408221281
Change-Id: Iac7c1179b4481635292bda11e8801505d3cccb9e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6700478
Reviewed-by: Xinghui Lu <xinghuilu@chromium.org>
Commit-Queue: Lina Ismail <ismaill@google.com>
Cr-Commit-Position: refs/heads/main@{#1491022}
[Extensions Metrics] Remove no-longer-needed histograms
Remove the following histograms, which are no longer needed:
* Extensions.ExtensionsWithPageActions
* PageActionController.Extensions.ExtensionsWithPageActions
* Extensions.LoadUserScript2
Bug: 402121109, 420443311
Change-Id: Iae12dfa0cca3f2dbed80bceafef9d37e8ffbeb46
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6769509
Reviewed-by: Justin Lulejian <jlulejian@chromium.org>
Commit-Queue: Devlin Cronin <rdevlin.cronin@chromium.org>
Reviewed-by: Charlie Harrison <csharrison@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491021}
Add GlicMediaLinkHelpers
Prototype extensible media link helpers.
Bug: 432546794, 431838728
Change-Id: Ia75d2c986e781ab1d6e6173af2f6beac17e6c7d8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6767474
Reviewed-by: Justin DeWitt <dewittj@chromium.org>
Commit-Queue: Frank Liberato <liberato@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491020}
[ios] Disable WebStateTests on devices
Bug: 433740395
Change-Id: I4f6a23f7afc1c86fd3da54b2d8149f54e2557360
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6780035
Auto-Submit: Chris Lu <thegreenfrog@chromium.org>
Owners-Override: Chris Lu <thegreenfrog@chromium.org>
Commit-Queue: Robbie Gibson <rkgibson@google.com>
Reviewed-by: Robbie Gibson <rkgibson@google.com>
Cr-Commit-Position: refs/heads/main@{#1491019}
Fix touch drag and drop incorrect coordinates on secondary monitors
On Windows systems with multiple monitors, touch drag-and-drop actions
on a secondary display do not correctly follow the user's finger. The
dragged element is positioned at the edge of the primary monitor instead
of the intended location.
This issue occurs because ui::SendMouseEvent only considers coordinates
within the primary monitor, ignoring the full virtual desktop area. To
resolve this, the fix adds the MOUSEEVENTF_VIRTUALDESK flag to mouse
events and updates the coordinate calculations to use the virtual
desktop metrics. This ensures that drag-and-drop actions work correctly
across all monitors, and the element follows the user's touch accurately
on any display.
test coverage originally, and hard to write test for these scenarios currently.
Low-Coverage-Reason: HARD_TO_TEST The modified methods don't have
Bug: 417245720
Change-Id: I0754418e23ae4ce24ad134fb3b48c9cc21f65577
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6774649
Reviewed-by: Keren Zhu <kerenzhu@chromium.org>
Commit-Queue: Eain Chen <eainchen@microsoft.com>
Reviewed-by: Gaston Rodriguez <gastonr@microsoft.com>
Reviewed-by: David Bienvenu <davidbienvenu@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491018}
[base] Add compound assignment operators to ByteCount
Bug: 429140103
Change-Id: I2f02856d93830cebe8ab0e85c2581e1c74fd4f91
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6776989
Reviewed-by: Gabriel Charette <gab@chromium.org>
Commit-Queue: Thiabaud Engelbrecht <thiabaud@google.com>
Cr-Commit-Position: refs/heads/main@{#1491017}
[declutter] Update the thumbnail fetcher refactor to use a null check
Update the thumbnail fetcher refactor in TabListMediator to null check
a tab if the status changes between update calls for any reason.
Bug: 433585805
Change-Id: I6d839cc6e37f5a2ff179d6e94a0057237bb5da25
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6776987
Reviewed-by: Calder Kitagawa <ckitagawa@chromium.org>
Commit-Queue: Brandon Fong <bjfong@google.com>
Cr-Commit-Position: refs/heads/main@{#1491016}
Clean-up Android P- code in //ui/android/java
Change-Id: I2eb629f821188fb23ad6fa44e3a2f17ba6e14361
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6777894
Reviewed-by: Wenyu Fu <wenyufu@chromium.org>
Commit-Queue: Theresa Sullivan <twellington@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491015}
Roll JetStream main from e30a452018bb to df197ef3b188 (1 revision)
https://chromium.googlesource.com/external/github.com/WebKit/JetStream.git/+log/e30a452018bb..df197ef3b188
2025-07-23 danleh@users.noreply.github.com Merge pull request #93 from danleh/cleanup-loadInternal
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/jetstream-main-chromium
Please CC manoskouk@google.com,mliedtke@google.com,v8-waterfall-gardeners@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
Bug: None
Tbr: manoskouk@google.com,mliedtke@google.com
Change-Id: Id4274e23e23a8abd968a91e4d43525b4b4680eb0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781598
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@{#1491014}
Use a loop in ChromeExtensionsRendererAPIProvider::PopulateSourceMap()
Rewrite the method to use a loop, which will slightly decrease the
amount of generated code. Gemini did this mechanically, with some human
touchups to better match the coding style.
Change-Id: Iaebc106dc67abec1a379368b9a7f6e8e30245a53
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6780689
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491013}
[ntp-composebox] Set media type for file upload requests
Bug: 432755529
Change-Id: I146303e95076385f15f1c914044b5929d0e179e6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6774648
Commit-Queue: Jason Hu <hujasonx@google.com>
Reviewed-by: Nihar Majmudar <niharm@google.com>
Cr-Commit-Position: refs/heads/main@{#1491012}
Create initial impl for ChromeAndroidTaskTracker and ChromeAndroidTask
This CL is large, but a large portion is documentation and tests.
Changes:
(1) Add and implement APIs for tracking Tasks/Activities:
* ChromeAndroidTaskTracker:
```
obtainTask(ActivityWindowAndroid);
get(int taskId);
remove(int taskId);
```
* ChromeAndroidTask:
```
getId();
{set|get|clear}ActivityWindowAndroid();
destroy();
isDestroyed();
```
(2) Create Robolectric tests for (1).
Bug: 431289118
Change-Id: Ic7ffdccc883c0516cee6d8218d3d33294d4f85a2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6733293
Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Commit-Queue: Linyu He <linyuh@google.com>
Cr-Commit-Position: refs/heads/main@{#1491011}
[Benefits][Clank] Enable kAutofillEnableCardBenefitsForAmericanExpress
This CL enables kAutofillEnableCardBenefitsForAmericanExpress by
default for the clank launch.
Launchcal Approval:
https://launch.corp.google.com/launch/4339204/approver/14628
Autofill Feature Sync Approval:
https://docs.google.com/document/d/1dDmgNDRoEv3omInLwWVeznJKveei3922XAOL2HihgfE/edit?tab=t.0#bookmark=id.syep3zzgigih
Bug: 374383781
Change-Id: I403169e3a0c75afab33f47c2c88ff78526a0ed27
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6701396
Reviewed-by: Olivia Saul <osaul@google.com>
Commit-Queue: Viplav Kadam <viplavkadam@google.com>
Cr-Commit-Position: refs/heads/main@{#1491010}
[ios] Make CloudProfileReportingEnabled future_on ios
Also add the policy handler, and add a Finch flag to gate the feature.
This CL contains no functional changes.
Bug: b/385175028
Change-Id: Idf819959545a733ca64ba2cca4a4a8cddc01ebd3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6779160
Reviewed-by: Guillaume Jenkins <gujen@google.com>
Commit-Queue: Nicolas Ouellet-Payeur <nicolaso@chromium.org>
Reviewed-by: Owen Min <zmin@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491009}
Run Nullaway scripts on media files
Bug: 389129271
Change-Id: Ieb4578120c4192dbc9316f0d2e23d059e3d8ef6f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6777882
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Commit-Queue: Jenna Himawan <jhimawan@google.com>
Cr-Commit-Position: refs/heads/main@{#1491008}
Roll Chrome Android ARM64 PGO Profile
Roll Chrome Android ARM64 PGO profile from chrome-android64-main-1753282773-b3669ade989cd0c0b536a4a68c5d32f3fb4ec178-32093f0b1887f58ac9849a01921abe9ebdd6e770.profdata to chrome-android64-main-1753285702-e2a307bfc5d4a42e12e4287ca36afa3691538aa5-808f006925c1f83ebc9f3cb9330d3f90d9e7c7fb.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: Id573e1091d6f15070562fed77400153893e319aa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781551
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@{#1491007}
Roll Perfetto Trace Processor Linux from b5d1992fb472 to 0bb55df38193
https://android.googlesource.com/platform/external/perfetto.git/+log/b5d1992fb472..0bb55df38193
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-linux-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: Iedaf849f291e8785a922fba3e5b837ffd4092f93
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781473
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@{#1491006}
Add bruschetta availability check to ChromeFeaturesService
Much like with crostini and pluginVM, we are sometimes interested in
querying if bruschetta is available. Make a new endpoint available.
The logic here is effectively the same as
https://source.chromium.org/chromium/chromium/src/+/main:chrome/browser/ui/webui/ash/settings/pages/crostini/crostini_section.cc;l=255;drc=d0260a368e65b2be56d179d21fab90976fd494b8,
except we don't care if bruschetta has been installed.
This will require the creation of the method name in cros_system_api as
a dependency roll as well.
Bug: b:432480112
Change-Id: I1c6c8f95afd442ed8a58ea9e0685735785d566a4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6765737
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Commit-Queue: maciek swiech <drmasquatch@google.com>
Reviewed-by: Junichi Uekawa <uekawa@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491005}
Roll Chrome Mac Arm PGO Profile
Roll Chrome Mac Arm PGO profile from chrome-mac-arm-main-1753278920-8f7a45c16f642b5ff268abcd2f7ef05b2ca6b85b-2b36f7981d58d83c5b1a9317d9237539ee1fe97f.profdata to chrome-mac-arm-main-1753285702-0231b0c364c39b2d78e2588f821114ef255c0b73-808f006925c1f83ebc9f3cb9330d3f90d9e7c7fb.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: I9929a835f4f76de63948167a48db1d5cfc04c866
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781688
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@{#1491004}