new Accessibility problem

[frodopwns]

Type: Bug

On OSX to perform a screen zoom you press CTRL+ 2 finger scroll or press some other keys.

I used to be able to hover over code, wait for the tooltip and then zoom in to read the tooltip. Now when i press CTRL the tooltip immediately closes.

VS Code version: Code 1.97.2 (Universal) (e54c774, 2025-02-12T23:20:35.343Z)
OS version: Darwin arm64 24.3.0
Modes:

System Info

Item	Value
CPUs	Apple M3 Pro (12 x 2400)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off
Load (avg)	5, 4, 4
Memory (System)	18.00GB (0.10GB free)
Process Argv	./ --crash-reporter-id f85175f7-c5ab-49ef-bee2-e64db6233106
Screen Reader	no
VM	0%

Extensions (9)

Extension	Author (truncated)	Version
gitlens	eam	16.3.0
copilot	Git	1.272.0
copilot-chat	Git	0.24.1
go	gol	0.44.0
vscode-docker	ms-	1.29.4
debugpy	ms-	2025.0.1
python	ms-	2025.0.0
vscode-pylance	ms-	2025.2.1
makefile-tools	ms-	0.11.13

A/B Experiments

vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dwnewjupyter:31046869
nativerepl2:31139839
pythonrstrctxt:31112756
nativeloc1:31192215
iacca1:31171482
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
6074i472:31201624
dwoutputs:31238123
customenabled:31237564
hdaa2157:31222309
copilot_t_ci:31222730
jda6j935:31233686

[meganrogge]

Thanks for creating this issue! To help narrow it down, please take the time to follow below steps. Thanks a lot and happy coding 🙏

Is the issue caused by an Extension?

Stop VS Code and from the command line (NOT the integrated terminal in Code), execute: code --disable-extensions and try your steps again to see if it reproduces. If it still reproduces, jump to the next chapter.

If you see it is an issue with the extension, please run the command Start Extension Bisect and follow the instructions to find the extension that is causing this issue.

Please report the issue to the extension causing this.

Is the issue caused by VS Code Core?

If the issue is not caused by an extension, it is maybe caused by your configuration. Try to run code --disable-extensions --user-data-dir <directory> where <directory> is an empty folder. This will ensure Code is starting with a fresh data directory, e.g. no specific settings and without any extensions running.

If it still reproduces, it was maybe fixed already in our nightly release. Please download from https://code.visualstudio.com/insiders/ and see if you can reproduce the issue.

Finally, to help us narrow down what change caused the issue, please run the following command to find the build. It will start previous releases of VS Code insiders to see where the regression was introduced:

• npx --yes vscode-bisect@latest
• follow the instructions until you found the offending build
• report back the commit range in this issue

Thanks!

/label info-needed

[frodopwns]

When i ran vscode with extensions disabled the tooltips no longer popped up when hovering over variables/functions so I couldn't test the behavior. I am mostly working with Go.

I will move on to the next steps.

[frodopwns]

It is the Go extension. I will file a new ticket.

[meganrogge]

thanks for investigating. closing this one.

[frodopwns]

golang/vscode-go#3685

[findleyr]

@frodopwns @meganrogge I can reproduce this behavior in a css file (an arbitrary other file type), with the Go extension disabled. This is also a low-level behavior that I wouldn't expect the language extension to control.

I believe this issue should be reopened.

[frodopwns]

@meganrogge

New update: I was able to reproduce this in a python file. So it isn't caused by the Go extension.
I will try to reproduce this on another machine to rule out environment specific stuff.

[findleyr]

@frodopwns well, for what it's worth, I reproduced on my machine :)

[frodopwns]

@frodopwns well, for what it's worth, I reproduced on my machine :)

Awesome. Thanks for that. I was in the process of plugging in my mac mini!

[meganrogge]

Could someone please follow these steps?

please run the following command to find the build. It will start previous releases of VS Code insiders to see where the regression was introduced:

npx --yes vscode-bisect@latest
follow the instructions until you found the offending build
report back the commit range in this issue

[frodopwns]

Could someone please follow these steps?

please run the following command to find the build. It will start previous releases of VS Code insiders to see where the regression was introduced:

npx --yes vscode-bisect@latest follow the instructions until you found the offending build report back the commit range in this issue

I'll try but i don't use javascript/typescript tooling much so i'm sure it is a hot mess.

[frodopwns]

@meganrogge

[build] 3e86f1e6cd9bf88b1ce23192fd0b68380bfc69be is the first bad commit after 95386dec787946547812c7ee9d38cba19d6a6398.

[meganrogge]

thanks for trying - that commit looks unrelated...

[frodopwns]

thanks for trying - that commit looks unrelated...

Ah, too bad, here I was thinking the bisect tool was somewhat magical