Temperature and top_p shoud be between 0 … 1, eg. 0,4 (or 0.4; format comes from language settings, I reckon). Now it erases leading zero and decimal point when entered. So. 0,4 and right away it changes to plain 4. It started quite recently. Sure, this can come by design too if someone wanted it…

No worries at all :hugs: so happy you have it sorted. [image] Jakke Flemming: if (e.target.tagName === 'TEXTAREA' || e.target.tagName === 'INPUT') { e.target.value = e.target.value.replace(/\(c\)/gi, '©'); } The problems is that you are unconditionally doing the replace and that is…

[image] Jakke Flemming: 0,4 Europe :slight_smile: Try 0.4 instead… does that work? If it does not allow you to enter, then I guess our number component needs fixing :cry:

[image] Sam Saffron: Try 0.4 instead That was the very first thing I tried, but no luck. When those settings was introduced I used 0.x form first, because you guys are using strange dates too :stuck_out_tongue_winking_eye: But back then it changed the format to 0,x when I clicked save. Now i…

Its this … <Input @type="number" class="ai-persona-editor__top_p" @value={{this.editingModel.top_p}} disabled={{this.editingModel.system}} /> The type=number thing is causing issues on European keyboards/locales. When we ask the component what the value…

Why isn’t it accepting nothing else than numbers then? Is it a bit smarter or thigher than others that are picky that way, but only when trying to save? But a bit dummer too because it is denying 0.x too just because it doesnt like 0,x. I’m just curious here because, kind of, it is helpful approach…

Hmmm reading the spec here… maybe this is not a locale issue: The default step is 1 (allowing only integers to be selected by the user, unless the step base has a non-integer value). So maybe the bug here is that we need to specify a step for it, will test a bit later…

Looks like it’s an HTML thing rather than an Ember thing. This suggests there’s a lang= attribute we can pass to get consistent decimal behaviour: [Peter] Force decimal point instead of comma in HTML5 number input (client-side) html, google-chrome, input, numbers …

Will be fixed with: FIX: Improve AI persona editor inputs and optional GitHub auth main ← fixes-for-claude merged 10:54PM - 07 Mar 24 UTC (UTC) [image] …

[image] Sam Saffron: Europe :slight_smile: Europe, large part of Asia, large part of Africa, South America… :wink: [image]

Let me demonstrate that, because the issue is still there. I’m using iPhone here because it is the easiest way (for me) show key strokes :wink:

You 100% sure you have the latest commit?

AI bot personas don’t accept decimals for temperature, top_p

Support

Topic		Replies	Views
Format numbers depending on selected locale Feature translation , polls	4	2448	September 23, 2015
Thousand separator silently ruins inputted value in settings Bug fixed	10	619	July 11, 2024
Can't enter AI model cost of less than 0.1 Bug ai	2	86	December 6, 2025
Floating numbers in RTL layout UX	5	660	September 28, 2020
Allow for decimals in point values UX gamification	3	231	May 25, 2023

AI bot personas don’t accept decimals for temperature, top_p

Related topics