Line height input format didn't follow system locale #21016

Closed
opened 2026-01-31 07:30:41 +00:00 by claunia · 5 comments
Owner

Originally created by @wicaksono on GitHub (Dec 27, 2023).

Windows Terminal version

1.18.3181.0

Windows build number

10.0.22631.2861

Other Software

No response

Steps to reproduce

Open Terminal, go to Settings > Default > Appearance > Line height

Expected Behavior

Decimal digit will separated by system locale (in my case is comma) and able to click up and down arrow.

Actual Behavior

On my locale, the digits is separated by comma, but terminal is ignoring it and using dot. This is also makes me unable to click up and down arrow next to it.

Originally created by @wicaksono on GitHub (Dec 27, 2023). ### Windows Terminal version 1.18.3181.0 ### Windows build number 10.0.22631.2861 ### Other Software _No response_ ### Steps to reproduce Open Terminal, go to Settings > Default > Appearance > Line height ### Expected Behavior Decimal digit will separated by system locale (in my case is comma) and able to click up and down arrow. ### Actual Behavior On my locale, the digits is separated by comma, but terminal is ignoring it and using dot. This is also makes me unable to click up and down arrow next to it.
Author
Owner

@zadjii-msft commented on GitHub (Jan 3, 2024):

Yep, we should fix that. Thanks!

@zadjii-msft commented on GitHub (Jan 3, 2024): Yep, we should fix that. Thanks!
Author
Owner

@lhecker commented on GitHub (Jan 8, 2024):

I was intending to change that input field to use a CSS line-height string so that it supports explicit "px" and "pt" suffixes. I wonder if it would be necessary to add an explicit unit selector as a GUI element... 🤔

@lhecker commented on GitHub (Jan 8, 2024): I was intending to change that input field to use a CSS line-height string so that it supports explicit "px" and "pt" suffixes. I wonder if it would be necessary to add an explicit unit selector as a GUI element... 🤔
Author
Owner

@lhecker commented on GitHub (May 17, 2024):

Oh I see now. The problem is that you're mistaking the placeholder string as a value. If you just type any number into the field you can use up/down perfectly fine:
image

@lhecker commented on GitHub (May 17, 2024): Oh I see now. The problem is that you're mistaking the placeholder string as a value. If you just type any number into the field you can use up/down perfectly fine: ![image](https://github.com/microsoft/terminal/assets/2256941/fc41e277-16ab-4f0a-ac5e-54a2c9feffe1)
Author
Owner

@lhecker commented on GitHub (May 17, 2024):

Frankly, I don't know how to fix this. NumberBox is hardcoded to disable the up/down buttons if the value is NaN (= no value): 326f5a684b/controls/dev/NumberBox/NumberBox.cpp (L665-L694)
We could change the template, but I'm not sure whether that's worth it.

@lhecker commented on GitHub (May 17, 2024): Frankly, I don't know how to fix this. `NumberBox` is hardcoded to disable the up/down buttons if the value is NaN (= no value): https://github.com/microsoft/microsoft-ui-xaml/blob/326f5a684bd765db6d7c939e971486810381688d/controls/dev/NumberBox/NumberBox.cpp#L665-L694 We could change the template, but I'm not sure whether that's worth it.
Author
Owner

@DHowett commented on GitHub (Aug 22, 2024):

I suspect that it's not worth it to fix this as-is. Please feel to reopen it (or comment!) if you disagree.

@DHowett commented on GitHub (Aug 22, 2024): I suspect that it's not worth it to fix this as-is. Please feel to reopen it (or comment!) if you disagree.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#21016