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 be between 0 … 100 and then this would be an UX issue. But how it acts on iPad/iPhone my bet is a bug.

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 fiddling with stuff downstream, a minimal fix would be only to perform the replace it fhe (c) is actually there, that said I would recommend against this hack anyway and do this in markdown prettify. ™ Back in the day we disabled this replacement here: app/assets/javascripts/discourse-markdown-it/src/features/custom-typographer-replacements.js c78019032 // -- → –, --- → — // --> to → ← → ← ↔ ↔ // (pa) (PA) → ¶ // // Disabled replacements: // // (c) (C) → © // (r) (R) → ® // (p) (P) -> § What you want is some sort of plugin that re-enables it.

[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 :winking_face_with_tongue: But back then it changed the format to 0,x when I clicked save. Now it messes numbers right away when comes a real number (well, zero is a real number, kind of…).

Its this … The type=number thing is causing issues on European keyboards/locales. When we ask the component what the value is we get a 0,4 which is correct but you don’t want code all through your code base that says: if Europe Locale then replace(",",".") etc… @cvx / @david what is the “correct” solution here, do we need our own Input here vs using Input from @ember/component ?

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 to deny every characters than right ones.

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: Force decimal point instead of comma in HTML5 number input (client-side) html, google-chrome, input, numbers answered by Peter on 12:02PM - 30 Sep 11 UTC (Should work for either ember’s <Input or simple <input)

Will be fixed with: https://github.com/discourse/discourse-ai/pull/518

[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

Product Support

Topic		Replies	Views
Format numbers depending on selected locale Feature translation , polls	3	2533	June 25, 2015
Thousand separator silently ruins inputted value in settings Bug fixed	7	781	July 8, 2024
Can't enter AI model cost of less than 0.1 Bug ai	1	177	December 2, 2025
The default locale detector agent has conflicting instructions Bug ai , dynaloc	4	165	September 17, 2026
Floating numbers in RTL layout UX	4	748	September 28, 2020

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

Related topics