chromium
| Legend: | Passed | Failed | Running | Exception |
Re-enable held.tentative.https.html WPT
The test is automatically added to expectations by import cl
(https://chromium-review.googlesource.com/c/chromium/src/+/6723156),
but this is not needed. It seems the update on test expected file is
added at the same day, which made the auto bot confused.
(https://chromium-review.googlesource.com/c/chromium/src/+/6713496)
Removing held.tentative.https.html from TestExpectations.
Bug: 431034520
Cq-Include-Trybots: luci.chromium.try:linux-blink-rel
Change-Id: Idfc38634c661cc2f3e1ca6a9f48632c69663eaba
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6780760
Auto-Submit: Eriko Kurimoto <elkurin@chromium.org>
Commit-Queue: Eriko Kurimoto <elkurin@chromium.org>
Reviewed-by: Mingyu Lei <leimy@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491234}
[DevTools] Register new badge for DevTools Ai File Assistance
Doc: go/devtools-new-badges
Bug: 427371633
Change-Id: Ib60980d4197950e132f239dbb27468ac7588f826
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6780580
Reviewed-by: Dana Fried <dfried@chromium.org>
Commit-Queue: Kim-Anh Tran <kimanh@chromium.org>
Reviewed-by: Wolfgang Beyer <wolfi@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491233}
Automated Commit: LKGM 16359.0.0-1070472 for chromeos.
CrOS Changes (16359.0.0-1070466 -> 16359.0.0-1070472):
- External: http://go/cros-changes/78184..78190?ext=true
- Internal: http://go/cros-changes/111872..111878
Uploaded by https://ci.chromium.org/b/8708539091012783393
CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-betty-chrome
CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-brya-chrome
CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-jacuzzi-chrome
CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-reven-chrome
CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-volteer-chrome
CQ_INCLUDE_TRYBOTS=luci.chromium.try:chromeos-octopus-rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:chromeos-jacuzzi-rel
CrOS-LKGM: 16359.0.0-1070472
Merge-Approval-Bypass: Automated LKGM update
Cr-Original-Build-Id: 8708539091012783393
CrOS-External-Manifest-Position: 78190
CrOS-Internal-Manifest-Position: 111878
Change-Id: I1d344f4b9f0c46c83ef8f68f67b8e4ed99572deb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782279
Commit-Queue: ChromeOS Prod (Robot) <chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com>
Bot-Commit: ChromeOS Prod (Robot) <chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1491232}
Roll Chrome Android ARM64 PGO Profile
Roll Chrome Android ARM64 PGO profile from chrome-android64-main-1753321021-f3a0a1a87c86255b70c55837442535504c6fb4b7-53f756a550388a4308378ce3b24df0593abf62d3.profdata to chrome-android64-main-1753324191-946ce75bfc0f44d02de1ebab81b2a8335985076f-ed097db5805c04ff8d5593196598d8db0293a825.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: Icb009f1a65dda00e79012d642dc1ee0b1a78e4ff
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782558
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@{#1491231}
Clean up unnecessary image_decoder dependency
This CL removes the chrome/browser/image_decoder dependency from:
- chrome/browser/ui/ash/shelf
- chrome/browser/ash/crosapi
Bug: b:428654878
Change-Id: I7bec450272cae4609c675b96476eff952efcb155
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6780425
Reviewed-by: Hidehiko Abe <hidehiko@chromium.org>
Commit-Queue: Jun Ishiguro <junis@google.com>
Cr-Commit-Position: refs/heads/main@{#1491230}
Roll gn from 85f62c164c82 to 05e031634869
https://gn.googlesource.com/gn.git/+log/85f62c164c82..05e031634869
2025-07-24 thestig@chromium.org Shorten targets from //path/to/foo:foo to //path/to/foo
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/gn-chromium-autoroll
Please CC dpranke@chromium.org,dpranke@google.com,thakis@chromium.org,tikuta@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: dpranke@chromium.org,thakis@chromium.org,tikuta@google.com
Change-Id: Ie75e11f8e712066cd8d30e249ce2ba31d58b5dce
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6780697
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@{#1491229}
Roll compiler-rt from f11321e08af0 to e2bc292b5860 (2 revisions)
https://chromium.googlesource.com/external/github.com/llvm/llvm-project/compiler-rt.git/+log/f11321e08af0..e2bc292b5860
2025-07-23 bblueconway@gmail.com [ASan][Darwin][GCD] Add interceptor for dispatch_apply (#149238)
2025-07-23 Jake.egan@ibm.com [sanitizer_common][nfc] Rename `tid_t` to avoid conflicting declarations (#149011)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/compiler-rt-chromium
Please CC aeubanks@google.com,lexan@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: aeubanks@google.com
Change-Id: I50783568ec8cea0a270af0177c7528fbeabe8e9b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782381
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@{#1491228}
Remove requirement for context sharing enabled in pinned tabs cause it is broken
Bug: 433154265
Change-Id: I525b779c1ddf56f22ae7541d588d1f7095f1357d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782100
Reviewed-by: Michael Crouse <mcrouse@chromium.org>
Commit-Queue: Sophie Chang <sophiechang@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491227}
Move wtf/wtf_size_t.h to "blink" namespace
This CL has no behavior changes.
Bug: 422768753
Change-Id: Ied36b5e69eba9af71f721a968b6a9e528f764da3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6778748
Auto-Submit: Kent Tamura <tkent@chromium.org>
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491226}
Disable "UseOriginalDomOffsetsForOffsetMap" flag for production
Bug: 430508617
Change-Id: I937cd78228853ffd9f64b125eb07b63af156c5f0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6779665
Reviewed-by: Koji Ishii <kojii@chromium.org>
Auto-Submit: Kent Tamura <tkent@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491225}
Roll Chrome Android ARM64 PGO Profile
Roll Chrome Android ARM64 PGO profile from chrome-android64-main-1753316103-aba96dd5a3d6f9357486a4c909c3e2d4a07dacbe-f0b2e763b0287bb864a26296f4645584053d65c8.profdata to chrome-android64-main-1753321021-f3a0a1a87c86255b70c55837442535504c6fb4b7-53f756a550388a4308378ce3b24df0593abf62d3.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: Ieea074c23196b3365bf88767e1bb24446204b818
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782288
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@{#1491224}
Roll Chrome Mac PGO Profile
Roll Chrome Mac PGO profile from chrome-mac-main-1753293557-62db5e51f0ed9367feb669a6c23db5eb90b26466-130e6845bbaaef3059f8518d8c550d9f4084401f.profdata to chrome-mac-main-1753314684-f8601a81b6179e9dc0abd448fe34eea60cec9315-701ac6259b6182382cbebd32369b58c64a99d12f.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: I210696ae84f157dbd2e98d60e655e160c0c28484
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782224
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@{#1491223}
Roll Chrome Win32 PGO Profile
Roll Chrome Win32 PGO profile from chrome-win32-main-1753271698-dba84a7f93b583ffd4f2cb2ad6c063c564f9f972-faf031012b7e5c3f8eae3fda40f75490f508e42d.profdata to chrome-win32-main-1753293557-1e5f5de80b7fe2c07413d277b32fb2f829caace6-130e6845bbaaef3059f8518d8c550d9f4084401f.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-win32-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:win-chrome
Tbr: pgo-profile-sheriffs@google.com
Merge-Approval-Bypass: Chrome autoroller
Change-Id: Ia6827cfd16335b8e5fb907c37b5d5856147d101e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781815
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@{#1491222}
Refactor: split module templates into separate file.
This will allow in the future for each platform's config to be stored in
a separate, autogenerated file.
Bug: 425527533
Change-Id: I6a6a69646b29f1a4a6238e8b8375b0f88ef5ea07
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6778646
Commit-Queue: Matt Stark <msta@google.com>
Reviewed-by: Takuto Ikuta <tikuta@chromium.org>
Reviewed-by: Junji Watanabe <jwata@google.com>
Cr-Commit-Position: refs/heads/main@{#1491221}
Roll src-internal from 69aa4b323eee to c304aaac9c9d (3 revisions)
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/69aa4b323eee..c304aaac9c9d
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,suzukikeita@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:1423117
Tbr: suzukikeita@google.com
Change-Id: Ib53851d600e9d1b7696520fb604eb9b26153bfa2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782287
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@{#1491220}
[FSA] Add implementation for "write" permission mode
- Add `blink::mojom::FileSystemAccessPermissionMode::kWrite` and make
the enum a standalone file to resolve dependency issues.
- Update `mojom::FileSystemAccess*Handle::GetPermissionStatus(bool)`
and `mojom::FileSystemAccess*Handle::RequestPermission(bool)` to take
`FileSystemAccessPermissionMode` instead of `bool writable`.
- Pipe down kWrite to content layer and update
`FileSystemAccessHandleBase::DoRequestPermission()` and
`FileSystemAccessHandleBase::DoGetPermissionStatus()` accordingly.
- The new permission mode is NOT surfaced to any IDL yet. And it should
be no impact to existing FileSystemAccess APIs.
Bug: 40276567
Change-Id: Ic9888cf389a553dd06b6d9127f00a9d0087deae8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6767698
Reviewed-by: Austin Sullivan <asully@chromium.org>
Reviewed-by: Nate Chapin <japhet@chromium.org>
Reviewed-by: Sam McNally <sammc@chromium.org>
Commit-Queue: Ming-Ying Chung <mych@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491219}
Updating trunk VERSION from 7315.0 to 7316.0
* This is an automated release commit.
* Do not revert without consulting chrome-pmo@google.com.
NOAUTOREVERT=true
Change-Id: I58d55981a9b46b3f0ae111d67a8915b03daf4f91
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6777135
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1491218}
Roll Chrome Win ARM64 PGO Profile
Roll Chrome Win ARM64 PGO profile from chrome-win-arm64-main-1753293557-65e43a6a29efc70373fd94b97be79d2b1b99b0ec-130e6845bbaaef3059f8518d8c550d9f4084401f.profdata to chrome-win-arm64-main-1753314684-2bbba4c72c63fafcd910a4d1123a071af9dd5c85-701ac6259b6182382cbebd32369b58c64a99d12f.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-win-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: I155269176e0cc63ee2a5cb4521afe16eda4b64c6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782283
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@{#1491217}
webnn: support run conformance test by specified test name
This CL introduces the 'tc' parameter to run conformance tests of
operators by specified test name. For example, navigating to this link
[1] only runs "abs float32 1D tensor" test, and link [2] only runs "abs
float32 1D tensor" and "abs float32 4D tensor" two tests. Besides, it's
to run all abs conformance tests without 'tc' parameter. This feature is
useful for driver developer to focus on debugging a particular failure
test case.
[1] https://wpt.live/webnn/conformance_tests/abs.https.any.html?device=cpu&tc=abs float32 1D tensor
[2] https://wpt.live/webnn/conformance_tests/abs.https.any.html?device=cpu&tc=abs float32 1D tensor&tc=abs float32 4D tensor
Bug: 433326681
Change-Id: Ic23cce2f652c7501a2392475490dd722ca9d3044
Cq-Include-Trybots: luci.chromium.try:win11-blink-rel, mac14.arm64-blink-rel, mac14-blink-rel, mac15.arm64-blink-rel, mac15-blink-rel, linux-blink-rel
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6776105
Commit-Queue: Feng Dai <feng.dai@intel.com>
Reviewed-by: ningxin hu <ningxin.hu@intel.com>
Auto-Submit: Feng Dai <feng.dai@intel.com>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491216}
spanification: automatically spanify various pointers
This is the result of running the automatic spanification on linux and
updating code to use and pass spans where size is known. This CL has no
behavior changes.
All changes should be correct and no behaviour changes in patchset 1,
however the plan is to follow up and remove the redundant size
parameters. To this effect in patchset 2 we've added CHECKS and renames
to note the fact the size is believed to be redundant. This was done
through AI and should be carefully checked, but the CHECKS are not fatal
and thus if unsure should be fine to land and remove after reports of
the crashes.
The original patch was fully automated using script:
//tools/clang/spanify/rewrite-multiple-platforms.sh -platforms=linux
and then split with `git cl split --target-range 8 32 --max-depth=2
--no-reviewers -d ~/description.txt`
This covers directories: third_party/blink/renderer/core/streams
This is part of auto spanification see internal doc about it:
https://docs.google.com/document/u/1/d/1poEhNARfFas2osqPoXGzVZtBgnOQGQtQNUFTA-MlADs/edit?tab=t.0
This CL was uploaded by an experimental version of git cl split
(https://crbug.com/389069356).
Bug: 431824299
Change-Id: I671938cc544cedb53fd7b53f7feedafd4ad09064
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6734602
Auto-Submit: Stephen Nusko <nuskos@chromium.org>
Commit-Queue: Stephen Nusko <nuskos@chromium.org>
Reviewed-by: Adam Rice <ricea@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491215}
Roll Chrome Android Desktop x64 PGO Profile
Roll Chrome Android Desktop x64 PGO profile from chrome-android-desktop-x64-main-1753293557-75f1c7bff7db606385a00be835a600d13f75c72f-130e6845bbaaef3059f8518d8c550d9f4084401f.profdata to chrome-android-desktop-x64-main-1753314684-fca3aa394d92074d0550999c1889d710de7f353b-701ac6259b6182382cbebd32369b58c64a99d12f.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-desktop-x64-chromium
Please CC al-clank-pgo@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: 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: Iddd3b8c3052a8012d8a097feab608560ed583742
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782282
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@{#1491214}
Revert "Set AutofillEnableShowSaveCardSecurelyMessage enabled by default"
This reverts commit 961eee164eeca76b9b184e5f2270e5cbe60d2a29.
Reason for revert: Suspect it broke test:
ChromePaymentsAutofillClientTest.ShowSaveCreditCardToCloud_CardSaveTypeIsWithCvc_RequestsBottomSheet
on:
https://ci.chromium.org/ui/p/chrome/builders/ci/android-desktop-16-x64-rel-al-emu-tests/2158/overview
Bug: b:409603749
Original change's description:
> Set AutofillEnableShowSaveCardSecurelyMessage enabled by default
> and remove fieldtrial testing config.
>
> Bug: b:409603749
> Change-Id: I809412f164f597f6df94508c8e7b5867f47f606f
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781879
> Commit-Queue: Qihui Zhao <qihuizhao@google.com>
> Reviewed-by: Olivia Saul <osaul@google.com>
> Cr-Commit-Position: refs/heads/main@{#1491097}
Bug: b:409603749
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Change-Id: I41dec64a167351b2f795216960efa9b1c399e016
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6778012
Auto-Submit: Andrew Grieve <agrieve@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Owners-Override: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Andrew Grieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491213}
[webaudio-testharness] Migrate iirfilter-getFrequencyResponse.html
This CL rewrites the IIRFilterNode getFrequencyResponse() test to use
testharness.js instead of the legacy audit.js framework. The logic and
thresholds remain unchanged, preserving test validity. This migration
helps reduce dependencies on audit.js and aligns with Web Platform Test
standards.
Bug: 396477778
Change-Id: I093a0ccd8792a5813c47e46148b09c7410474e1f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6688066
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Auto-Submit: Punith Nayak <punithbnayak@chromium.org>
Reviewed-by: Michael Wilson <mjwilson@chromium.org>
Commit-Queue: Punith Nayak <punithbnayak@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491212}
[webaudio-testharness] Migrate audiochannelsplitter.html
This CL replaces usage of audit.js in
third_party/blink/web_tests/webaudio/the-audio-api/audiochannelsplitter.html
with testharness.js, preserving existing test logic and comments.
Bug: 396477778
Change-Id: I82a31c746da93d844cbd3eedc28490fe84e368d6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6709825
Reviewed-by: Michael Wilson <mjwilson@chromium.org>
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Punith Nayak <punithbnayak@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491211}
Roll Chrome Android ARM64 PGO Profile
Roll Chrome Android ARM64 PGO profile from chrome-android64-main-1753311747-b7db342dc73c8647d1539bd995ff39bbc6b6f6ff-3667e2e53a3cce646f3710a8408aed305c3892ea.profdata to chrome-android64-main-1753316103-aba96dd5a3d6f9357486a4c909c3e2d4a07dacbe-f0b2e763b0287bb864a26296f4645584053d65c8.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: Iff7bdd168f23f588b9c4a6ea8011bc90ba2e9b8c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782281
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@{#1491210}
Roll Chrome Win64 PGO Profile
Roll Chrome Win64 PGO profile from chrome-win64-main-1753271698-d867931a2e58acaf23629c343ce4a72e3832d46c-faf031012b7e5c3f8eae3fda40f75490f508e42d.profdata to chrome-win64-main-1753282773-9ff150ff83e0015e7bf29c3a08593d4b1b6cc8ff-32093f0b1887f58ac9849a01921abe9ebdd6e770.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-win64-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:win64-chrome
Tbr: pgo-profile-sheriffs@google.com
Merge-Approval-Bypass: Chrome autoroller
Change-Id: I1fead25d8529ae5e23ce76d6525a257ca9be8b0f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781804
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@{#1491209}
Roll Chrome Mac Arm PGO Profile
Roll Chrome Mac Arm PGO profile from chrome-mac-arm-main-1753307944-0293fce53192d21b2e00d09c92bd45b280f2cc2c-4c40e1c20da2b4ff6ad23a2da704b7bcbf0acf22.profdata to chrome-mac-arm-main-1753314684-7b1d8af4b17e9003032919fefcee7cc879b83668-701ac6259b6182382cbebd32369b58c64a99d12f.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: I5f88f37fc5d3e2f07b890c63a2fdf82648eacfac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782227
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@{#1491208}
disable secagentd.FileEvents tests on trogdor
Bug: 433816171
Change-Id: I3172001ddd0d3ced64ae7bdc9ee2e0e5b13b102c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782061
Auto-Submit: Jeffrey Young <cowmoo@google.com>
Reviewed-by: Yoshiki Iguchi <yoshiki@chromium.org>
Commit-Queue: Yoshiki Iguchi <yoshiki@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491207}
Disable GetLastActiveBrowserWindowInterface_ReturnsLastActive
Bug: 431671448
Change-Id: I424174f8547167ebb695abde2426c9375becfe65
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781451
Reviewed-by: Keita Suzuki <suzukikeita@chromium.org>
Owners-Override: Keita Suzuki <suzukikeita@chromium.org>
Auto-Submit: Nick Birnie <birnie@google.com>
Commit-Queue: Keita Suzuki <suzukikeita@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491206}
NavigationThrottleRunner2: Initial placeholder implementation
This change introduces a new flag-guarded NavigationThrottleRunner2
implementation, which is intended to replace the current one in the
future.
NavigationThrottleRegistryImpl owns a virtual interface to the runner,
and actual instance can be switched behind a base::Feature flag.
This is the first step to introduce the implementation switch, and
subsequent CLs will implement the new behaviour in
NavigationThrottleRunner2.
Bug: 422003056
Change-Id: Ife180cb0284bbdd94a7c420e99073ab932987e55
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6777133
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491205}
spanification: automatically spanify various pointers
This is the result of running the automatic spanification on linux and
updating code to use and pass spans where size is known.
This CL has no behavior changes.
All changes should be correct and no behaviour changes in patchset 1, however the plan is to follow up and remove the redundant size parameters. To this effect in patchset 2
we've added CHECKS and renames to note the fact the size is believed to be redundant. This was done through AI and should be carefully checked, but the CHECKS are not fatal and thus if unsure should be fine to land and remove after reports of the crashes.
The original patch was fully automated using script:
//tools/clang/spanify/rewrite-multiple-platforms.sh -platforms=linux
and then split with
`git cl split --target-range 8 32 --max-depth=2 --no-reviewers -d ~/description.txt`
This covers directories:
remoting
This is part of auto spanification see internal doc about it:
https://docs.google.com/document/u/1/d/1poEhNARfFas2osqPoXGzVZtBgnOQGQtQNUFTA-MlADs/edit?tab=t.0
This CL was uploaded by an experimental version of git cl split
(https://crbug.com/389069356).
Bug: 431824299
Change-Id: I7e86bbf995c7c3c20e81b6042cf486608034b090
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6737283
Reviewed-by: Joe Downing <joedow@chromium.org>
Auto-Submit: Stephen Nusko <nuskos@chromium.org>
Commit-Queue: Stephen Nusko <nuskos@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491204}
Roll Chromium Variations from o7FVvr7bQQu5penh4... to HTAVu9JCOAeq43Tt-...
https://chrome-infra-packages.appspot.com/p/chromium/chrome/test/data/variations/cipd/+/HTAVu9JCOAeq43Tt-jP4PtKydpWS5lVKWZ-Qgx2HUv0C
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/chromium-variations-chromium
Please CC chrome-metrics-team@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in Chromium Variations: https://bugs.chromium.org/p/chromium/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: None
Tbr: chrome-metrics-team@google.com
Change-Id: I03c22f7ed0dda5f4df325c6c466afee31335edcc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782226
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@{#1491203}
ThreadTicks GetForThread should include kernel time for arm64
Modify ThreadTicks::GetForThread to return user time + kernel time
instead of just user time.
Bug: 433551588
Change-Id: I52141f94fa5824601a519f5a2b34cd00cee34e9f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781007
Commit-Queue: Chris Davis <chrdavis@microsoft.com>
Reviewed-by: Will Harris <wfh@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491202}
spanification: automatically spanify various pointers
This is the result of running the automatic spanification on linux and
updating code to use and pass spans where size is known.
This CL has no behavior changes.
All changes should be correct and no behaviour changes, however the plan
is to follow up and remove the redundant size parameters. To this effect
we've added CHECKS and renames to note the fact the size is believed to
be redundant.
The original patch was fully automated using script:
//tools/clang/spanify/rewrite-multiple-platforms.sh -platforms=linux
and then split with
`git cl split --target-range 8 32 --max-depth=2 --no-reviewers -d ~/description.txt`
This covers directories:
mojo
This is part of auto spanification see internal doc about it:
https://docs.google.com/document/u/1/d/1poEhNARfFas2osqPoXGzVZtBgnOQGQtQNUFTA-MlADs/edit?tab=t.0
This CL was uploaded by an experimental version of git cl split
(https://crbug.com/389069356).
Bug: 431824299
Change-Id: I037f3f84dadc1f344525406b43d3e0719781b1be
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6734599
Commit-Queue: Stephen Nusko <nuskos@chromium.org>
Auto-Submit: Stephen Nusko <nuskos@chromium.org>
Reviewed-by: Fred Shih <ffred@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491201}
Roll GoogleTest from 7e17b15f1547 to 32f9f4c82afa (1 revision)
https://chromium.googlesource.com/external/github.com/google/googletest.git/+log/7e17b15f1547..32f9f4c82afa
2025-07-23 absl-team@google.com Skip the predicate on SIGSEGV in death-test on Android builds with API level <= 23.
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/googletest-chromium-autoroll
Please CC asully@google.com,jonathanjlee@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
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:linux_chromium_cfi_rel_ng;luci.chrome.try:win-chrome
Tbr: asully@google.com,jonathanjlee@google.com
Change-Id: I980c1cbef230160ade0b387230ff867b5697be2e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781812
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@{#1491200}
[exit-time-destructors] Exclude target with warnings
This CL is part of number of CLs disabling `-Wexit-time-destructors`in
places where this warning is going off. This will allow having this
warning enabled-by-default across the codebase, whilst documenting the
places where corrections for this warning are necessary.
Bug: 40031409, 430332953
Change-Id: I0a306ea43722c4dd1ba4d59afdf6030492aa87b3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6777947
Reviewed-by: Rick Byers <rbyers@chromium.org>
Commit-Queue: Claudio DeSouza <cdesouza@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491199}
Rollback to pdf library alpha06
Revert back due to unresolved regressions. See bug below.
Will add local modifications back once the change is picked up by the
roller.
See http://crrev.com/c/6669737
Bug: 424250731
Change-Id: I4c9d9738615218f4fb8acb6d8166fe77b9510a73
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782318
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Shu Yang <shuyng@google.com>
Cr-Commit-Position: refs/heads/main@{#1491198}
NTP Promos: Use ordering policy when generating promo lists
Bug: 428035923
Change-Id: I7218dcce4ed5c9e6fad5b9d360fef0d63ecda590
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6780056
Reviewed-by: Dana Fried <dfried@chromium.org>
Commit-Queue: Christopher Grant <cjgrant@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491197}
WebNN: Ensure scale and zeroPoint rank is equal to input rank
This CL implements the WebNN spec change [1] that requires the scale
and zeroPoint for quantizeLinear and dequantizeLinear ops have the
the same rank as input.
[1]: https://github.com/webmachinelearning/webnn/pull/805#discussion_r1919498405
Bug: 396176047
Change-Id: Ia310e0c254ad90967b4e3577e54498fa28532f84
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6773953
Commit-Queue: ningxin hu <ningxin.hu@intel.com>
Reviewed-by: Phillis Tang <phillis@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491196}
Remove redundant parameters from SendMouseWheelEvent [12/n]
This CL is a part of a series of CLs to refactor how motion events are
handled in `ContentUiEventHandler`.
This CL removes redundant `x`, `y`, `ticks_x`, and `ticks_y`
parameters from `SendMouseWheelEvent` and its JNI wrapper. The values
are now obtained from the `MotionEventAndroid` object.
Bug: 417078839
Change-Id: Ieec0ca978ea58154c0d026cb43324ee262038fa1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6736131
Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Keigo Oka <oka@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491195}
Roll Chrome Android ARM64 PGO Profile
Roll Chrome Android ARM64 PGO profile from chrome-android64-main-1753306862-6789fc95071645358839e74ba56025cb768385cd-5fe745a715b290c05cc40c3eb6590a904304b147.profdata to chrome-android64-main-1753311747-b7db342dc73c8647d1539bd995ff39bbc6b6f6ff-3667e2e53a3cce646f3710a8408aed305c3892ea.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: Icd29f987a4448a93dca364f4fe1236eec39d65fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782127
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@{#1491194}
[pus] plumb the pause_js setting to the renderer side
Mainline-3
For prerendering pages that are triggered by "prerender_until_script"
action, they should pause the JS execution until activation (for MVP).
This CL plumbs this setting from the browser side to the renderer side.
Bug: 428500219
Change-Id: Iae58b7ad503827f75b9f57e021e086baff5b27a1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6764926
Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org>
Commit-Queue: Lingqi Chi <lingqi@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491193}
Roll Chrome Mac Arm PGO Profile
Roll Chrome Mac Arm PGO profile from chrome-mac-arm-main-1753300775-51765b994e03e6636c589556812c7a4fc8d29a0e-7a00f784447244cdbe8f755ef429c03c5fecd57a.profdata to chrome-mac-arm-main-1753307944-0293fce53192d21b2e00d09c92bd45b280f2cc2c-4c40e1c20da2b4ff6ad23a2da704b7bcbf0acf22.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: I05c1671fe036b9b2ec90214afda7129311b2bb10
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781989
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@{#1491192}
Refactor SendMouseEvent to use MotionEventAndroidSource [11/n]
This change continues the refactoring of the JNI bridge by removing
redundant parameters from the `SendMouseEvent` method. The method now
uses the `MotionEventAndroidSource` to directly access the event data,
simplifying the JNI call and making the code more maintainable.
This is a pure refactoring with no behavior change.
Bug: 417078839
Change-Id: I7491310756f06cf3760c755b6ac8e6bb3d160f9f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6736130
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Keigo Oka <oka@chromium.org>
Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491191}
Roll Enterprise Companion chromium_mac_arm64 from H-lcF-xdzf6ydSO8a... to KYK86AbBYpTxcC8ce...
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/ceca-chromium-mac-arm64-chromium
Please CC chrome-updates-dev@chromium.org,omaha-core@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in Enterprise Companion chromium_mac_arm64: https://g-issues.chromium.org/issues/new?component=1604672&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:linux-enterprise-companion-try-builder-dbg;luci.chromium.try:linux-enterprise-companion-try-builder-rel;luci.chromium.try:mac-enterprise-companion-try-builder-dbg;luci.chromium.try:mac-enterprise-companion-try-builder-rel;luci.chromium.try:win-enterprise-companion-try-builder-dbg;luci.chromium.try:win-enterprise-companion-try-builder-rel
Tbr: omaha-core@google.com
Change-Id: I81b7e415b6b60040bded4be2e4e6a5e2049fbbf3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781991
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@{#1491190}
Roll Enterprise Companion chromium_win_x86_64 from UVrqAtGzmgUEfnEM-... to I9bjoaDlSd9f5OfXj...
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/ceca-chromium-win-x86-64-chromium
Please CC chrome-updates-dev@chromium.org,omaha-core@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in Enterprise Companion chromium_win_x86_64: https://g-issues.chromium.org/issues/new?component=1604672&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:linux-enterprise-companion-try-builder-dbg;luci.chromium.try:linux-enterprise-companion-try-builder-rel;luci.chromium.try:mac-enterprise-companion-try-builder-dbg;luci.chromium.try:mac-enterprise-companion-try-builder-rel;luci.chromium.try:win-enterprise-companion-try-builder-dbg;luci.chromium.try:win-enterprise-companion-try-builder-rel
Tbr: omaha-core@google.com
Change-Id: Ibc1738101869446eb5a2a65e3c9ee86352831569
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782014
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@{#1491189}
Add trace events to AudioContext, Destination, and SilentSinkSuspender
The following events are added:
- AudioContext::StartRendering()
- AudioContext::StopRendering()
- AudioContext::FrameVisibilityChanged()
- AudioContext::SuspendRendering()
- AudioContext::ResumeOnPrerenderActivation()
- AudioContext::StartContextInterruption()
- AudioContext::EndContextInterruption()
- SilentSinkSuspender::TransitionSinks()
- RealtimeAudioDestinationHandler::SetDetectSilenceIfNecessary()
These events would help to analyze the audio context lifecycle in real
time.
Bug: 415797981
Change-Id: If70ee1f54ff5342dd1ef2d6dca2aa763f6bcd053
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6774346
Commit-Queue: Hongchan Choi <hongchan@chromium.org>
Reviewed-by: Thomas Guilbert <tguilbert@chromium.org>
Reviewed-by: Michael Wilson <mjwilson@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491188}
Roll Enterprise Companion chromium_win_x86 from S5floWfqKlbbmjco5... to Ug5VZgL4SCG86isJQ...
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/ceca-chromium-win-x86-chromium
Please CC chrome-updates-dev@chromium.org,omaha-core@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in Enterprise Companion chromium_win_x86: https://g-issues.chromium.org/issues/new?component=1604672&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:linux-enterprise-companion-try-builder-dbg;luci.chromium.try:linux-enterprise-companion-try-builder-rel;luci.chromium.try:mac-enterprise-companion-try-builder-dbg;luci.chromium.try:mac-enterprise-companion-try-builder-rel;luci.chromium.try:win-enterprise-companion-try-builder-dbg;luci.chromium.try:win-enterprise-companion-try-builder-rel
Tbr: omaha-core@google.com
Change-Id: I8d274964b046143bdbfac0343d00b8ab47e208a9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782015
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@{#1491187}
crypto: deduplicate EVPMDForHashKind
This function has 3 copies in //crypto already and several elsewhere in
the codebase. This change moves it onto the crypto/hash interface and
has the other clients in //crypto call that.
Fixed: 430635196
Change-Id: Icfdf3edd365690af63afa72d586bb36d54b1767a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6778234
Reviewed-by: Matt Mueller <mattm@chromium.org>
Commit-Queue: Elly FJ <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491186}
Roll clank/internal/apps from a1044967c2ce to 08f659e4dc8f (1 revision)
https://chrome-internal.googlesource.com/clank/internal/apps.git/+log/a1044967c2ce..08f659e4dc8f
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 agrieve@google.com,chrome-brapp-engprod@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: agrieve@google.com
No-Try: true
Change-Id: I110b388345832c2f5c0fb684405db1bc942da04a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782145
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@{#1491185}
Writing Assistance APIs: Add language expansion feature flags
Add Writer/Rewriter supported language utils, params, flags.
Facilitates experimentation with expanded API language options.
See crrev.com/c/6778695 for plumbing API options to protos.
Bug: 428229777
Change-Id: Id74f644f4160bec49f62262124a30c7610680e5a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6779232
Commit-Queue: Mike Wasserman <msw@chromium.org>
Auto-Submit: Mike Wasserman <msw@chromium.org>
Reviewed-by: Brad Triebwasser <btriebw@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491184}
crypto: get rid of RSAPrivateKey::CreateFromKey
The only remaining clients of it were some net unit tests which already
had an EVP_PKEY in hand, so just use the EVP_PKEYs directly for now.
Bug: 425863216
Change-Id: I00672a691f58198da75bfb85111a674b53bc196e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782099
Reviewed-by: Matt Mueller <mattm@chromium.org>
Commit-Queue: Elly FJ <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491183}
ash: extend the expiry date for the metrics that my team owns.
Set all relevant metrics to be the same expiry date so that it's easier
to extend them in the future.
421901535, 421901635, 418771728, 418772389
Fixed: 400444371, 404246764, 418772233, 417216861, 421901474, 421901438,
Change-Id: Ie47bdc88b46e07ba9d34119e4a1f2ab52e6a5e86
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6730500
Commit-Queue: Xiaoqian Dai <xdai@chromium.org>
Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Reviewed-by: Tony Yeoman <tby@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491182}
Roll Enterprise Companion chromium_linux64 from R95qtSy1rOs0TjSjv... to ZwB7j920SYwARGX8j...
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/ceca-chromium-linux64-chromium
Please CC chrome-updates-dev@chromium.org,omaha-core@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in Enterprise Companion chromium_linux64: https://g-issues.chromium.org/issues/new?component=1604672&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:linux-enterprise-companion-try-builder-dbg;luci.chromium.try:linux-enterprise-companion-try-builder-rel;luci.chromium.try:mac-enterprise-companion-try-builder-dbg;luci.chromium.try:mac-enterprise-companion-try-builder-rel;luci.chromium.try:win-enterprise-companion-try-builder-dbg;luci.chromium.try:win-enterprise-companion-try-builder-rel
Tbr: omaha-core@google.com
Change-Id: I3ea1525ea8fa3199ff5420c483c578da18227f65
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782012
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@{#1491181}
[WebNN] Implement gru and gruCell operations for ORT backend
Bug: 432377532
Change-Id: I909fedf8c3500add63cd04c02b25772554cee6fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6769125
Reviewed-by: Phillis Tang <phillis@chromium.org>
Reviewed-by: ningxin hu <ningxin.hu@intel.com>
Commit-Queue: Bin Miao <bin.miao@intel.com>
Cr-Commit-Position: refs/heads/main@{#1491180}
Roll Enterprise Companion chromium_mac_amd64 from dlKk0is7o_-2KJCYJ... to fB6AH_X51yaYucp26...
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/ceca-chromium-mac-amd64-chromium
Please CC chrome-updates-dev@chromium.org,omaha-core@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in Enterprise Companion chromium_mac_amd64: https://g-issues.chromium.org/issues/new?component=1604672&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:linux-enterprise-companion-try-builder-dbg;luci.chromium.try:linux-enterprise-companion-try-builder-rel;luci.chromium.try:mac-enterprise-companion-try-builder-dbg;luci.chromium.try:mac-enterprise-companion-try-builder-rel;luci.chromium.try:win-enterprise-companion-try-builder-dbg;luci.chromium.try:win-enterprise-companion-try-builder-rel
Tbr: omaha-core@google.com
Change-Id: Ibaf91371b540d4fdf61c8a3173a16cc0e1edaff1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782013
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@{#1491179}
[Read aloud] Use the highlight menu without phrase highlighting.
Previously, the highlight menu [1] was planned to be launched with
phrase highlighting, so the menu was guarded around the phrase
highlighting flag.
However, there's value in launching the menu separate from phrase
highlighting, so this change shows the menu without the phrase
highlighting option by default.
[1] https://screenshot.googleplex.com/9scCCzU8qh47etW.png
Fixed: 428973725
Change-Id: Ieb42b911d0571ff22571ff1e96a7c355d03f0f90
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781370
Reviewed-by: Jocelyn Tran <jocelyntran@google.com>
Commit-Queue: Lauren Winston <lwinston@google.com>
Cr-Commit-Position: refs/heads/main@{#1491178}
[WebNN] Implement LayerNormalization operation for ORT backend
Bug: 432054940
Change-Id: Iea5704b58c25a6438aac62283ba44fdba5c6f439
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6758777
Commit-Queue: Bin Miao <bin.miao@intel.com>
Reviewed-by: ningxin hu <ningxin.hu@intel.com>
Reviewed-by: Phillis Tang <phillis@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491177}
Record time spent on each glic loading stage
NO_IFTTT=Suppressing the complaint about NOT_LOADING being missing from histograms.xml because we don't need to log a duration for that stage.
Bug: 433274974
Change-Id: I1e3211be9d5310aec99ec9a96830eeac961079d4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6778682
Reviewed-by: Dan Harrington <harringtond@chromium.org>
Commit-Queue: Ian Wells <iwells@chromium.org>
Auto-Submit: Ian Wells <iwells@chromium.org>
Commit-Queue: Dan Harrington <harringtond@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491176}
Roll Catapult from f789180ef868 to 5b2aa8309e96 (1 revision)
https://chromium.googlesource.com/catapult.git/+log/f789180ef868..5b2aa8309e96
2025-07-23 wenbinzhang@google.com [chromeperf] moving pinpoint forward
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/catapult-autoroll
Please CC chrome-speed-operations@google.com,dberris@chromium.org,eduardoyap@google.com,jbudorick@chromium.org,johnchen@chromium.org,sullivan@chromium.org,wenbinzhang@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
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
Bug: None
Tbr: eduardoyap@google.com
Change-Id: I3136b07f097faab6f17f1e938530e7d3293a772c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781990
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@{#1491175}
Replace flat_set with EnumSet for OnDeviceModelPerformanceHint
Change-Id: I76f26d3b90c6afe0f3f075952d29721bea51cf6f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782025
Commit-Queue: Raj T <rajendrant@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491174}
Roll Chrome Android ARM64 PGO Profile
Roll Chrome Android ARM64 PGO profile from chrome-android64-main-1753302081-6b36eb314dfc7b27e357a958dad5d8248550f93d-ad0a20f5ea51409d569f4e876f2c44ffe868ac0e.profdata to chrome-android64-main-1753306862-6789fc95071645358839e74ba56025cb768385cd-5fe745a715b290c05cc40c3eb6590a904304b147.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: I6903bb88af0d3967a37fbd6d02a30b83d534ffc5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781506
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@{#1491173}
WebNN: Fall back to TFLite backend if ORT backend is not available
This CL enables the fallback to TFlite backend if ORT `Environment`
creation fails. Instead of reporting mojom error to renderer process,
only print the error log by `LOG(ERROR)`.
The CL also simplifies some codes:
1. Let `SessionOptions::Create` not return `mojom::ErrorPtr`, as it
shouldn't fail.
2. Let `Environment::Create` return error of `std::string` instead of
`mojom::ErrorPtr`.
Bug: 430616169
Change-Id: If12b9741aaaea9ffdf8e7a411f82a451bec2ceff
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6773670
Commit-Queue: Mingming1 Xu <mingming1.xu@intel.com>
Reviewed-by: ningxin hu <ningxin.hu@intel.com>
Reviewed-by: Rafael Cintron <rafael.cintron@microsoft.com>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491172}
Roll Chrome Android ARM64 Orderfile from 9u1H4l0UpmS77e1bx... to Dx9VhIMwnCX73bAra...
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/orderfile-android-arm64-chromium
Please CC clank-build@google.com,clank-library-failures@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: clank-library-failures@google.com
Merge-Approval-Bypass: Chrome autoroller
Change-Id: Iee762b05a5127b09754b078f8ab3896e4c703ac2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781857
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@{#1491171}
Support Windows patch version in GpuControlList
This change add support to specify a Windows patch version in GPU
control list.
The GPU driver bug list already has several entries that limit the
workaround to a specific patch version of Windows, but these have
previously been ignored by GPU control list.
This means that any entries that specify, e.g. <10.0.26100.xxxx will
actually match <10.0.26100 (i.e. <10.0.26100.0). This will therefore
unexpectedly allow versions between 10.0.26100.0 up to 10.0.26100.xxxx.
Bug: 431824285
Change-Id: I1488a0e9029073bb4c3d1563635e159692ab5250
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6735069
Reviewed-by: Rafael Cintron <rafael.cintron@microsoft.com>
Commit-Queue: Michael Tang <tangm@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#1491170}
Revert "Set CCT sample app targetSdkVersion="35""
This reverts commit a14f8114bd160a491c5a4ecf4d52dcd9d45eede1.
Reason for revert: crrev.com/c/6761856 already fixed this
Bug: 433813184
Original change's description:
> Set CCT sample app targetSdkVersion="35"
>
> Apps with targetSdkVersion="36" automatically draw edge to edge, which
> is breaking the CCT sample app on Android 16.
>
> Bug: 433813184
> Change-Id: I2e740e4a0fd14f8799ba21da66fdbf37b0bf885d
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781399
> Auto-Submit: Theresa Sullivan <twellington@chromium.org>
> Reviewed-by: Moe Adel <adelm@google.com>
> Commit-Queue: Moe Adel <adelm@google.com>
> Commit-Queue: Theresa Sullivan <twellington@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1491160}
Bug: 433813184
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Change-Id: I2761a3e098254eb424f02ae87f11d963868f9a0e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6778235
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Auto-Submit: Theresa Sullivan <twellington@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491169}
[iOS] Update Google logo color on NTP when a background is applied
This CL updates the appearance of the Google logo on the New Tab Page
(NTP) based on the applied background:
- If the background is an image, the logo is shown in white.
- If the background is a solid color, the logo uses colorPalette.tintColor.
- If no background is applied, the logo remains in its default colored state.
Spec:
https://docs.google.com/document/d/1tlAMUSiFMSTYVbuLdOz9uudry0lWFFrGlpz4nljonis/edit?resourcekey=0-Uapn51jTRGwOT6hsozObgA&tab=t.0
Background color: https://screenshot.googleplex.com/6FyuddqviWP5AWW
Background image: https://screenshot.googleplex.com/uteDGiUfoGxtwSH
Default experience: https://screenshot.googleplex.com/7PGfQWgbcCyoVnd
Change-Id: I5f788c9916d90e16aeaba8feeb3e8e6193b4b84d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6780364
Reviewed-by: Adam Arcaro <adamta@google.com>
Commit-Queue: Pier-Alexandre Bouchard <pabouchard@google.com>
Cr-Commit-Position: refs/heads/main@{#1491168}
[Save and Fill] Offer upload Save and Fill dialog
If the preflight call succeeds and the legal message is valid, offer the
upload version of the Save and Fill dialog. If it fails, fall back to
offering the local dialog.
Design doc: go/payments-autofill-save-and-fill-desktop-design
Bug: 378164165
Change-Id: Ia73811efe7accb1a23528bf439b06f9c4a34e4ab
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6771731
Reviewed-by: Siyu An <siyua@chromium.org>
Commit-Queue: Verina Armanyous <averina@google.com>
Cr-Commit-Position: refs/heads/main@{#1491167}
Revert "Default enable SalientImage traffic on mobile."
This reverts commit 4200e34b7c293b4ab7057bbd6d60b5753e28fe83.
Reason for revert: Not ready to launch yet.
Bug: 399446794
Original change's description:
> Default enable SalientImage traffic on mobile.
>
> Change-Id: Iac8a6878da74d1cb5b9ddd54af885c2e44d6b803
> Bug: 399446794
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6659058
> Commit-Queue: Jonathan Freed <freedjm@google.com>
> Reviewed-by: Steven Holte <holte@chromium.org>
> Auto-Submit: Catherine Liu <catliu@google.com>
> Reviewed-by: Jonathan Freed <freedjm@google.com>
> Cr-Commit-Position: refs/heads/main@{#1478061}
Bug: 399446794
Change-Id: I79aac5f695147217d5e4090d778a8271d56684dc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6773678
Reviewed-by: Steven Holte <holte@chromium.org>
Reviewed-by: Jonathan Freed <freedjm@google.com>
Commit-Queue: Catherine Liu <catliu@google.com>
Cr-Commit-Position: refs/heads/main@{#1491166}
Set up ExtensionWindowControllerBridge
ExtensionWindowControllerBridge will give Java code access to the
cross-platform extension windowing code.
Changes:
(1) Set up a modular directory
(browser/ui/android/extension/windowing/)
with the skeletons of:
ExtensionWindowControllerBridge (.java & .cc), and
ExtensionWindowControllerBridgeFactory (.java).
(2) Connect the Java ExtensionWindowControllerBridge with its native
counterpart.
(3) Compile new code into the "desktop Android" build.
See:
`chrome/android/BUILD.gn` (Java)
`chrome/browser/ui/BUILD.gn` (C++)
(4) Add unit tests.
Bug: 424854148
Change-Id: I9a016c90e805c990d1b1108d8a884343727a9f7e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6775982
Commit-Queue: Linyu He <linyuh@google.com>
Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491165}
Destroy AndroidBrowserWindow in ChromeAndroidTaskImpl#destroy()
http://crrev.com/c/6735831 introduced AndroidBrowserWindow#destroy(),
so we can now call it in ChromeAndroidTaskImpl#destroy().
Bug: 427214087
Change-Id: I729a136a6e26dfd18bdf5943029e991ec7da72b2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6778452
Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Commit-Queue: Linyu He <linyuh@google.com>
Cr-Commit-Position: refs/heads/main@{#1491164}
[launcher search] Update the field trail
As ica has launched, remove it the from the field trail.
Instead add the ocr so that we can relaunch it.
Bug: 410785996
Change-Id: I098be4ff40f40fad39bf2a92a929635502d50322
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6780000
Reviewed-by: Xinglong (Alan) Luan <alanlxl@chromium.org>
Commit-Queue: CJ Huang <chenjih@google.com>
Cr-Commit-Position: refs/heads/main@{#1491163}
Roll androidx from XYEuEU1MHqK0JQ6QS... to s8TCmy3SnbP9-airP...
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/androidx-chromium
Please CC clank-build@google.com,clank-library-failures@google.com,wnwen@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
Cq-Include-Trybots: luci.chrome.try:android-internal-binary-size;luci.chrome.try:android-internal-rel;luci.chrome.try:test-emulator
Tbr: clank-library-failures@google.com
Change-Id: I71ef490ce7429a3966e8e9e62f0fc319f8831187
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781132
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@{#1491162}
ash/ambient: base/hash/sha1 -> crypto/hash
The new API is equivalent but not deprecated.
Bug: 430344933
Change-Id: Iaa93908847b82be1728cc04f94664fbef8eff2aa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6779576
Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Commit-Queue: Elly FJ <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491161}
Set CCT sample app targetSdkVersion="35"
Apps with targetSdkVersion="36" automatically draw edge to edge, which
is breaking the CCT sample app on Android 16.
Bug: 433813184
Change-Id: I2e740e4a0fd14f8799ba21da66fdbf37b0bf885d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781399
Auto-Submit: Theresa Sullivan <twellington@chromium.org>
Reviewed-by: Moe Adel <adelm@google.com>
Commit-Queue: Moe Adel <adelm@google.com>
Commit-Queue: Theresa Sullivan <twellington@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491160}
Roll llvm-libc from 15268943dc72 to 3a943c302028 (9 revisions)
https://chromium.googlesource.com/external/github.com/llvm/llvm-project/libc.git/+log/15268943dc72..3a943c302028
2025-07-23 lntue@google.com [libc] Add support for __builtin_is_constant_evaluated for GCC 9+. (#150322)
2025-07-23 huberjn@outlook.com [libc] Search empty bits after failed allocation (#149910)
2025-07-23 huberjn@outlook.com [libc] Cache the most recently used slot for a chunk size (#149751)
2025-07-23 lntue@google.com [libc] Fix problem with older compilers that do not have __has_builtin. (#150264)
2025-07-23 lntue@google.com [libc] Make FPUtils' rounding_mode.h functions constexpr. (#149167)
2025-07-23 kpandey81930@gmail.com [libc][math] Remove constexpr from bfloat16 comparison operations (#150227)
2025-07-23 kpandey81930@gmail.com [libc][math][c++23] Implement comparison operations operator overloads for BFloat16 (#150087)
2025-07-23 leandrolcampos@yahoo.com.br [libc] Fix incorrect macro usage in shared/sign.h (#150140)
2025-07-22 sriya.pratipati@gmail.com [libc] Fixed mbtowc functions (#150118)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/llvm-libc-chromium
Please CC aeubanks@google.com,lexan@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: aeubanks@google.com
Change-Id: I09a73930a404bd6dd5066daade16d24050feef37
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781987
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@{#1491159}
[line-clamp] Support clamping by lines and a height at the same time
Until now, in our implementation of `line-clamp`, we allowed clamping
by a number of lines (e.g. `line-clamp: 3`), and clamping by a block
size (e.g. `line-clamp: auto`, with a block size constraint given by
`max-height`, for example); but we did not support clamping by both.
If `line-clamp: 3` was set on a container with a height that did not
fully fit the third line, that line would overflow, but the clamp
point would not be moved earlier.
However, in the April CSSWG F2F, it was discussed that clamping by
both lines and a block size should be possible. This was not resolved
at that point, since this was tangential to the issue that was being
discussed, but the working group seemed to lean in that direction.
We implement this by adding a new value to the `LineClampData::State`
enum, `kClampByLinesWithBfcOffset`. This state will both act as if
clamping by a number of lines, while at the same time checking if we
ever go past the BFC offset before the clamp point, in which case we
relayout using regular `kClampByLines`.
Bug: 40336192
Change-Id: I2519c9f84b3ca41aa9418c435bea978bfe1fec73
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6757119
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Andreu Botella <abotella@igalia.com>
Cr-Commit-Position: refs/heads/main@{#1491158}
Connect Java Android{Browser|Base}Window and their native counterparts
This CL is large, but the changes are simple:
(1) Connect Java Android{Browser|Base}Window with their native
counterparts:
Add native ctor and dtor and Java methods to invoke them.
(2) Connect AndroidBrowserWindow with AndroidBaseWindow:
* Return AndroidBaseWindow in AndroidBrowserWindow::GetWindow;
* Destroy AndroidBaseWindow in AndroidBrowserWindow#destroy().
(3) Add native unit tests to test each (java, cc) pair.
Bug: 427214087
Bug: 427215420
Change-Id: I430e4daf9ccf423935d3908bf39e5170ef4a8953
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6735831
Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Commit-Queue: Linyu He <linyuh@google.com>
Cr-Commit-Position: refs/heads/main@{#1491157}
[LNA] Update urls for spec location
Change links pointing to the LNA explainer to point to the LNA spec
instead.
Also remove a random TODO that was already done that was next to
one of the links.
Bug: 394009026
Change-Id: I4194fe973c1aeec924b797ec8cabbffed2bcc705
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6768252
Reviewed-by: Adam Rice <ricea@chromium.org>
Reviewed-by: Igor Ruvinov <igorruvinov@chromium.org>
Commit-Queue: Hubert Chao <hchao@chromium.org>
Reviewed-by: Chris Thompson <cthomp@chromium.org>
Reviewed-by: Giovanni Ortuno Urquidi <ortuno@chromium.org>
Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Reviewed-by: Camille Lamy <clamy@chromium.org>
Reviewed-by: Yann Dago <ydago@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491156}
[PWA/Trusted Icons] Introduce WebAppIconManager APIs to write to disk
This CL updates WebAppIconManager::WriteData() to also write to the
disk. The information in stored inside `profile_dir/manifest_resources/<app_id>/Trusted Icons/<Icon Purpose>/size.png`. Also adds a unit-test that verifies storing the
icons from the disk and reading it.
Change-Id: I9a2a1bd1bc568f505fcafb0ac402a875ba143c26
Bug: 423906188
Validate-Test-Flakiness: skip
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6776003
Reviewed-by: May Siem <msiem@chromium.org>
Commit-Queue: Dibyajyoti Pal <dibyapal@chromium.org>
Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491155}
crypto/keychain: move into crypto/apple
We want to move OS-specific abstractions into OS subdirectories to make
it easier for users to navigate //crypto. This change moves the
keychain-related apple APIs into the apple subdirectory and updates all
includes of them. It also renames the various keychain-related classes
from:
crypto::AppleFoo
to:
crypto::apple::Foo
and updates uses of them.
Bug: 431952820
Change-Id: I7f1b16b24e9c6e7d6c0fd75d50a317b88b1e7b73
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6736212
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Elly FJ <ellyjones@chromium.org>
Owners-Override: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491154}
[line-clamp] Allow clamping after lineless blocks
In the April CSS F2F, it was resolved that when clamping by a height,
if the last thing that fits without overflowing is a lineless block,
then the clamp point would be after it, and no line would have an
ellipsis.
This is actually a behavior that we had previously implemented in
Chromium, but which we changed in https://crrev.com/c/5904459 since
some conversations in the CSSWG seemed to indicate that clamping only
after a line was preferred. However, the implementation before that CL
used a second counter to indicate the number of remaining blocks after
the last line, and the way in which that interacted with the number of
lines until clamp was sometimes hard to reason about. So in this CL we
have gone with a different approach.
In `LineClampData` we add a new state `kClampAfterLayoutObject`, which
stores a pointer to a `LayoutObject`, which should be the last in-flow
layout object before clamp. When this state is set, if
`BlockLineClampData::UpdateAfterLayout` is called with a layout result
whose corresponding layout object matches, then the state is changed
to be `kLinesUntilClamp` with a negative number of lines.
Bug: 40336192, 407983089
Change-Id: I10c3246f583f92825aafa78e179fd809b1ef8481
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6708845
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Andreu Botella <abotella@igalia.com>
Cr-Commit-Position: refs/heads/main@{#1491153}
crypto: remove RSAPrivateKey::Create
There are no remaining clients of it; key generation now has to go via
PrivateKey::GenerateRsa*() (which only allows generating fixed key sizes
chosen by //crypto owners).
Bug: 425863216
Change-Id: I6aeb93048e2fd9984eab3a6d9686fa63babde921
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781523
Reviewed-by: Matt Mueller <mattm@chromium.org>
Commit-Queue: Elly FJ <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491152}
Roll Catapult from 961f2ceed93c to f789180ef868 (1 revision)
https://chromium.googlesource.com/catapult.git/+log/961f2ceed93c..f789180ef868
2025-07-23 wenbinzhang@google.com [chromeperf] add tags for swarming task if it is from perf on cq
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/catapult-autoroll
Please CC chrome-speed-operations@google.com,dberris@chromium.org,eduardoyap@google.com,jbudorick@chromium.org,johnchen@chromium.org,sullivan@chromium.org,wenbinzhang@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
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
Bug: None
Tbr: eduardoyap@google.com
Change-Id: I17c6f80c49ee0abbb2f47ba07753184e23da5d20
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781982
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@{#1491151}
[ozone/wayland] Fix dangling pointer by resetting drag delegate in WaylandConnection destructor
Bug: 324294360
Change-Id: I54f6479bf57b926d1e7d4e80dde7867fa6409fe5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6766454
Reviewed-by: Max Ihlenfeldt <max@igalia.com>
Commit-Queue: AbdAlRahman Gad <agad@igalia.com>
Reviewed-by: Orko Garai <orko@igalia.com>
Cr-Commit-Position: refs/heads/main@{#1491150}
[ios] Disable WindowOpenByDomTest.DocumentWrite
Failing on devices.
Bug: 433776063
Change-Id: I92fb8a6978defc132482e6b0c0f66d48079669bf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6780694
Commit-Queue: Chris Lu <thegreenfrog@chromium.org>
Reviewed-by: Mike Dougherty <michaeldo@chromium.org>
Auto-Submit: Chris Lu <thegreenfrog@chromium.org>
Owners-Override: Chris Lu <thegreenfrog@chromium.org>
Commit-Queue: Mike Dougherty <michaeldo@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491149}
[ozone/wayland] Remove unnecessary DanglingUntriaged flags from various pointers
It's safe to remove DanglingUntriaged, as tests and manual checks show
no dangling pointer issues.
Bug: 324294360
Change-Id: I1c4e5ac167a7b301bf78022d09e832a225b704e6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6767414
Commit-Queue: AbdAlRahman Gad <agad@igalia.com>
Reviewed-by: Max Ihlenfeldt <max@igalia.com>
Reviewed-by: Orko Garai <orko@igalia.com>
Cr-Commit-Position: refs/heads/main@{#1491148}
Roll Chrome Android ARM64 PGO Profile
Roll Chrome Android ARM64 PGO profile from chrome-android64-main-1753298748-2f4961be6467aea99016ec217449eb7a98525b47-8714d8f12abe1e87400105ff3bfdd1a4f2665c1d.profdata to chrome-android64-main-1753302081-6b36eb314dfc7b27e357a958dad5d8248550f93d-ad0a20f5ea51409d569f4e876f2c44ffe868ac0e.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: I894fd953a82c045dfab5a1357c05666fd53adfdd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781983
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@{#1491147}
[TabAlert] Hook up TabAlertController with the glic accessing alert
Hooks up the TabAlertController to subscribe for when glic is accessing
a tab. This allows features to get the active tab alerts through the
alert controller instead of through the TabRendererData.
Fixed: 422748665
Change-Id: Icb8b28e39c40625492659c4aeff4b97ede6d36d1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6765871
Reviewed-by: David Pennington <dpenning@chromium.org>
Commit-Queue: Steven Luong <stluong@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491146}
update rust tests/codegen to tests-codegen-llvm
It was renamed in https://github.com/rust-lang/rust/commit/a27f3e3fd1e4d16160f8885b6b06665b5319f56c
Bug: 433795835
Change-Id: I5b66e5920bb93ea99bcb22c9d3ec0f6cbfcce46b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781882
Commit-Queue: Zequan Wu <zequanwu@google.com>
Reviewed-by: Alan Zhao <ayzhao@google.com>
Cr-Commit-Position: refs/heads/main@{#1491145}
Disable GlicActorControllerUiTest.PauseThenStopActorTask
Bug: 430643846
Change-Id: I0fa4eb4027cfd6288418c0b7056c94b7bf6e1bc6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781014
Auto-Submit: Nick Birnie <birnie@google.com>
Reviewed-by: Kevin McNee <mcnee@chromium.org>
Commit-Queue: Kevin McNee <mcnee@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491144}
ChromeVox: Update syntax when throwing an error
This syntax issue was added during the manifest v3 migration. The
proper syntax is Throw new Error('message').
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/throw#description
Bug: N/A
Change-Id: Ida24fdb23bde7f91ae536d11ba31f72868f50681
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6778802
Reviewed-by: Kyungjun Lee <kyungjunlee@google.com>
Auto-Submit: Akihiro Ota <akihiroota@chromium.org>
Commit-Queue: Kyungjun Lee <kyungjunlee@google.com>
Cr-Commit-Position: refs/heads/main@{#1491143}
Roll Chrome Mac Arm PGO Profile
Roll Chrome Mac Arm PGO profile from chrome-mac-arm-main-1753293557-890a2d9d8b3cbd1c162df5b96a73aabdf96ede1e-130e6845bbaaef3059f8518d8c550d9f4084401f.profdata to chrome-mac-arm-main-1753300775-51765b994e03e6636c589556812c7a4fc8d29a0e-7a00f784447244cdbe8f755ef429c03c5fecd57a.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: I6ad9ff152b294ffed9b0030635c487edec4d27f9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781979
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@{#1491142}
Extend ChromeOS.FirmwareUpdateUI.*.*UpdateCount metrics
Fixed: 433257780
Test: N/A
Change-Id: I1ab97e7587e0696dcf9cb24973f849eabbe47ba1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6773676
Auto-Submit: Jimmy Gong <jimmyxgong@chromium.org>
Commit-Queue: Gavin Williams <gavinwill@chromium.org>
Reviewed-by: Gavin Williams <gavinwill@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491141}
webnn: Rebaseline OptimizationGuideExpectations
Bug: 394119734
Change-Id: I3e0f04752125d37dd997a4eabfb2671f5e9af580
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6778698
Commit-Queue: Phillis Tang <phillis@chromium.org>
Auto-Submit: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Phillis Tang <phillis@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491140}
[SxS] Add side by side field trial config ahead of dogfood
Omitting ChromeOS from dogfood due to test failures. There are two
devtools tests still failing in BrowserViewTest but there is ongoing
migration happening. Will update those tests after that is complete.
There is separate test coverage within that file for side by side.
Change-Id: I2d158653bb7c5b8244c65613fa1652fda0b3c8ad
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6773897
Reviewed-by: Eshwar Stalin <estalin@chromium.org>
Commit-Queue: Alison Gale <agale@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491139}
Make sharing pinned tabs always possible even if not visible.
Sharing of pinned tabs should be always possible even if it's not focused or user has minimized the window, even if the user has blocked the use of general contexts for tabs, that's why it's allowed in case the current shared tab is pinned.
Change-Id: I092a40f1deafd342d9472096829c49aa04ea2d9b
Bug: b:427256654
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781475
Reviewed-by: Michael Crouse <mcrouse@chromium.org>
Reviewed-by: Dan Harrington <harringtond@chromium.org>
Commit-Queue: Michael Crouse <mcrouse@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491138}
Modify MediaPlayerLoggingId to be a int64_t
The player id is sometimes stored as an int64_t, sometimes as an
int32_t. This will now achieve consistency with the generated
SetPlayerId function that is called through the UKM generated code.
Bug: 421435479
Change-Id: I168f0cf1339f46df98cea3e15a9b701b2274c628
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781628
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Commit-Queue: Vikram Pasupathy <vpasupathy@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491137}
Add user-agent client hints browser tests on Android
In order to better prepare the changes on XR devices related to
User-Agent and User-Agent client hints, add some example tests on
Android.
Change-Id: I7fa2184b77e04477ef6e0c8c69497f342ce8b2fe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6778002
Reviewed-by: Mike Taylor <miketaylr@chromium.org>
Commit-Queue: Victor Tan <victortan@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491136}
Create initial APIs for ChromeAndroidTaskFeature
Changes:
(1) Add ChromeAndroidTaskFeature APIs to support syncing its lifecycle
with ChromeAndroidTask:
```
onAddedToTask();
onTaskRemoved();
```
(2) Call those APIs in `ChromeAndroidTaskImpl`.
(3) Add Robolectric tests.
Bug: 431289118
Change-Id: Ic480b19403d390a1ee7b0c5d585ee591a2ad7071
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6758154
Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Commit-Queue: Linyu He <linyuh@google.com>
Cr-Commit-Position: refs/heads/main@{#1491135}