Weird behaviour with fader and input sharing the same ID when validation field is set

Community Usage questions
1

Maybe a bug, i’m happy to fill an issue if needed.

When validation property is set to something that allows digit values (and dot) and a fader and an input share the same ID for sync, moving the fader only update the value to 0 or 100 (range set accordingly).

Removing the validation property, fix the behavior.

See attached session for example.
validation bug.json (6.5 KB)

2

It’s a bit tricky: the input widget actually receives the fader’s value with all the decimals (the decimal option is only applied before displaying or sending the value). Replacing the regexp with this fixes it.:
^\d{1,3}(\.\d*)?$ (no digit limit after the floating point)

3

Perfect, thanks for the clarification!

So not really a bug? Mora a implementation caveat?
Maybe it’s worth mentioning in the documentation

Thanks for the swift reply

4

Actually you’re right, it’s a bug (fixed in sources)