{{ message }}
Repository navigation
Upgrade Chromium to 155.0.8059.79 - #459
Draft
tnsardesai wants to merge 4 commits into
Draft
tnsardesai wants to merge 4 commits into
tnsardesai wants to merge 4 commits into
Conversation
Chromium 154 clears Emulation.setDeviceMetricsOverride when the session that set it detaches, so the override PATCH /display applies on the headless path is undone as soon as the server disconnects. Size the window around the page instead, which persists independently of any CDP session. Also match the chrome://extensions Developer mode toggle by either role: Chromium 154 changed cr-toggle from role=button to role=switch.
…efused Chromium rejects Browser.setContentsSize for a maximized, minimized or fullscreen window. Production headless launches maximized, so restore maximized and minimized windows to normal first. Leave fullscreen windows alone, since leaving fullscreen would exit kiosk mode, and fall back to the previous device metrics override whenever Chromium refuses the resize, so no request fails that succeeded before. Keep SetDeviceMetricsOverride for that fallback, and cover maximized and kiosk headless browsers in the resize e2e.
tnsardesai
force-pushed
the
hypeship/chrome-155
branch
from
October 14, 2026 02:59
d0e39d3 to
f3cf83d
Compare
Base automatically changed from
hypeship/headless-resize-setcontentssize
to
main
October 21, 2026 13:37
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bumps Chrome for Testing (and the matching ChromeDriver) from 152.0.7977.42 to 155.0.8059.79, the current Stable, in both the headful and headless images. The WebMCP fixture README named the version its behaviour was verified on, so it now says 155.
Stacked on #458. That PR fixes two Chromium 154 changes this bump would otherwise break: the headless
PATCH /displayviewport override being reset when its CDP session detaches, and the chrome://extensions Developer mode toggle changing fromrole=buttontorole=switch. Merge #458 first; this PR's base will then move tomain.Runtime dependencies
The only change to
deb.depsbetween the two releases is thelibglib2.0-0minimum, from>= 2.39.4to>= 2.49.3. Ubuntu 22.04 ships 2.72, so neither image needs new packages.Validation
mainbase, so I started it manually on this branch (run 38503931861, head f3cf83d, rebased onto Resize the headless viewport with Browser.setContentsSize #458's fallback fix). Both image builds,test-server-unitandtest-server-e2epassed, includingheadless_default,headless_start_maximized,headless_kioskandTestMV3ServiceWorkerRegistration.chromium --versionreportsGoogle Chrome for Testing 155.0.8059.79) and ran the headless e2e tests against it with-parallel=4. 29 passed (before the Resize the headless viewport with Browser.setContentsSize #458 fallback fix), includingTestPlaywrightExecuteAPI(all WebMCP subtests), the BiDi and CDP proxy tests,TestChromiumConfigureMultipartPowerset,TestExtensionUploadAndActivationandTestMV3ServiceWorkerRegistration.TestDisplayResizeChromiumWindow/headless_defaultfailed once in that run, duringnavigateBlank:page.goto('about:blank')timed out after 30 s, before any resize was sent. It passed on 3 of 3 runs by itself, with the renderer at 1920x1080 and then 1280x720. The same pre-resize timeout happened once on 152, so it isn't caused by this bump.