Chromium Main Console
| Legend: | Passed | Failed | Running | Exception |
Add Installer attributes for GPU/CPU class.
Bug: 428039852
Change-Id: I93589eef4728c804f795f905b8df87553dad48fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6803281
Reviewed-by: Joshua Pawlicki <[email protected]>
Commit-Queue: Steven Holte <[email protected]>
Reviewed-by: Clark DuVall <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495244}
[DX12 Enc] Set coded size alignment to 2 for D3D12 VEA.
H.264 requires coded size to be 2-aligned. By spec H.265 allows odd
coded size but this adds complexity to input texture handling,
expecially when input texture needs go through VP for pixel format
conversion, which IHV D3D12 VP may not handle cropping correctly. For
AV1, since render_size syntax is not for cropping purpose, there is no
way to instruct decoder about visible rect.
As a result, we follow MF VEA's approach to announce support 2-aligned
coded size only.
WebCodecs in blink only blocks non-2-aligned encoding request for H.264
. There should be a way to convey the limitation at MediaCapability
API level, which is not within the scope of this CL.
Bug: 40275246
Change-Id: Ia86e8973ac8a64c66cbb3112fbf6d36de0cb4ef4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6805168
Commit-Queue: Jianlin Qiu <[email protected]>
Reviewed-by: Eugene Zemtsov <[email protected]>
Reviewed-by: Sergey Silkin <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495243}
Android: remove references to weblayer
No change to logic. WebLayer is no longer supported so we can remove
references to this project.
Bug: 40272607
Test: autoninja system_webview_apk trichrome_webview_apk
Change-Id: Ia5108a8178339c468abd45e33d123482ef8e2827
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6807225
Auto-Submit: Nate Fischer <[email protected]>
Reviewed-by: Dominic Battré <[email protected]>
Commit-Queue: Dominic Battré <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495242}
Roll Updater chromium_win_x86_64 from 2@1491001 to 2@1495038
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/updater-chromium-win-x86-64-chromium
Please CC [email protected],[email protected] 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: [email protected]
Change-Id: I2c2491fc3db558ec9ee075ffd0324f7f19f8d0cf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6808135
Bot-Commit: chromium-autoroll <[email protected]>
Commit-Queue: chromium-autoroll <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495241}
Roll Chrome Mac Arm PGO Profile
Roll Chrome Mac Arm PGO profile from chrome-mac-arm-main-1754005981-79631c2dcedb56c30e83abe4c2447817d1d05c40-1472d1bc9adbbc7279d1446f0abe4e505570da8a.profdata to chrome-mac-arm-main-1754013452-fa1c0847cd7163549dd7c4a2457c5c6f9596870d-7d5f750db0ae836036c8c1f3b4c1ae39d05d0ea9.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 [email protected],[email protected] 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: [email protected]
Merge-Approval-Bypass: Chrome autoroller
Change-Id: If28597d9d02af79187c7610baee63c88a10a6da2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6808881
Commit-Queue: chromium-autoroll <[email protected]>
Bot-Commit: chromium-autoroll <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495240}
Roll clank/internal/apps from 4fde0b9650fd to c84d41b2ac78 (1 revision)
https://chrome-internal.googlesource.com/clank/internal/apps.git/+log/4fde0b9650fd..c84d41b2ac78
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 [email protected] 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:
No-Try: true
Change-Id: Ifc1fc79f45b42087596f0b002b1c8aa84f37cd53
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6809549
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@{#1495239}
Roll DevTools Frontend from c4b03ebbbdd7 to 96c7979dd12e (1 revision)
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/c4b03ebbbdd7..96c7979dd12e
2025-08-01 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update Chrome (for Testing) PIN
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/devtools-frontend-chromium
Please CC [email protected] 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: I082adc8621d986631a3841329cd661a94b71a472
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6809745
Commit-Queue: chromium-autoroll <[email protected]>
Bot-Commit: chromium-autoroll <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495238}
Roll Chrome Android ARM64 PGO Profile
Roll Chrome Android ARM64 PGO profile from chrome-android64-main-1754009601-0ea1e80cde38466a8c6f9f7f9017016b3a569318-bfb4bc46e223f92a8ab9d1235dc33ff6584972b5.profdata to chrome-android64-main-1754015172-1b803716623acd9bf14d6641f1b6acb2f22e32c6-274417bceddff4e68594787065511c2b114a4bb9.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 [email protected],[email protected] 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: [email protected]
Merge-Approval-Bypass: Chrome autoroller
Change-Id: I1ab5f0b7d815baa1499a892b5bf297e6dde8db19
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6809587
Commit-Queue: chromium-autoroll <[email protected]>
Bot-Commit: chromium-autoroll <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495237}
Bugfix and Cleanup in ManagedPreferencesUtils
Previous changes left this code slightly wrong, legacy case was handling unfollowed recommended preferences. This change fixes that and leaves only custom preferences and custodians on the legacy path. Also added more commenting to make this clearer.
Bug: 429018995
Bug: 400800634
Bug: 400804628
Change-Id: Ia273d7c9e605959ea183f6edf898c65d254aa964
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6803334
Reviewed-by: Wenyu Fu <[email protected]>
Commit-Queue: Jack Thiesen <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495236}
Roll Updater chromium_linux64 from 2@1491002 to 2@1495011
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/updater-chromium-linux64-chromium
Please CC [email protected],[email protected] 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: [email protected]
Change-Id: I6f360aac934bce4faa1ae39c217809b877a9f7dc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6808820
Bot-Commit: chromium-autoroll <[email protected]>
Commit-Queue: chromium-autoroll <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495235}
Roll Chrome Win ARM64 PGO Profile
Roll Chrome Win ARM64 PGO profile from chrome-win-arm64-main-1753984643-2d9b0172080dc3c51a908c33cad2e3cf9d619714-739f10b7f26e3db54704550f0cea4efc11e28c37.profdata to chrome-win-arm64-main-1754005981-1f2c30daba65f0ae59b864d000f0442c1a15ed10-1472d1bc9adbbc7279d1446f0abe4e505570da8a.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 [email protected],[email protected] 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: [email protected]
Merge-Approval-Bypass: Chrome autoroller
Change-Id: Iab0250158ee2394eb1dc1e824d949c95a96c199d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6809545
Commit-Queue: chromium-autoroll <[email protected]>
Bot-Commit: chromium-autoroll <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495234}
Boost cpu priority of discarding renderer processes
With WebContentsDiscard feature, discarding frames are done by blink
running on the renderer process for the main frame of the discarding
page. Boosting process priority of the main frame renderer process is
critical to the discard latency. This is significant on ChromeOS in
which background renderer processes has only 1% of cpu.shares from cpu
cgroups.
Delay of discard latency results in more critical memory pressure
signals and more tab discarding.
Bug: 432390949
Change-Id: I8390836884eb33d9c7b0ea0926e9980e387dd01f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6796029
Commit-Queue: Shin Kawamura <[email protected]>
Reviewed-by: Tom Lukaszewicz <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495233}
Roll Chrome Android ARM64 Orderfile from 6Md-2cHZdyUZbQgCq... to igSgbfFUiZAaiwKZb...
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 [email protected],[email protected] 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: [email protected]
Merge-Approval-Bypass: Chrome autoroller
Change-Id: I52fe11605aad2ff555e729894d1d1da2105b797a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6809586
Commit-Queue: chromium-autoroll <[email protected]>
Bot-Commit: chromium-autoroll <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495232}
Roll Chrome Win64 PGO Profile
Roll Chrome Win64 PGO profile from chrome-win64-main-1753984643-9ce830037d157f6ffbdf3b3492c53e4ed45ad6a2-739f10b7f26e3db54704550f0cea4efc11e28c37.profdata to chrome-win64-main-1753995572-cb5086c57b1d0335f1548bc774a03e827c57959a-b87085002112c8d70f73ae8dc2f3112d06fc4105.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 [email protected],[email protected] 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: [email protected]
Merge-Approval-Bypass: Chrome autoroller
Change-Id: I2a45b291c8db60b945de0716868570f5c85874c1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6808437
Commit-Queue: chromium-autoroll <[email protected]>
Bot-Commit: chromium-autoroll <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495231}
[PA] Propose "ExternalMetadata" synthetic finch trials if enabled
If `enable_move_metadata_outside_gigacage_trial`(gn var) is true,
propose synthetic finch trials: 10% enabled and 10% disabled(control).
Design Doc:
https://docs.google.com/document/d/1Mn-qRAWuDhS_gRL_OG2TYL-EW5D8yljaCyM40S0ocVc/edit?tab=t.0
Bug: crbug.com/435341877
Change-Id: Ib0987efc576d4ba797bed119e18dd595e4d807f7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6795727
Reviewed-by: Yuki Shiino <[email protected]>
Commit-Queue: Takashi Sakamoto <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495230}
Roll Amd64 AFDO from 140.0.7327.0_pre1493754_rc-r1-merged to 140.0.7330.0_pre1494797_rc-r1-merged
This CL may cause a small binary size increase, roughly proportional
to how long it's been since our last AFDO profile roll. For larger
increases (around or exceeding 100KB), please file go/crostc-bug.
Please note that, despite rolling to chrome/android, this profile is
used for both Linux and Android.
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/afdo-chromium
Please CC [email protected],[email protected] on the revert to ensure that a human
is aware of the problem.
To file a bug in Chromium Main: 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: [email protected]
Merge-Approval-Bypass: Chrome autoroller
Change-Id: I08efd835f66e75f6e43ce9c0f146be554c505327
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6808818
Bot-Commit: chromium-autoroll <[email protected]>
Commit-Queue: chromium-autoroll <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495229}
Roll Chrome Mac PGO Profile
Roll Chrome Mac PGO profile from chrome-mac-main-1753984643-76bb98111c1ab01e1538e62047b21c21c7c9ad61-739f10b7f26e3db54704550f0cea4efc11e28c37.profdata to chrome-mac-main-1754005981-7a703d78adafc020cf93fa6c9287c6379ee095f3-1472d1bc9adbbc7279d1446f0abe4e505570da8a.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 [email protected],[email protected] 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: [email protected]
Merge-Approval-Bypass: Chrome autoroller
Change-Id: Iae82e89677f8a7c6941fd2ee77978a5f26576b10
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6808329
Commit-Queue: chromium-autoroll <[email protected]>
Bot-Commit: chromium-autoroll <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495228}
Roll Chrome Android ARM64 PGO Profile
Roll Chrome Android ARM64 PGO profile from chrome-android64-main-1754004759-dcf498a6609e6fd6c45a32e812c05b64228e3846-2d344d8ece18959de7a5b4ea9efc41cbbf84c98c.profdata to chrome-android64-main-1754009601-0ea1e80cde38466a8c6f9f7f9017016b3a569318-bfb4bc46e223f92a8ab9d1235dc33ff6584972b5.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 [email protected],[email protected] 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: [email protected]
Merge-Approval-Bypass: Chrome autoroller
Change-Id: I3301fff787ae2c9c5f71060cfe2db75d22ed378b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6808448
Bot-Commit: chromium-autoroll <[email protected]>
Commit-Queue: chromium-autoroll <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495227}
Roll Chrome Android ARM32 Orderfile from _YL2zhs0P_79KiVZP... to Lh0XWtYoLIW9B5gmA...
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-arm32-chromium
Please CC [email protected],[email protected] 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: [email protected]
Merge-Approval-Bypass: Chrome autoroller
Change-Id: I5ebb0937a6002c6f69bf5e5bac40afe26c383f35
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6807915
Bot-Commit: chromium-autoroll <[email protected]>
Commit-Queue: chromium-autoroll <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495226}
Updating trunk VERSION from 7331.0 to 7332.0
* This is an automated release commit.
* Do not revert without consulting [email protected].
NOAUTOREVERT=true
Change-Id: I86a1a185bd918806da5cd0e7c9b4197fa76d1708
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6808819
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1495225}
Reland "Capture hit order in AccessibilityNodeInfo for use in Android XR"
This is a reland of commit 3e3ed18252a15de50676d25fd0ced26c439e05d6
Fixing build break when enable_vr=false.
AX-Relnotes: On Android XR, this will fix occlusion issues. On other
AX-Relnotes: platforms should have no effect.
Original change's description:
> Capture hit order in AccessibilityNodeInfo for use in Android XR
>
> In Android XR we have a need to tell, when two accessibility nodes
> overlap, which one is on top, in order to render system hover effects
> correctly. This change attempts to capture the hit order during the
> painting process in the Blink renderer and then pass that on to be
> included in the accessibility extras.
>
> In order to capture the z order across all frames rendered by a single
> renderer process, we capture the CompositorElementIds of all nodes
> passed to PaintChunker::AddHitTestDataToCurrentChunk() and pass them
> through to the cc::Layers, and then finally I use the layer tree to
> compute the final z order values and attach them to the
> AXObjects.
>
> The expensive steps of this process are all protected by platform
> checks to try to eliminate any perf impact on non-XR platforms.
>
> Bug: 410670957
>
> AX-Relnotes: On Android XR, this will fix occlusion issues. On other
> AX-Relnotes: platforms should have no effect.
>
> Test: Loaded up various websites on XR device including Naver.com
> Test: and confirmed that order was as expected. Some small issues
> Test: that appear as the content changes dynamically over time.
> Test: Also ran new test:
> Test: autoninja -C out/Debug content_shell_test_apk && out/Debug/bin/run_content_shell_test_apk --test-filter
> org.chromium.content.browser.accessibility.WebContentsAccessibilityTest#testNodeInfo_extraDataAdded_paintOrder
> Test: Also ran all other WebContentsAccessibilityTest tests.
>
> Change-Id: Ice4e67df7337c2bbda1e20ee474846b61b52c0e6
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6518162
> Reviewed-by: Mark Schillaci <[email protected]>
> Reviewed-by: Philip Rogers <[email protected]>
> Commit-Queue: Chiara Coetzee <[email protected]>
> Cr-Commit-Position: refs/heads/main@{#1494938}
Bug: 410670957
Change-Id: I13f74a9b25658a08fe008d2ee0d5ea9cd1519308
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6806931
Reviewed-by: Stefan Zager <[email protected]>
Reviewed-by: Mark Schillaci <[email protected]>
Commit-Queue: Chiara Coetzee <[email protected]>
Reviewed-by: Matthew Denton <[email protected]>
Reviewed-by: Philip Rogers <[email protected]>
Reviewed-by: Alexander Cooper <[email protected]>
Reviewed-by: Yaron Friedman <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495224}
Roll Chrome Win32 PGO Profile
Roll Chrome Win32 PGO profile from chrome-win32-main-1753973894-18936bb1e43ebdbe47172c87e6f542fea8841f66-c9533bc9b264b16d981279e48012260a19ecb774.profdata to chrome-win32-main-1753984643-35a68821a6616d49a5e282df39fe0c1f455ed20c-739f10b7f26e3db54704550f0cea4efc11e28c37.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 [email protected],[email protected] 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: [email protected]
Merge-Approval-Bypass: Chrome autoroller
Change-Id: Icaf812e922823fb9dbf2213350bb951fd67b0b0c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6807923
Commit-Queue: chromium-autoroll <[email protected]>
Bot-Commit: chromium-autoroll <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495223}
[ios] Enable AutofillAllowDefaultPreventedSubmission by default
Change-Id: I9bd7b232dc1a3c0b9d4bef365631a4bafc9634e1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6806118
Reviewed-by: Noémie St-Onge <[email protected]>
Commit-Queue: Vincent Boisselle <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495222}
[wpt-importer] Skip export for https://crrev.com/c/6794665
An identical patch was landed in both GitHub and chromium/src, causing
the latter to not apply cleanly on web-platform-tests/wpt@master. The
workaround detailed in [0] fixed the exporter, but not the importer,
which also looks for a matching `Change-Id` footer in the GitHub repo's
commit messages to avoid clobbering in-flight exportable CLs.
Fall back to the procedure documented in [1].
[0]: https://crrev.com/c/6794665/comments/3f93724b_1ba128a7
[1]: https://github.com/Ecosystem-Infra/ecosystem-infra-rotation/blob/d5cf828ca6fd4767e27acb46b2577c70c8aca63f/docs/import.md?plain=1#L65-L72
Bug: None
Change-Id: I448065fe2b283afc60bd5d4a1ea2632ae72e0513
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6808509
Commit-Queue: Brian Sheedy <[email protected]>
Reviewed-by: Brian Sheedy <[email protected]>
Auto-Submit: Jonathan Lee <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495221}
Roll Chrome Mac Arm PGO Profile
Roll Chrome Mac Arm PGO profile from chrome-mac-arm-main-1753991944-fb025a6155b0da5a28c414877f6360c50c1a5526-6beacdf983876716847712078372fc4a1f0d8cd4.profdata to chrome-mac-arm-main-1754005981-79631c2dcedb56c30e83abe4c2447817d1d05c40-1472d1bc9adbbc7279d1446f0abe4e505570da8a.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 [email protected],[email protected] 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: [email protected]
Merge-Approval-Bypass: Chrome autoroller
Change-Id: I0df2ff5ca28c3cec497d4400689a9b5f910dac26
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6808443
Commit-Queue: chromium-autoroll <[email protected]>
Bot-Commit: chromium-autoroll <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495220}
Roll WebRTC from d26ff678906f to 656f65baf74b (1 revision)
https://webrtc.googlesource.com/src.git/+log/d26ff678906f..656f65baf74b
2025-08-01 [email protected] Roll chromium_revision 3566b11a24..bc83480c62 (1495033:1495169)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/webrtc-chromium-autoroll
Please CC [email protected],[email protected] on the revert to ensure that a human
is aware of the problem.
To file a bug in WebRTC: https://bugs.chromium.org/p/webrtc/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: [email protected]
Change-Id: I6a83e1808a1065289ad8ed1fc2ab9ddcf22039af
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6808878
Bot-Commit: chromium-autoroll <[email protected]>
Commit-Queue: chromium-autoroll <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495219}
Roll Chrome Android ARM64 Orderfile from Ma0T6sb3IsZp5ogps... to 6Md-2cHZdyUZbQgCq...
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 [email protected],[email protected] 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: [email protected]
Merge-Approval-Bypass: Chrome autoroller
Change-Id: I6f47a4863725a868e4cadfd3145e691750e0a5a5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6808877
Commit-Queue: chromium-autoroll <[email protected]>
Bot-Commit: chromium-autoroll <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495218}
Update libcxx headers. They have gone out of date again.
Bug: 432582032
Change-Id: I6a6a6964aebdc11b598d965b738181185e203aae
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6808676
Reviewed-by: Takuto Ikuta <[email protected]>
Commit-Queue: Takuto Ikuta <[email protected]>
Auto-Submit: Matt Stark <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495217}
Roll Chrome Android Desktop x64 PGO Profile
Roll Chrome Android Desktop x64 PGO profile from chrome-android-desktop-x64-main-1753984643-ba5ac4b131498617b08b8c64694bd60b093cced3-739f10b7f26e3db54704550f0cea4efc11e28c37.profdata to chrome-android-desktop-x64-main-1754005981-d01af00a61a7b48ad496ffe5a2bf8fa71c48f100-1472d1bc9adbbc7279d1446f0abe4e505570da8a.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 [email protected],[email protected] 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: [email protected]
Merge-Approval-Bypass: Chrome autoroller
Change-Id: Ibd963b65e37c66d7bb85c235a5a43542050b9670
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6808876
Commit-Queue: chromium-autoroll <[email protected]>
Bot-Commit: chromium-autoroll <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495216}
Extensions: Improve validation of icon variants relative paths
Extension icons are specified in the extension's manifest as relative
paths. These paths are validated in the `Extension::GetResource`
function to make sure they're indeed relative, don't contain invalid
characters, etc., but it's not always used, allowing such non-conforming
paths to propagate to other parts of the code.
Improve the icon variant utils to always use `Extension::GetResource`
instead of using the raw paths that are specified in the manifest.
Bug: 407932132
Change-Id: I24cf74683636fbc6f2e7be25fd29ec5c83078143
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6730255
Commit-Queue: Michael Maltsev (R&D) <[email protected]>
Reviewed-by: Solomon Kinard <[email protected]>
Reviewed-by: Devlin Cronin <[email protected]>
Reviewed-by: Oliver Dunk <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495215}
Add ASR Streaming functions to OnDevice Model Session.
Adds ASR streaming support to an on-device session. Supports
streaming audio chunks and receiving transcription results.
Change-Id: Ibd8a8ead3cda9e552ea9397a82200876bee9750d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6725434
Reviewed-by: Tom Sepez <[email protected]>
Reviewed-by: Clark DuVall <[email protected]>
Commit-Queue: Brad Triebwasser <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495214}
[BD][HandoffButton] Fix button flicker when hovering near overlay.
This CL fixes this by:
1. adding a hover target on the button: A new HandoffButtonWidget
subclass of views::Widget overrides OnMouseEvent. this tracks mouseEnter
and mouseLeave so that we are visible when the mouse is.
2. adding a debouncer when calling UpdateState: A cancellable timer in
ActorUiTabController now calls any updates on UI components. This
provides a grace period for all calls, especially this one on the button
visibility that prevents the UI from flickering during rapid mouse
transitions around the edge of the border where the overlay ends and the
button begins, and vice versa.
3. removing tab_active_state param from UpdateState: The previous logic
could make UI decisions based on a stale tab_active_status that was
captured when the update was scheduled. The controller now queries the
tab for its current active status when the update runs to prevent race
conditions.
updated screencast:
https://screencast.googleplex.com/cast/NTc1NTY0NzMyNzk5Mzg1NnwxYTY1OTM4ZS04Ng
Bug: b:422541242, b:422540637
Change-Id: I39cc84b23f6ed7d3255270b1646d4f8e635c9aba
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6802260
Reviewed-by: Jacob Stanley <[email protected]>
Commit-Queue: Michelle Abreo <[email protected]>
Reviewed-by: Kevin Graney <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495213}
Partially Reland "Automatically generate libcxx headers as a hook."
This reverts commit 920adc8f1cf65a63043776e2192bd6ce5819cd31.
Reason for revert: Safe partial revert which fixes the bug introduce in
the original commit.
Bug: 432582032
Original change's description:
> Revert "Automatically generate libcxx headers as a hook."
>
> This reverts commit f757979abb319cab03a3a040b5fd288f06edf6ad.
>
> Reason for revert:
> This broke Cider-G
> https://chromium-review.googlesource.com/c/chromium/src/+/6768520/comments/13bb2d1d_3e90a250
>
> Bug: 432582032
> Original change's description:
> > Automatically generate libcxx headers as a hook.
> >
> > I'm explicitly choosing not to do anything with it yet, to make for a simpler rollback if it doesn't go well.
> >
> > In a follow-up CL, I will delete libcxx_headers.gni and replace all
> > references to it to the generated version.
> >
> > Bug: 432582032
> > Change-Id: I6a6a6964d84cab9d121fbfe0da227c8237953f0c
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6768520
> > Auto-Submit: Matt Stark <[email protected]>
> > Reviewed-by: Junji Watanabe <[email protected]>
> > Reviewed-by: Takuto Ikuta <[email protected]>
> > Commit-Queue: Matt Stark <[email protected]>
> > Reviewed-by: Brian Ryner <[email protected]>
> > Cr-Commit-Position: refs/heads/main@{#1494567}
>
> Bug: 432582032
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Change-Id: I24d90a747e6bd37353856d13b34c797f9ba9a72c
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6805053
> Commit-Queue: Takuto Ikuta <[email protected]>
> Bot-Commit: Rubber Stamper <[email protected]>
> Cr-Commit-Position: refs/heads/main@{#1494660}
Bug: 432582032
Change-Id: Ia6ff26c7248a90b75ed25fe9fb0fc53e69535782
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6808195
Reviewed-by: Takuto Ikuta <[email protected]>
Commit-Queue: Matt Stark <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495212}
Preload: Add BookmarkTriggerForPreconnect in field trial config
Bug: 413259638
Change-Id: Ia99a6333a5a1a276392a96c65cf90806674973d9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6797512
Commit-Queue: Huanpo Lin <[email protected]>
Reviewed-by: Shunya Shishido <[email protected]>
Reviewed-by: Hiroki Nakagawa <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495211}
Fix ESLint 'no-var', 'prefer-const' violations in c/renderer/resources.
This is in preparation of turning on PRESUBMIT checks for this folder.
Bug: 433671012
Change-Id: I0b8376962b57766a028d7345f409be96669b8e28
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6795070
Reviewed-by: Devlin Cronin <[email protected]>
Reviewed-by: Robbie McElrath <[email protected]>
Commit-Queue: Demetrios Papadopoulos <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495210}
Roll Chrome Android ARM32 PGO Profile
Roll Chrome Android ARM32 PGO profile from chrome-android32-main-1753984643-1edb7491b4456274d5bf8b861525a330d93c3db7-739f10b7f26e3db54704550f0cea4efc11e28c37.profdata to chrome-android32-main-1754005981-91ff8971836b6a317a5e095c1bd38a3e2bad9577-1472d1bc9adbbc7279d1446f0abe4e505570da8a.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-arm32-chromium
Please CC [email protected],[email protected] 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: [email protected]
Merge-Approval-Bypass: Chrome autoroller
Change-Id: I9ee66a72570c2db5ccf14c8f836532076291e97f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6808331
Commit-Queue: chromium-autoroll <[email protected]>
Bot-Commit: chromium-autoroll <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495209}
[TaskIcon] Reset task icon when task is active
Bug: 422442801
Change-Id: I2e962b66aabb5c63e62f75d9f69a2d6b1e173c4c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6807015
Commit-Queue: Maggie Jennings <[email protected]>
Auto-Submit: Maggie Jennings <[email protected]>
Reviewed-by: Mark Foltz <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495208}
Roll WebRTC from be1d925be37f to d26ff678906f (1 revision)
https://webrtc.googlesource.com/src.git/+log/be1d925be37f..d26ff678906f
2025-07-31 [email protected] Reformat gn files
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/webrtc-chromium-autoroll
Please CC [email protected],[email protected] on the revert to ensure that a human
is aware of the problem.
To file a bug in WebRTC: https://bugs.chromium.org/p/webrtc/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: [email protected]
Change-Id: I8ff645b940b1122bd9f735d7a5b7b2d5146c0a54
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6808330
Commit-Queue: chromium-autoroll <[email protected]>
Bot-Commit: chromium-autoroll <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495207}
Roll Chrome Android ARM64 PGO Profile
Roll Chrome Android ARM64 PGO profile from chrome-android64-main-1753997452-eb7972faa61636822cabf1aa7823c53d8a2d05aa-7dee5535e402a7fe0fbafa00724570cd5337fb01.profdata to chrome-android64-main-1754004759-dcf498a6609e6fd6c45a32e812c05b64228e3846-2d344d8ece18959de7a5b4ea9efc41cbbf84c98c.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 [email protected],[email protected] 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: [email protected]
Merge-Approval-Bypass: Chrome autoroller
Change-Id: If391477115590ff6638f73303cedffb3c4a0e386
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6808327
Bot-Commit: chromium-autoroll <[email protected]>
Commit-Queue: chromium-autoroll <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495206}
Roll ios_internal from e733c5ec5c24 to f709c1a086fc
https://chrome-internal.googlesource.com/chrome/ios_internal.git/+log/e733c5ec5c24..f709c1a086fc
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://skia-autoroll.corp.goog/r/ios-internal-chromium-autoroll
Please CC [email protected],[email protected] 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:434662294
Change-Id: Iaff21624dd8282b5bb2df49831ccd9c29ba2e3bb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6807751
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@{#1495205}
Roll Chromium Variations from KlD4b_8YKsvHOKLFt... to Qta3KtD5sSY3myzbR...
https://chrome-infra-packages.appspot.com/p/chromium/chrome/test/data/variations/cipd/+/Qta3KtD5sSY3myzbReTurm7U_BO4uwNiSThu-4_UT_IC
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 [email protected] 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: [email protected]
Change-Id: I2c4d25df0d7fd4b79fe38cfb9d61522b5769aad0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6808438
Commit-Queue: chromium-autoroll <[email protected]>
Bot-Commit: chromium-autoroll <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495204}
webium: introduce chrome://webui-browser
This is a skeleton WebUI with basic set up, such as html/css/ts.
screenshot:
https://drive.google.com/file/d/1jDyT8ejsdIulhQ080TTYdjK97NvtMrQb/view?usp=sharing
Bug: 393144165
Change-Id: I0a537f463cc7d72a907974b220c136fdca311b6d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6802568
Reviewed-by: Demetrios Papadopoulos <[email protected]>
Commit-Queue: Keren Zhu <[email protected]>
Reviewed-by: Tom Lukaszewicz <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495203}
Roll Chrome Android ARM64 Orderfile from TzumDm3s_fOXQfARy... to Ma0T6sb3IsZp5ogps...
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 [email protected],[email protected] 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: [email protected]
Merge-Approval-Bypass: Chrome autoroller
Change-Id: Ic7603e050f8f4598d9c1b7f28b8c2592b9584f4d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6808462
Bot-Commit: chromium-autoroll <[email protected]>
Commit-Queue: chromium-autoroll <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495202}
Add param to Max Display supported notification
This change adds a required field to the display notification feature.
Without setting number of display, the feature cannot be enabled.
This also changes the name of MaximumDisplaySupportedNotification to
MaxExternalDisplaySupportedNotification to avoid confusion with
internal display.
Bug: b:425437937,b:433318990
Change-Id: Ia5693dbfa056a66b55b4833e4b7d0ede55818b97
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6807216
Reviewed-by: Xiyuan Xia <[email protected]>
Commit-Queue: Vincent Chiang <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495201}
MemoryCache: Ensure ClearStrongReferences clears the tiered cache
ClearStrongReferences() didn't clear the `tiered_strong_references_`
vector used by the `kMemoryCacheIntelligentPruning` feature. This caused
state leakage in tests calling EvictResources(), leading to failures.
This change adds the missing `.clear()` call to correctly clear all
strong references, fixing the tests.
Bug: 432275223
Change-Id: I1695fa3005e966113583d950a4a1cd948295b435
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6806164
Reviewed-by: Kouhei Ueno <[email protected]>
Commit-Queue: Kouhei Ueno <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495200}
magic-boost: fix cropped settings icon
This CL modifies:
* Make the container that contains the icon and the magic boost header a box layout instead of flex layout with min_width scale to zero and max width unbounded.
- In narrow width, this container can shrink to 0, preserving the settings icon not to go off-screen.
- In normal/wide width, this container extends limitlessly, pushing the settings icon to the right.
* Adds some more margins around the settings / gear icon.
Fixed: b:435217549
Change-Id: I87f2508fd64e35e604af66bc8e34dc8c61983d37
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6804222
Reviewed-by: Yuki Awano <[email protected]>
Commit-Queue: Chuong Ho <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495199}
Roll WebRTC from 6b9333ad21b1 to be1d925be37f (3 revisions)
https://webrtc.googlesource.com/src.git/+log/6b9333ad21b1..be1d925be37f
2025-07-31 [email protected] Remove obsolete ubsan suppression
2025-07-31 [email protected] Roll chromium_revision fb179e390b..3566b11a24 (1494868:1495033)
2025-07-31 [email protected] Provide transitional opt accessor to RTCConfiguration.crypto_options
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/webrtc-chromium-autoroll
Please CC [email protected],[email protected] on the revert to ensure that a human
is aware of the problem.
To file a bug in WebRTC: https://bugs.chromium.org/p/webrtc/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: [email protected]
Change-Id: Ic4267925c7e39a0d6ce4bba52a0ea31e6c08dcda
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6808318
Commit-Queue: chromium-autoroll <[email protected]>
Bot-Commit: chromium-autoroll <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495198}
Remove deprecated dbus::ObjectProxy::CallMethodWithErrorCallback()
R=hashimoto
Bug: 41328956
Change-Id: Iac68aa0101b11d62992efefad7bb1af1a97e934e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6799255
Reviewed-by: Ryo Hashimoto <[email protected]>
Commit-Queue: Thomas Anderson <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495197}
[Desktop Android] Compile multiple extension uninstallation dialog
This CL does the following:
- It implements the extension multiple uninstallation dialog for Android by using the tab modal dialog.
- Moves the extension multiple uninstallation dialog to the extensions
folder and out of /views.
Bug: 434755940
Change-Id: If3c18309f4ccaab009ee40404e7d8cd225efbdb9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6798763
Reviewed-by: Emilia Paz <[email protected]>
Reviewed-by: Shuhei Takahashi <[email protected]>
Commit-Queue: Eva Su <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495196}
[WebAudio] Remove interrupted state feature flag
The "interrupted" state was shipped in M136. No issues have been raised
so far. It should be safe to remove the feature flag.
ChromeStatus: https://chromestatus.com/feature/5172068166139904
Bug: 374805121
Change-Id: Ia28e1f0c0834289eafac9488f524d5b8098fa48e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6799134
Reviewed-by: Hongchan Choi <[email protected]>
Commit-Queue: Gabriel Brito <[email protected]>
Reviewed-by: Michael Wilson <[email protected]>
Reviewed-by: Dan Clark <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1495195}