Bug - [Slider with Input] - [should accept , as comma for non en US locales]

Describe the problem
This is an issue with

Patternfly 6

When using , if the adjacent input is initialized with a non-English decimal separator (comma, e.g. "50,2"), the component breaks: the slider/input get out of sync and/or parsing fails. This happens even when the page/parent container has a non-EN lang (e.g. lang="el").

Affected components: Slider (with isInputVisible, value, inputValue)

How do you reproduce the problem?
https://codesandbox.io/p/sandbox/3kn8jh?file=%2Findex.tsx

Expected behavior
The input next to the slider should accept and display localized decimal separators in line with the container/page lang.

The slider should internally normalize user input (comma or dot) and maintain a numeric state.

Is this issue blocking you?
No, I am now normalizing the input myself.

What is your product and what release date are you targeting?
anaconda installer, no specific target

Jira Issue: PF-2789

fix(storage): normalize locale decimals for PatternFly slider input

storage: normalize locale decimals for PatternFly slider input

storage: stop using inputValue from slider as it cannot parse localiz…

storage: normalize locale decimals for PatternFly slider input

storage: stop using inputValue from slider as it cannot parse localiz…

@KKoukiou

@KKoukiou Just to confirm some things:

Is it expected that you would pass in a string like "50,2" to the inputValue prop
from there, PF would transform that string to a decimal number internal to the component
that transformed number would be what's displayed in the input as well as what's stored internally
- Or rather, is the expectation that the input would still display the commas 50,2, and just internally the component would transform to a decimal to do any calculations, then render it back in the input with the comma again

The same confirmations above would likely apply to the slider steps as well, in terms of their value and displayed label.

Would you also be able to confirm whether this is something specific to Slider, or if there are other instances of numbers needed for input where this is a problem? Thinking namely of the NumberInput component

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

Looking at language detection, we could use the inherited lang attribute, but OpenShift doesn't change this when language changes.

OpenShift uses https://github.com/i18next/i18next-browser-languageDetector (this is just the translated codebase I'm most familiar with) and then stores language changes via a dropdown in local storage.

feat(Slider): Recognize localized number input

We had a go at this in #12599. As of right now, it adds a lot of complexity. It sounds like you are already normalizing the input yourself. We'd like to skip adding this for now, but we'd be happy to revisit this if it comes up for more teams again in the future (or if our JavaScript overlords come up with a built-in parser).

Navigation Menu

Repository navigation

Bug - [Slider with Input] - [should accept , as comma for non en US locales] #12052

4 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Bug - [Slider with Input] - [should accept , as comma for non en US locales] #12052

Description

Activity

thatblindgeye commented on Oct 17, 2025

github-actions commented on Dec 18, 2025

4 remaining items

github-actions commented on Jun 24, 2026

rebeccaalpert commented on Jul 27, 2026

rebeccaalpert commented on Aug 3, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions