[Bug]: Test Explorer Arrows Misaligned

[craig-jennings]

Version

1.57.0

Steps to reproduce

Create multiple tests within the same file and enable the test explorer to discover and display the "run" arrow next to tests. Notice the arrows do not align with the test calls.

Expected behavior

Arrows align with test calls

Actual behavior

Arrows are misaligned

Additional context

This happens in all of my projects. This behavior started recently (within the past couple of weeks). Not really sure what changed.

Environment

VSCode extension version: 1.1.17

[Skn0tt]

Hi there! We've seen a couple reports about this, but it's always hard to reproduce. Is this happeing in .ts or .js files? Could you provide us with a minimal reproduction repo? Also, please try running npx playwright clear-cache and check if the problem goes away.

[craig-jennings]

It's happening in .ts files. FWIW, I tried the playwright clear-cache command but the behavior stayed the same.

In doing more investigation, it looks like there's a disconnect between the extension and the version of playwright installed. I was able to whittle down the code to just this repo with two branches. 1.57.0 and 1.58.0, denoting the version of Playwright that is installed. Notice the arrows are improperly aligned in the 1.57.0 branch but are correct on the 1.58.0 branch. However, I've been on version 1.57.0 since it was released and had not seen this behavior until recently (most likely when the extension updated).

Extension details:
Identifier: ms-playwright.playwright
Version: 1.1.17

VSCode Details:
Version: 1.108.2 (user setup)
Commit: c9d77990917f3102ada88be140d28b038d1dd7c7
Date: 2026-01-21T13:52:09.270Z
Electron: 39.2.7
ElectronBuildId: 12953945
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26200

It may also be of note that I'm using WSL for development

[Skn0tt]

If they're correct on 1.58.0, could you try finding which nightly version of Playwright fixed it? You can see all our nightly versions on https://www.npmjs.com/package/@playwright/test?activeTab=versions or npm view @playwright/test versions. If we can pinpoint the commits, that might tell us something about what's going on.

[SivanRP]

I think I tracked down the root cause — the range end line wasn't being converted from 1-based to 0-based. Opened a fix in microsoft/playwright-vscode#757