[corytheboyd]

Very clever!

Totally unrelated to this project, just a general UI question: does anyone like these inputs? Every time there is a number input next to one, I use that instead. Seems the upper limit of “ticks” you can have on one before it becomes unusable is like… 10?

Proper number inputs support all the same features (min, max, arrow keys to increment/decrement), but you can also just input an exact number. The range does visualize min, max, and current value relative to those nicely, but it’s annoying to actually use as an input more often than not.

The only real exception is for ranges of 0-100 type things, where the exact value doesn’t need to be precise, just roughly somewhere on that 1-100 scale. Eyeballing it is enough here, you don’t feel frustrated that you can’t use your thumb to get exactly 71. Volume slider, etc.

[yreg]

> does anyone like these inputs?

We've A/B tested a slider against a textbox with plus and minus buttons (banking, on mobile) and the latter seemed to work better (as in fewer users cancelled the flow).

I'm not pretending this finding can be generalised, though.

[Rygian]

I can't imagine a banking interaction where the amount of money is not a precise value.

What use cases motivated the testing of a slider?

[lmm]

Wonga.com was (briefly) a huge success story with their "two slider" interface. Perhaps because it made it easy to see how the output changed with the input.

[yreg]

I believe it was some mortgage calculator and it jumped by 10k steps.

[encoderer]

I could make the argument that a number input plus a labeled slider is superior to number input plus a text label of min/max

[corytheboyd]

Makes sense to me, the range input is effectively acting as the label here, it just happens to be an input as well. Best (better?) of both worlds.

[wruza]

I almost never use them. In sd webui I change resolution often, so I patched some divs to contain [512, 640, 768, …] and click these instead. Not sure if this slider control should even exist in a flow context, because it cannot be made scrollable like a volume range.

I also somewhat like unix style numeric inputs because you can grab a bar between the arrows and drag it to change the value. No long range required.

Ranges with sticky points are somewhat okay, e.g. Virtualbox settings stick to 2^n values for RAM and some integer disk GBs. But these intermediate values are just nonsense and nobody ever selected 7527MB of RAM by non-mistake.

Bonus points for Ubuntu keyboard repeat/delay settings which don’t show the numeric values at all. You set delay to 178 or maybe 223 or maybe 202. Who cares about muscle memory, right?

[zapparoni]

Anytime you don't care about exact values and want a quick way to nudge the value in a live visual environment they are great.

For example in an editor for procedurally generated stuff like random maps, texture, sounds, etc.

[jcelerier]

> does anyone like these inputs?

I implemented one in https://ossia.io but in practice a draggable spinbox is much more useable