The vertical scrollbar thumb does not expand to full size

[heaths]

Windows Terminal version

1.13.11432.0

Windows build number

10.0.22000.0

Other Software

No response

Steps to reproduce

1. Write enough text to display a vertical scrollbar e.g. tree /f %windir%
2. Hover mouse over scrollbar or even the thumb specifically

Expected Behavior

Thumb expands to a larger size as it does in Notepad (new Windows 11 version).

Actual Behavior

Thumb stays tiny as shown in screen grab below:

[zadjii-msft]

Huh.

any chance you have animations disabled in the OS? I honestly have no idea what could possibly cause this 😕

Maybe #12608?

[vefatica]

I have

and

Microsoft Windows 10 Pro for Workstations
10.0.19044.1766 (2009, 21H2)
WindowsTerminalPreview 1.14.2205.25001

I do not see the animation shown in @zadjii-msft's clip. Ditto in 1.13.2205.23001. The slider acts as if it's wider; i.e., I can grab it with the mouse a few pixels on either side. I just don't see the wider version.

[heaths]

Maybe #12608?

Animations are enabled. It could be related to that issue, though. I should've also mentioned I'm running 4K resolution. Assuming new notepad is using WinUI (I'm pretty sure it is), you can see the scrollbar works as I'd expect with modern UI.

To note: this also repros in Terminal Preview version 1.14.1452.0.

[zadjii-msft]

If I had to guess, this regressed in #12608, but I have no idea why. We're just copy-pasting the scrollbar XAML in its entirety.

Do the scrollbars in the Settings UI work as expected? That might help narrow this down.

[vefatica]

Here, they're old-fashioned looking.

Microsoft Windows 10 Pro for Workstations
10.0.19044.1766 (2009, 21H2)

[heaths]

Do the scrollbars in the Settings UI work as expected? That might help narrow this down.

@zadjii-msft no, they exhibit the same always-narrow behavior as shown in my screenvid.

[zadjii-msft]

Sticking Leonard on this since he's got a live repro. Presumably this is sure to our manual re-template of the scrollbar control, but I wouldn't begin to know what we broke.

[lhecker]

I used to have this issue and it doesn't occur in the internal 1.16.2352.0 preview build anymore. Closing, because it'll be (hopefully - if I'm right) fixed in the upcoming 1.16 build.