Browse 50 recent commits with full metadata
[ios] Remove obsolete SceneStatePrefs migration The migration to ProfileAttributesIOS has shipped for five milestones. Remove the legacy migration instead of accessing UISceneSession.userInfo, which can cause UIKit to persist scene restoration data on the main thread. Bug: 519105565 Change-Id: I0803338fb8b59fdeb65baebe694a4248f840bb19 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8534788 Reviewed-by: Sylvain Defresne <sdefresne@chromium.org> Reviewed-by: Gauthier Ambard <gambard@chromium.org> Commit-Queue: Ning Sun <ningsun@microsoft.com> Cr-Commit-Position: refs/heads/main@{#1715132}
Roll BoringSSL from cee89849ad5e to 44979b8a96e4 (2 revisions) https://boringssl.googlesource.com/boringssl.git/+log/cee89849ad5e..44979b8a96e4 2026-10-08 mattm@google.com Add MTC draft plants-07 support (for pki/). 2026-10-08 chlily@google.com Define V_ASN1_RELATIVE_OID tag number If this roll has caused a breakage, revert this CL and set the roller to dry run mode using the controls here: https://autoroll.skia.org/r/boringssl-chromium Please CC boringssl-cabal@google.com,boringssl-reviews@google.com on the revert to ensure that a human is aware of the problem. To file a bug in BoringSSL: https://crbug.com/boringssl/new To file a bug in Chromium: https://crbug.com/new 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: boringssl-reviews@google.com Submodule-Gn-Analyze: true Change-Id: I6bfcab226233b866442c58206d482468f434e249 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8543710 Bot-Commit: chromium-autoroll@skia-public.iam.gserviceaccount.com <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll@skia-public.iam.gserviceaccount.com <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1715131}
Roll Enterprise Companion chromium_mac_arm64 from igR7izJQf6lbwSNAl... to Vg7voq1po4fSdp2fn... If this roll has caused a breakage, revert this CL and set the roller to dry run mode 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: Icd17cc046887851499fe3b21e4ef81fb9570a8c3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8544133 Bot-Commit: chromium-autoroll@skia-public.iam.gserviceaccount.com <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll@skia-public.iam.gserviceaccount.com <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1715130}
Roll Enterprise Companion chromium_mac_amd64 from RusDY50OfRh7SyU_p... to NF6xk3aHYhbqd2xIh... If this roll has caused a breakage, revert this CL and set the roller to dry run mode 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: Ia6123a7195f32ec8be0476fc0df5a6ebbddf3b53 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8544033 Bot-Commit: chromium-autoroll@skia-public.iam.gserviceaccount.com <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll@skia-public.iam.gserviceaccount.com <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1715129}
Support 'auto' tracking mode for Android window occlusion Introduce 'auto' mode for the AndroidWindowOcclusion tracking_mode feature parameter. When 'auto' is selected, Chrome uses the new strict TrustedPresentationListener API if supported on the platform; otherwise, it automatically falls back to self_occlusion mode. This allows enabling the Finch experiment broadly without disabling occlusion tracking on older Android versions where the strict API is unavailable. Bug: 408975278 Change-Id: I6c8f7d5d0e68b9d4674a62065885ed7cb06971e0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8535354 Auto-Submit: Lepton Wu <lepton@chromium.org> Reviewed-by: Bo Liu <boliu@chromium.org> Reviewed-by: Kameron Lutes <kalutes@google.com> Commit-Queue: Lepton Wu <lepton@chromium.org> Reviewed-by: Theresa Wellington <twellington@chromium.org> Cr-Commit-Position: refs/heads/main@{#1715128}
No metadata found
Remove i18n tests from content_shell.filter The following tests run on headless shell and can be removed from content_shell.filter: external/wpt/css/css-text/i18n/ja/css-text-line-break-ja-in-loose.html external/wpt/css/css-text/i18n/ja/css-text-line-break-ja-pr-normal.html external/wpt/css/css-text/i18n/ja/css-text-line-break-ja-pr-strict.html external/wpt/css/css-text/i18n/other-lang/css-text-line-break-de-in-loose.html external/wpt/css/css-text/i18n/unknown-lang/css-text-line-break-in-loose.html external/wpt/css/css-text/i18n/zh/css-text-line-break-zh-in-loose.html external/wpt/css/css-text/i18n/zh/css-text-line-break-zh-pr-normal.html external/wpt/css/css-text/i18n/zh/css-text-line-break-zh-pr-strict.html Bug: 526667990 Change-Id: I8457ac832fd2975b2d5c439bb75503d0c87edfed Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8542196 Commit-Queue: Sharon Yang <yangsharon@igalia.com> Reviewed-by: Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/main@{#1715126}
Move LoadingPredictorTabHelper from AttachTabHelpers to TabFeatures Convert predictors::LoadingPredictorTabHelper from WebContentsUserData to ScopedUnownedUserData<LoadingPredictorTabHelper> owned by Desktop and Android TabFeatures, and recreate it on tab discard in TabFeatures::WillDiscardContents. Bug: 540709814 Agent-Generated: true Change-Id: Idbcd5bb3eea383c4984865e98f85ae2c4c496bc0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8537174 Reviewed-by: Thomas Lukaszewicz <tluk@chromium.org> Reviewed-by: Erik Chen <erikchen@chromium.org> Commit-Queue: Erik Chen <erikchen@chromium.org> Cr-Commit-Position: refs/heads/main@{#1715125}
Remove expired show-spatial-audio-toggle flag and kShowSpatialAudioToggle The feature kShowSpatialAudioToggle has been enabled by default since M138 and its chrome://flags entry expired in M140. Remove the flag entry, feature definition, WebUI loadTimeData boolean, and redundant test override. Bug: 563193206 Test: CQ Change-Id: I386b515ebc896ed526d81be399c7a46dcfdf28a1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8423303 Reviewed-by: Hidehiko Abe <hidehiko@chromium.org> Commit-Queue: Satoru Takabayashi <satorux@google.com> Cr-Commit-Position: refs/heads/main@{#1715124}
[iOS] Update Level Up Tab Group task IPH text to be clearer The initial text didn't actually say how to create a tab group. The title parameter was also ignored for this Bubble variant, so that was removed to not be confusing. Fixed: b:564563042 Change-Id: I6816f6cbbc86eef188f75b7d0933d2a2c17c25ad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8522446 Auto-Submit: Robbie Gibson <rkgibson@google.com> Reviewed-by: Louis Romero <lpromero@google.com> Reviewed-by: Pier-Alexandre Bouchard <pabouchard@google.com> Commit-Queue: Louis Romero <lpromero@google.com> Cr-Commit-Position: refs/heads/main@{#1715123}
[Android] Migrate IPH test waits to ViewFinder Replace ViewUtils.isEventuallyVisible() in KeyboardAccessoryViewTest and ReadLaterContextMenuTest with ViewFinder.waitForView(). IPH bubbles are shown in a separate, non-focusable window, so search anyRoot(). KeyboardAccessoryViewTest now clicks the ViewPresence returned by waitForView() instead of re-querying, so the click only happens after the bubble is displayed. Clicking before the bubble was displayed hit the extensions button and caused the revert in crbug.com/486235095. Split out of https://crrev.com/c/7596310. Bug: 471253747 Change-Id: I23f7279d35e1e6bf7273ee8bd54af11ff31e7fe8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8520701 Owners-Override: Henrique Nakashima <hnakashima@chromium.org> Reviewed-by: Andrew Grieve <agrieve@chromium.org> Commit-Queue: Andrew Grieve <agrieve@chromium.org> Auto-Submit: Henrique Nakashima <hnakashima@chromium.org> Cr-Commit-Position: refs/heads/main@{#1715122}
[Notifications] SW popup capability delegation
When handling a notification click, a Service Worker may need an
existing client window to open a popup (e.g. an email preview or chat
compose). Currently, window.open() in the client is blocked by the popup
blocker because the client window lacks transient user activation.
This CL allows the Service Worker to delegate popup capability to a
same-origin WindowClient via client.postMessage(msg, {delegate:
'popup'}). Upon receipt, the client window receives a 1-second transient
popup token enabling window.open(). This is decoupled from window
interaction and gated behind the CapabilityDelegationPopup feature flag.
See https://chromestatus.com/feature/5091965583622144
Bug: 542314185, b:529458813
Test: http/tests/serviceworker/clients-capability-delegation.html
Test: external/wpt/html/capability-delegation/
Test: blink_unittests --gtest_filter=WebFrameTest.CapabilityDelegation*
Change-Id: I43dcdbf25b6585f9fcdb8a49f9810037136aec5e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8069089
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Commit-Queue: Daniel Murphy <dmurph@chromium.org>
Reviewed-by: Nasko Oskov <nasko@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1715121}
[Surface Embed] Pinch zoom (Part 1/3): Resolve pinch zoom target Touchscreen pinch gestures currently scale the root view, including when they originate in embedded or out-of-process content. Before input routing can selectively scale embedded content, each view needs a consistent way to identify which WebContents should own the gesture. Add target resolution that preserves the root view as the default. OOPIF child views delegate through their frame connector, while Surface Embed connectors can either select their child or continue toward the embedder. This also supports resolving ownership through nested embeds. Later changes will configure this policy and consume the resolved target during input dispatch. Bug: 568317234 Test: SurfaceEmbedConnectorImplBrowserTest.* Test: RenderWidgetHostViewChildFrameTest.* Change-Id: Iac6b5c5873a96a8bf3345bc2a9206fcee1584e0a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8508937 Reviewed-by: Dave Tapuska <dtapuska@chromium.org> Commit-Queue: Liang Zhao <lzhao@microsoft.com> Cr-Commit-Position: refs/heads/main@{#1715120}
Gate D3D11VideoDecoderUseSharedHandle on single texture decoders. Shared handle output textures cannot be presented with the zero-copy decode swap chain, so enabling D3D11VideoDecoderUseSharedHandle forces decoders that would otherwise decode into a texture array, e.g. H.264, onto the VPBlit presentation path and regresses playback power. Only apply shared handles when the driver requests one texture per picture buffer (bit 14 of ConfigDecoderSpecific), where the decode swap chain is unavailable anyway. Also add the D3D11VideoDecoderUseSharedHandle to fieldtrial config so win10 perf tests will cover it. Bug: 40270305 Change-Id: If09ecbb84d30105af1246137af0655fd74f14215 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8537633 Reviewed-by: Dale Curtis <dalecurtis@chromium.org> Commit-Queue: Qiu, Jianlin <jianlin.qiu@intel.com> Cr-Commit-Position: refs/heads/main@{#1715119}
Android: Replace View / Activity mocks with real objects (hard-6)
Removes the @SuppressWarnings("DoNotMock").
Bug: 567604165
Change-Id: Ic5c531ec13fa23cf9e1d696b290692b8eecdf5ca
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8526311
Reviewed-by: Patrick Noland <pnoland@chromium.org>
Commit-Queue: Andrew Grieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1715118}
chromeos/CHROMEOS_LKGM: Automatic uprev to 16848.0.0-1080818. Diff Link: http://crosland/log/1080814..1080818 Generated by PUpr, see https://cr-buildbucket.appspot.com/build/8668469385220659521 for job details. BUG=None TEST=CQ Pupr-Upstream-Versions: [{"ref": "refs/heads/snapshot", "repository": "/chromeos/manifest-internal", "revision": "df8dc3daf374f9fa9769a4e3d31df5ad90539b72"}] Cq-Cl-Tag: pupr:chromeos-lkgm Override-Tryjobs-For-Automation: luci.chrome.try:chromeos-betty-chrome-gtest-and-tast,chromeos-brya-chrome,chromeos-jacuzzi-chrome,chromeos-reven-chrome,chromeos-trogdor-chrome,chromeos-volteer-chrome; luci.chromium.try:chromeos-amd64-generic-rel,chromeos-arm64-generic-rel,linux-presubmit,win-presubmit Change-Id: I7fbe490c7b05af7523110af961654d7083305fff Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8540738 Commit-Queue: chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com <chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com> Bot-Commit: chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com <chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1715117}
Deflake cdata-001.xhtml and cdata-002.xhtml by waiting for Ahem `wpt/html/rendering/cdata-001.xhtml` and `wpt/html/rendering/cdata-002.xhtml` are flaky due to not waiting for Ahem to load. When the tests are run by themselves, the flakiness is consistently reproducible without this patch and goes away with this patch, which waits for the font to be ready. This patch has a small special-case because the fonts may not load until the non-empty xhtml with the Ahem font is present, so a second await is needed. Bug: 568337130 Change-Id: Ic739279bde8f84527bd8c9225ab63d78c3c1e430 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8542234 Commit-Queue: Kent Tamura <tkent@chromium.org> Reviewed-by: Kent Tamura <tkent@chromium.org> Auto-Submit: Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/main@{#1715116}
[OE] Align plus button icon with suggestion icons and submit button The 40px-wide oblong contextual entrypoint (+) button in #bottomControls previously used a 16px inline-start padding (plus a 0.5px margin in composebox), placing the centered 20px plus icon at 36px/36.5px instead of 32px where the 32px-wide suggestion icon containers (16px + 16px) are centered. Update #bottomControls padding-inline-start to 12px and remove the 0.5px inline-start margin on #contextEntrypoint so the plus icon center aligns at 32px with the suggestion and input icons. Also set padding-inline-end to 12px on #bottomControls when cr-composebox-submit is present so the 40px-wide submit button maintains matching 12px horizontal edge spacing. Demo: https://screencast.googleplex.com/cast/NTcwMjQxNTc4MDE1MTI5NnwzZjA4ZTA0NC04Yw Bug: 568081200 Change-Id: I42f62dc3fd91e9cf4f96c3ac03714fad18419df9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8521482 Reviewed-by: Juliet Knighton <julietlevesque@google.com> Commit-Queue: Hamzah Behery <behery@chromium.org> Cr-Commit-Position: refs/heads/main@{#1715115}
[Organizer] Small spacing and layout updates Rounded effect on hover, reduce padding to match Figma https://screenshot-v2.corp.google.com/65e7260ne6090 Bug: 563021016 Change-Id: I9f7c87b745a50a432b52491bd562b776b83474b3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8542514 Reviewed-by: Chase Hartsell <chazzy@chromium.org> Commit-Queue: Alison Gale <agale@chromium.org> Cr-Commit-Position: refs/heads/main@{#1715114}
build: Make chrome/linux cross builds on mac hosts work On mac hosts, pkg-config.py now queries the linux sysroot's .pc files with the host's pkg-config instead of returning empty results, so the right include dirs, libs and defines (e.g. the ATSPI version) are used. Also disable the V8 context snapshot for linux builds on non-linux hosts, as is already done for mac and win cross builds. Tested by building chrome for linux arm64 and linux x64 on a mac arm64 host (with target_os = ["linux"] in .gclient). Change-Id: Ibd68a17b8a4c282be1fbc706aa831694a5effcf3 Bug: 571157137 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8539008 Reviewed-by: Jesse McKenna <jessemckenna@google.com> Reviewed-by: Thomas Anderson <thomasanderson@chromium.org> Commit-Queue: Marco Bartoli <marcobartoli@microsoft.com> Cr-Commit-Position: refs/heads/main@{#1715113}
[ios] Prevent stopping non-active FullscreenAnimator Calling stopAnimation on a UIViewPropertyAnimator that is not in the active state seems to cause a crash on iOS 27. This change adds an early return to avoid this. Fixed: 571488704 Change-Id: I95e612e21bab8e664b1ed3d12f52c564efadc48c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8537973 Reviewed-by: Chris Lu <thegreenfrog@google.com> Commit-Queue: Scott Yoder <scottyoder@google.com> Cr-Commit-Position: refs/heads/main@{#1715112}
Roll ANGLE from 2e5da5cc4d17 to d2e5e488da0c (2 revisions) https://chromium.googlesource.com/angle/angle.git/+log/2e5da5cc4d17..d2e5e488da0c 2026-10-08 pmukesh@qti.qualcomm.com Vulkan: Fix tile memory vkCmdCopyImage path missing flush 2026-10-08 cnorthrop@google.com Capture/Replay: Track state changes during resource reset If this roll has caused a breakage, revert this CL and set the roller to dry run mode using the controls here: https://autoroll.skia.org/r/angle-chromium-autoroll Please CC angle-team@google.com,yuxinhu@google.com on the revert to ensure that a human is aware of the problem. To file a bug in ANGLE: https://bugs.chromium.org/p/angleproject/issues/entry To file a bug in Chromium: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:gpu-fyi-cq-mac-arm64;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:gpu-fyi-cq-win-arm64;luci.chromium.try:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86 Bug: None Tbr: yuxinhu@google.com Test: Test: angle_trace_tests --gtest_filter=*one_piece_bounty_rush Test: Test: capture_tests.py Submodule-Gn-Analyze: true Change-Id: I8ab123170372fadd3ef672a634488f5542e01673 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8544030 Bot-Commit: chromium-autoroll@skia-public.iam.gserviceaccount.com <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll@skia-public.iam.gserviceaccount.com <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1715111}
No metadata found
Fix naming style in platform/image-*coders/ * Variable names should be lower_snake_case. Bug: 492927412 Change-Id: I84b653fdfee0223ca591daba082586799484f317 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8532966 Auto-Submit: Kent Tamura <tkent@chromium.org> Reviewed-by: Fredrik Söderquist <fs@opera.com> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/main@{#1715109}
Android: Skip extracting .res.zip files in compile_resources.py
Move static resource path transformations (locale directory renaming,
moving images from drawable-*-mdpi-* folders to non-mdpi folders, and
stripping .png/.webp extensions) from compile_resources.py into
prepare_resources.py, and stop adding {index}_{resource_dir_name}/
prefixes and MULTIPLE_RES_MAGIC_STRING zip comments when creating
.resources.zip archives.
In compile_resources.py, pass unmodified .resources.zip files directly
to 'aapt2 compile --zip', and create a temporary filtered input zip only
for dependencies that have entries excluded by
--resource-exclusion-regex or --locale-allowlist, or converted by
--png-to-webp.
Benchmark (hyperfine --warmup 1 --runs 5 on
chrome_public_apk__compile_resources):
Before: 19.673 s +- 0.208 s (user: 15.474 s, sys: 12.310 s)
After: 11.365 s +- 0.097 s (user: 13.650 s, sys: 7.277 s)
Speedup: 1.73x faster (-8.31 s / -42.2%)
Bug: 558715733
Change-Id: I094c5627e5a2fcdbeffe155d5b0cb03c1981de7a
Agent-Generated: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8534906
Reviewed-by: Peter Wen <wnwen@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1715108}
Roll DevTools Frontend from c0884b8bff9a to f4923b265b7a (1 revision) https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/c0884b8bff9a..f4923b265b7a 2026-10-08 cjamcl@chromium.org [trace] Use export enum instead of const enum and type ImageDelivery strings If this roll has caused a breakage, revert this CL and set the roller to dry run mode using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC chrome-devtools-staff+oncall-change@google.com,liviurau@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Bug: None Submodule-Gn-Analyze: true Change-Id: I929b0f573432bb0f2cee3f71afb3a7faa55461e4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8544050 Bot-Commit: chromium-autoroll@skia-public.iam.gserviceaccount.com <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll@skia-public.iam.gserviceaccount.com <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1715107}
[Actor]: Register PerformSearchToolRequest in ToolRegistry Actor tool requests declare model-facing schemas so LLM clients can discover and invoke available browser tools. PerformSearchToolRequest navigates the active tab to a search URL using the profile's default search engine, but was missing a ToolDefinition registration and model-facing schema in ToolRegistry. This CL registers PerformSearchToolRequest as `perform_search` under ToolId::kPerformSearch, exposing the required `query` parameter while omitting the unsupported `new_tab` parameter. Bug: b:567263315 Change-Id: I62877746b93c8467a1db890f6d4add776a6a6964 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8531599 Commit-Queue: Leah Ryu <woodchip@chromium.org> Reviewed-by: Natalia Androsz <nandrosz@chromium.org> Cr-Commit-Position: refs/heads/main@{#1715106}
Roll Chrome Win64 PGO Profile Roll Chrome Win64 PGO profile from chrome-win64-main-1791482367-5e8838e61ee2e61fa3e9043ffde619e5588fab0d-0abc99b6126d8146fd76a9f19e7286144e372097.profdata to chrome-win64-main-1791493192-069ea082269f8121e9b22f4dcf346b00a7636c3e-30cc89f19055fd875a301e4f54462ee7281276b5.profdata If this roll has caused a breakage, revert this CL and set the roller to dry run mode 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: 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: I599ff7e025fc234d10808c34e0c6b5b39f3a4f4f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8543991 Commit-Queue: chromium-autoroll@skia-public.iam.gserviceaccount.com <chromium-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: chromium-autoroll@skia-public.iam.gserviceaccount.com <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1715105}
Roll android_deps from 9nQ_9KETeXJwMaKTF... to _popEsZncps9W6-TE... If this roll has caused a breakage, revert this CL and set the roller to dry run mode using the controls here: https://autoroll.skia.org/r/android-deps-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 Tbr: clank-library-failures@google.com Change-Id: I3b95ad17bdc70a94d239fd52b84c6f7839936abb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8543950 Commit-Queue: chromium-autoroll@skia-public.iam.gserviceaccount.com <chromium-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: chromium-autoroll@skia-public.iam.gserviceaccount.com <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1715104}
Settings Lit: Migrate settings_ui/ to Lit Bug: 393471368 Change-Id: Ic57ab89eaa7f0e8944c014e91dbfeebf3188f91e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8540330 Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org> Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Cr-Commit-Position: refs/heads/main@{#1715103}
Roll vulkan-deps from 48e2fa5d23e0 to 85c125900cdb (1 revision) https://chromium.googlesource.com/vulkan-deps.git/+log/48e2fa5d23e0..85c125900cdb Also rolling transitive DEPS: https://chromium.googlesource.com/external/github.com/KhronosGroup/Vulkan-ValidationLayers/+log/d266b01c102aebdf68da7e3edbc70bfc62aeed48..4d9108fb142e330532b8f1289e868c977f1e69cf If this roll has caused a breakage, revert this CL and set the roller to dry run mode using the controls here: https://autoroll.skia.org/r/vulkan-deps-chromium-autoroll Please CC angle-team@google.com,chouinard@google.com,radial-bots+chrome-roll@google.com,radial-bots@google.com,webgpu-developers@google.com,yuxinhu@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:gpu-fyi-cq-mac-arm64;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:gpu-fyi-cq-win-arm64;luci.chromium.try:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86;luci.chromium.try:dawn-linux-x64-deps-rel Bug: None Tbr: chouinard@google.com,radial-bots+chrome-roll@google.com,yuxinhu@google.com Change-Id: I84d48fd3c2aa7815cedeee7d649167eeb76256af Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8543930 Bot-Commit: chromium-autoroll@skia-public.iam.gserviceaccount.com <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll@skia-public.iam.gserviceaccount.com <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1715102}
Remove unused WebMWebVTTParser and webvtt_util.h In-band text track support was removed in crrev.com/c/4843921, leaving WebMWebVTTParser and media::MakeSideData (in webvtt_util.h) with no remaining callers. Change-Id: I02a1a0b4f8deccf73aa454243e9322ba5848c477 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8542213 Reviewed-by: Syed AbuTalib <lowkey@google.com> Commit-Queue: Dale Curtis <dalecurtis@chromium.org> Commit-Queue: Syed AbuTalib <lowkey@google.com> Auto-Submit: Dale Curtis <dalecurtis@chromium.org> Cr-Commit-Position: refs/heads/main@{#1715101}
[tab_management] Fix InputStateModel method naming violations Renames methods in InputStateModel (such as setActiveTool, setActiveModel, subscribe, notifySubscribers, updateDisabledState, and updateSelectedState) to PascalCase to align with Chromium/Google C++ style guidelines, and updates all call sites across the codebase. Bug: b:563489230 Change-Id: Ide24b593b8bfc4351447e8c2569aa67aabefc101 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8519366 Reviewed-by: Duncan Mercer <mercerd@google.com> Commit-Queue: James Leung <jamesleung@google.com> Cr-Commit-Position: refs/heads/main@{#1715100}
[Organizer] Show tab count for nameless groups Bug: 571567043 Change-Id: I1a0647153aa85e0bf15437956ab4d39ffdf77d07 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8540372 Commit-Queue: Alison Gale <agale@chromium.org> Reviewed-by: Chase Hartsell <chazzy@chromium.org> Cr-Commit-Position: refs/heads/main@{#1715099}
mojo: Cache PLY lexer and yacc parser across Parse() calls in parser.py Previously, Parse() called lex.lex() and yacc.yacc() on every invocation, rebuilding the regex lexer tables and LALR(1) parsing tables from scratch for every .mojom file parsed in the same process. Build the Lexer/lex and Parser/yacc instances once per process and reset their per-file state (filename, comment lists, lineno, and lexer state) on each Parse() call. Measured median wall time improvements: - //third_party/blink/public/mojom:mojom_platform__parser_action (249 files): - Default parallelism (multi-core): 1.45s -> 1.41s (-0.04s, -2.6%) - Single-core (taskset -c 0): 6.29s -> 4.89s (-1.40s, -22.3%) - //content/common:mojo_bindings__parser_action (18 files, single-core): 2.27s -> 2.18s (-0.08s, -3.6%) - Mojom python unit tests (221 tests, single-threaded): 5.81s -> 0.49s (-5.32s, -91.6%, 11.8x faster) Bug: 563098656 Change-Id: I2c3614054f2e5715922e02df2701eb396911649a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8513737 Reviewed-by: Andrea Orru <andreaorru@chromium.org> Auto-Submit: Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Takuto Ikuta <tikuta@chromium.org> Cr-Commit-Position: refs/heads/main@{#1715098}
No metadata found
PaintTiming: Return a PaintTimingCallback from ElementTiming::OnPaintFinished() This CL is a step towards creating all PaintTimingClient-related performance entries at paint time: - Convert PaintTimingClient::OnPaintFinished() to return an OptionalPaintTimingCallback. OnFramePresented() will eventually be removed, but is temporarily left so that we can convert LCP/ICP separately. - Convert ElementTiming to return a callback instead of using OnFramePresented(). This removes the need for PaintTiming to know about ElementTimingInfo. - Convert PaintTimingTest unit tests to use the callback-based approach. For now, these register a callback to call OnFramePresented() to keep the tests working through the transition. - In PaintTiming, clear the pending presentation data on detach to prevent holding onto persistent callback data longer than needed. Bug: 454082773 Change-Id: I3760055679802b6322cf5696b0e0609f9c6e0a43 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8535351 Commit-Queue: Scott Haseley <shaseley@chromium.org> Reviewed-by: Michal Mocny <mmocny@chromium.org> Cr-Commit-Position: refs/heads/main@{#1715096}
[RTS] Enable RTS test skipping for content_browsertests on Linux ASan LSan Tests (1) This enables RTS (Regression Test Selection) filtering for content_browsertests on Linux ASan LSan Tests (1) (mirrored by linux_chromium_asan_rel_ng try builder). Potential savings: ~1,338 bot-hours daily / ~55.8 bot-hours/hour (83 shards, 11.7% of test time skipped). Bug: 571587032 Change-Id: Ia7f449f6befaf74efdd6a0a06843761bb1355a7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8539409 Reviewed-by: Ben Pastene <bpastene@chromium.org> Commit-Queue: Fernando Flores <ferflores@google.com> Cr-Commit-Position: refs/heads/main@{#1715095}
PaintTiming: Mark kLcpCandidateRemovedWhilePaintTimePending obsolete In preparation for creating LCP entries at paint time, remove the UseCounter tracking nodes removed between paint and presentation time, since we'll be explicitly supporting this and removing these will simplify the implementation. Bug: 454082773 Change-Id: I8038a2ad1b07499eca49d41bc99715a2967c615a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8534626 Reviewed-by: Michal Mocny <mmocny@chromium.org> Commit-Queue: Scott Haseley <shaseley@chromium.org> Cr-Commit-Position: refs/heads/main@{#1715094}
Roll Chrome Android ARM32 Orderfile from G3Q9z0l9xCUWAv7x1... to fyvXL74Nh7Nj2ZReM... If this roll has caused a breakage, revert this CL and set the roller to dry run mode using the controls here: https://autoroll.skia.org/r/orderfile-android-arm32-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: 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: I387e31eea032bea220c084477a1d0b7d494eb778 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8544031 Bot-Commit: chromium-autoroll@skia-public.iam.gserviceaccount.com <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll@skia-public.iam.gserviceaccount.com <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1715093}
PaintTiming: Remove LargestImagePaint::NoCandidate trace event This is being removed as part of moving LCP candidate selection to paint time in order to simplify largest pending image handling, specifically keeping this makes largest pending image removal more complicated since we may need to re-emit trace events. This trace event is emitted when a pending image (not sufficiently loaded) becomes the image LCP candidate, and it's used to implement the largestImagePaint trace-based metric. This metrics was a pre-LCP metric, and AFAICT: - The trace event is not conusmed by devtools or Lighthouse. They use LargestImagePaint::Candidate, but not NoCandidate - The TBM is a legacy metric and not tied to any alert groups. LCP, which is based on the UKM trace events, does have alerts set up. - In benchmarks, removing this does not affect fully loaded pages since a Candidate trace is emitted when the image load completes Given this is only used by a legacy TBM and is not set up for alterts, I think changing its behavior slightly should hopefully be safe. Bug: 454082773 Change-Id: I1d8d5736fdbc6c23bec7fe3b9ac02fcf3dd6153f Fixed: 40803519 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8526479 Commit-Queue: Scott Haseley <shaseley@chromium.org> Reviewed-by: Michal Mocny <mmocny@chromium.org> Reviewed-by: Annie Sullivan <sullivan@chromium.org> Cr-Commit-Position: refs/heads/main@{#1715092}
Roll Perfetto Trace Processor Win from f34010eccc09 to 9843f023eb4f https://chromium.googlesource.com/external/github.com/google/perfetto.git/+log/f34010eccc09..9843f023eb4f If this roll has caused a breakage, revert this CL and set the roller to dry run mode using the controls here: https://autoroll.skia.org/r/perfetto-trace-processor-win-chromium Please CC chrometto-team@google.com,perfetto-bugs@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Tbr: perfetto-bugs@google.com Change-Id: Ib32267e16e6b8c33609fde93a3deba42215652ea Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8543630 Bot-Commit: chromium-autoroll@skia-public.iam.gserviceaccount.com <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll@skia-public.iam.gserviceaccount.com <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1715091}
No metadata found
[RTS] Enable RTS test skipping for sync_integration_tests on Linux Tests This enables RTS (Regression Test Selection) filtering for sync_integration_tests on Linux Tests (mirrored by linux-rel try builder). Potential savings: ~762 bot-hours daily / ~31.8 bot-hours/hour (6 shards, 51.5% of test time skipped). Bug: 571587032 Change-Id: Ibee8f120ffe7a1cb43759164b663171058f0afde Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8538947 Commit-Queue: Fernando Flores <ferflores@google.com> Reviewed-by: Ben Pastene <bpastene@chromium.org> Cr-Commit-Position: refs/heads/main@{#1715089}
[RTS] Enable RTS test skipping for sync_integration_tests on Linux ASan LSan Tests (1) This enables RTS (Regression Test Selection) filtering for sync_integration_tests on Linux ASan LSan Tests (1) (mirrored by linux_chromium_asan_rel_ng try builder). Potential savings: ~1,838 bot-hours daily / ~76.6 bot-hours/hour (20 shards, 51.1% of test time skipped). Bug: 571587032 Change-Id: I39afdb750400baa58d0e76a205afbaa928b293ee Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8540268 Commit-Queue: Fernando Flores <ferflores@google.com> Reviewed-by: Ben Pastene <bpastene@chromium.org> Cr-Commit-Position: refs/heads/main@{#1715088}
[RTS] Enable RTS test skipping for components_unittests on Linux ASan LSan Tests (1) This enables RTS (Regression Test Selection) filtering for components_unittests on Linux ASan LSan Tests (1) (mirrored by linux_chromium_asan_rel_ng try builder). Potential savings: ~371 bot-hours daily / ~15.5 bot-hours/hour (7 shards, 28.5% of test time skipped). Bug: 571587032 Change-Id: I3150b8f13e34abd6e6c5a1fcced18f2a07278812 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8538948 Reviewed-by: Ben Pastene <bpastene@chromium.org> Commit-Queue: Fernando Flores <ferflores@google.com> Cr-Commit-Position: refs/heads/main@{#1715087}
Error fetching metadata:
[Contextual Tasks] Repopulate tab picker selection from session context When the outer Search page closes the context menu, the tab picker extension iframe unmounts and loses its local `selectedTabs` state. This CL repopulates `selectedTabs` whenever the tab picker mounts or the session tab context changes: - Subscribe `<tab-picker-app>` to `callbackRouter.onTabContextUpdated` and load `tab_picker.js` before `post_message_entrypoint.js` so the initial tab context update is received on mount. - Resolve `SessionID` back to `TabHandle` ID in `ContextualTasksExtensionHandler::SendTabContextToExtensionPage` so the `tabId`s sent in `OnTabContextUpdated` match those returned by `GetRecentTabs()` and expected by `DeleteTabContext()`. Before: screencast/cast/NDc2MzY2Mjc5ODU1MzA4OHw1ZDUwZjAyZC1mYQ After: screencast/cast/NjA2OTI4Mzg2NzA2NjM2OHwzNGM3MWE4ZS0zYw Bug: b:571137154 Change-Id: I4cb0ca0a87b1bd6614e79a5e6f51882cead33667 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8531708 Commit-Queue: James Leung <jamesleung@google.com> Reviewed-by: Duncan Mercer <mercerd@google.com> Cr-Commit-Position: refs/heads/main@{#1715085}
PaintTiming: Refactor LargestContentfulPaintDetails This CL refactors LargestContentfulPaintDetails in advance of moving the LCP candidate selection to paint time (vs presentation time): - Split LargestContentfulPaintDetails into separate image and text structs. In a subsequent patch, we'll store the current presented image details separately so we can fall back to it if the largest pending image is removed (vs. storing an ImageRecord and falling back to that). - Add helper methods to get the "merged" values (combined image and text presentation time and type). This removes the duplication in deciding if we should use the text or image candidate, which was repeated in a few places. - Move the image type calculation into a helper function to make the image details initialization a bit more readable. Bug: 454082773 Change-Id: I9fe71fb33f5ab039fa60ae36ade5887255fac817 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8528497 Commit-Queue: Scott Haseley <shaseley@chromium.org> Reviewed-by: Michal Mocny <mmocny@chromium.org> Cr-Commit-Position: refs/heads/main@{#1715084}
[contextual_tasks] Dark mode in context library + adjust outline * Add dark mode detector to context library iframe * Use that attribute to change CSS outline for favicons in context library * Fix outline color for favicons (dark and light) * Add tests screen/cast/Njc0ODA0NTA2MzQ4NzQ4OHxiMWU0YTFjNS0wYg Bug: b:571139132 Change-Id: I7a0a2a60bc1e9ca793cda42451a4d1c4b98d71bc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8530640 Reviewed-by: Duncan Mercer <mercerd@google.com> Reviewed-by: Josiah Kiehl <kiehl@google.com> Commit-Queue: James Leung <jamesleung@google.com> Cr-Commit-Position: refs/heads/main@{#1715083}