One more thing I hate: <input type=number /> coerce to a number when bind:value

[NormandoHall]

As say in docs https://svelte.dev/docs/svelte/bind#input-bind:value I think this is really bad. This breaks a lot of code and validations suites.

Why????

I'm a developer, not a silly kid. Numeric input are for UI (browser/mobile) purposes, but it should always be a string. Leave things the way they always were, even before Svelte existed!

https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/number

Please, stop!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! PLEASE STOP!!!!!!!!!!

[brunnerh]

You don't have to use the binding if you don't want this behavior.

<script>
	let value = $state('1.0');
</script>

<input type=number {value} oninput={e => value = e.currentTarget.value} />

Playground

[NormandoHall]

Thanks for the suggestion! But I need to adapt a lot of code to use it as callback. For a quick and dirty workaround I "hack" the bind with get/set functions in the components.

<script>
  let {
    value = $bindable(),
  } = $props();
</script>

<input type=number bind:value={() => value, (v) => (value = v?.toString())} />

[Ocean-OS]

That works as well, or if you want to have more concise code:

<input type="number" bind:value={()=>value, v=>(value = v+"")} />