Hello,

Think of use numberlonly class to have a global js in survey_runtime.js.

With maxlength i do this, and i can copy/paste.

But numberlonly class are only for Yii ....

I would suggest something like this: http://stackoverflow.com/a/3257682/974390

The "difficulty" is not for [0-9] an -, it's for . and , : langage specific.

Maybe add a inline global var on the survey is the best solution.

Denis

Actually, I've already fixed the comma issue. And as part of that fix, it validates that the entry is a real number - so if you try to enter "1.2.3", or "-1,23,4-5", the field will be blanked onchange.

Since that processing works, it may be fine to just remove the onkeyup function that only lets you enter numbers. If people enter non-numeric values, the field will be blanked and they will have to try again.

Personally, I think that blanking a field may be safer than removing non-numeric values, since people may not notice that the field is shortened by a character (thus realizing they made a typo), but they'll certainly notice if the field gets blanked.

I don't think that's ideal.

Let's say you have a non-mandatory field in question by question mode.

User enters 1,234 instead of the valid 1.234 and submits the page.
He will not notice at all that the field was blanked at submit.

I think validation while typing is the better choice.

It's not blanked at submit - it is blanked onchange - so as soon as they tab off the field. The risk (as you say) is that if they press Next to submit without noticing the onchange event.

Perhaps another option would be to force a re-focus on the field if it gets blanked by this process - that would prevent a submit until they entered a real number (or just left the field blank, which is OK if non mandatory)

I like the later option better.
So why not validate it as any other field?
I would not blank it,
but rather put out a validation error ('PLease enter a valid number or leave it blank')and stop the page from submitting.
I think that is better than loosing the data (=blanking)

We could certainly add a numbers_only validation option similar to the ones EM now manages and have the field show in pink. I had avoided that since there was also the onkeyup command; but we can move in this direction for a + release (unless you feel this needs to be addressed for 1.92 stable)

That sounds good.

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=8873

Fix committed to Yii branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=8875

New 1.92+ version released.