Repository navigation
chore(deps): update playwright to v1.65.1 - #31714
Open
renovate[bot] wants to merge 2 commits into
Open
renovate[bot] wants to merge 2 commits into
renovate[bot] wants to merge 2 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
1 of 2 tasks
renovate
Bot
force-pushed
the
renovate/playwright
branch
from
November 16, 2026 23:47
84dbf4a to
25b3d4e
Compare
wheakerd
pushed a commit
to wheakerd/ionic-framework
that referenced
this pull request
Nov 17, 2026
…rome 157+ (ionic-team#31755) Issue number: internal ## What is the current behavior? In Chrome 157 and later, pressing Tab on the last focusable element of a presented `ion-modal` or `ion-popover` moves focus out of the overlay. Chrome now lets Tab move focus off the end of the page without firing a `focus` event, so the document focus listener that traps focus never runs. Alert, action sheet and loading are not affected because they already render focusable sentinels around their content. ## What is the new behavior? - Modal and popover render a focusable boundary before and after their content. A boundary moves focus to the first or last focusable element, so Tab wraps without focus leaving the page. - Alert, action sheet and loading use the same shared boundary in place of their own sentinels, and the scoped focus trap in `overlays.ts` no longer wraps focus itself. - Boundaries are hidden while the focus trap is off (`focusTrap="false"`, or a sheet modal below its `backdropBreakpoint`), so focus can still leave the overlay. - Shift+Tab from the alert wrapper now wraps to the last button. Previously it moved to the first button. ## Does this introduce a breaking change? - [ ] Yes - [x] No ## Other information - Test on localhost, not the Vercel preview. The Vercel toolbar's floating button sits after the overlay and catches the Tab, which hides the bug on `main`. - Unblocks the Playwright 1.65 update in ionic-team#31714, where the Mobile Chrome focus trap tests fail on this Chrome change. - In Firefox, the first Tab into a popover now lands on the native `textarea` inside `ion-textarea` instead of the `ion-textarea` host, which matches Chrome and Safari. The extra Firefox-only Tab in the popover textarea test was removed. - Checked with VoiceOver in Safari and Chrome: Tab wraps announce only the newly focused element, and the VoiceOver cursor never stops on a boundary, the same as on `main`. --------- Co-authored-by: ShaneK <561207+ShaneK@users.noreply.github.com>
Contributor
Author
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
This branch was successfully deployed
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.
This PR contains the following updates:
1.64.1→1.65.1^1.64.1→^1.65.1^1.64.1→^1.65.1Release Notes
microsoft/playwright (@playwright/test)
v1.65.1Compare Source
Bug Fixes
Browser Versions
v1.65.0Compare Source
🥟 Run tests with Bun
The test runner now runs under Bun. Bun transpiles your TypeScript test files itself, so Playwright does not use Babel or its compilation cache. Pass the
--bunflag, because without itbunx playwright testruns on Node.js:bunx --bun playwright testOur CI runs the test runner tests under Bun 1.4.3 on Linux. Some features work differently under Bun:
--only-changeddoes not follow imports.--tsconfigand the JSX options intsconfig.jsonhave no effect, and custom ESM loaders are not supported.clickinstead oflocator.click. This changes some step locations, step titles and error messages.🚨 Reports with only failures
New
failuresreporter prints failures and successful retries as they occur, followed by a summary, without progress output.New
onlyFailuresoption of the HTML, JSON and JUnit reporters keeps only tests with unexpected outcomes, flaky tests and interrupted tests:🎯 Test runner
New built-in
-exclusive-test lock runs a test only when no other tests are running. All other tests continue to run in parallel with each other:test.skip(), test.fixme(), test.fail() and test.slow() now accept only a description. It is recorded in the test annotation:
New
PLAYWRIGHT_TRANSFORM_CACHE_DIRenvironment variable sets the directory for transpiled test files, for example on a Linux machine shared with other users.New APIs
timeoutandsignalin cdpSession.send().Notable Changes⚠️
TypeScript class fields now follow
useDefineForClassFieldsfrom yourtsconfig.json, the same astsc. It is enabled forES2022and later targets, and whentargetis not specified. A field initializer that reads a constructor parameter property now fails, because the initializer runs first:Move the initialization to the constructor, or set
"useDefineForClassFields": falsein yourtsconfig.json.Actions such as locator.click(), locator.check(), locator.tap(), locator.fill(), locator.clear() and locator.selectOption() now wait for the element to be not inert. An action on an element with the
inertattribute, or inside such an element, now times out if the element stays inert.A sharded run now fails with "No tests found" when no tests match across all shards. Pass
--pass-with-no-teststo allow this. An empty shard still passes when other shards have tests.Cookie matching now follows RFC 6265. With a URL, browserContext.cookies() and apiRequestContext.cookies() no longer return host-only cookies for subdomains or
Path=/apicookies for/apiv2, and aPath=/foo/cookie does not match/foo. APIRequestContext sends a cookie without a name asCookie: xinstead ofCookie: =x, and storesSet-Cookie: tokenas a cookie without a name.Proxy credentials are no longer sent to websites. The credentials in the
proxyoption now answer only proxy challenges. To authenticate on a website, usehttpCredentials.Text that the browser does not render, such as text that is not assigned to a slot or text directly inside a closed
<details>, is no longer part of accessible names and aria snapshots. This can change the results of page.getByRole() with a name, locator.ariaSnapshot() and expect(locator).toMatchAriaSnapshot().String and
URLSearchParamsvalues of theparamsoption in APIRequestContext requests are now appended to the query that the URL already has, instead of replacing it..css,.lessand.scssimports in test files now load as empty modules instead of being removed, so the imported file must exist.The blob reporter again deletes the content of its output directory before it writes the report. Playwright 1.64 kept reports with other names.
Test locations of imported calls such as
test(in CommonJS output now point to the start of the callee, for examplea.spec.ts:3:7instead ofa.spec.ts:3:11. This is the same as in ESM.Announcements
Browser Versions
This version was also tested against the following stable channels:
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Never, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.