[BUG] not a valid decimal in a DynamicForm validation

[simokris]

Hi,

I’m facing this bug when I try to validate a DynamicForm with a localFloat field.

What I expect is that when I put a correct value the validation passes without error, but in some cases the validation returns a “not a valid decimal” error.

These are the steps to reproduce the problem which only happens after other validation errors:

1. Fill 'integer' field with incorrect value (i.e. 'hello')
2. Fill 'account' field with a correct value (i.e. 1200.5)
3. Validate
4. Validate again

If you correct the integer field, putting a valid value and validate it again, the error remains on the 'account' field.

In this case I suppose the problem is the fact that it keeps the format characters.

Other ways to produce this error are:

1. Fill the field with the value: 9.00 and validate (if you try with 9.01 the error disappear)
2. Fill the field with a correct value and press enter before validating (this also happens with other keys)

ISC_VERSION :

1. v10.0p_2015-11-18/Enterprise Development Only

OS and Browser: Internet Explorer 11.0.9600.16384 x64 on Windows 8.1 Pro x64


Code snippet to be used: here

isc.DynamicForm.create({
     ID: "boundForm",
     dataSource: "type",
     fields: [
         {name: "intField"},
         {
         name: "account",
         type: "localeFloat",
         format: ",##0.00 €",
         defaultValue: 0
         }
     ]
});
 
isc.Button.create({
    top: 60,
    title: "Validate",
    click: "boundForm.validate()"
});

[Medioman92]

Easier steps to reproduces the bug:

1. fill "account" field with some decimal value, for example 1200.50
2. Press TAB
3. Press validate button

[Isomorphic]

This is fixed now and will be available in nightly builds since today (2015-11-23).

[Medioman92]

this is also affecting version "SNAPSHOT_v10.1d_2015-11-24/EVAL Development Only" on Internet Explorer 11.0.9600.16384 x64 on Windows 8.1 Pro x64

[Isomorphic]

After the fix mentioned earlier in this thread this will not happen if you navigate between form fields using <TAB>.

There's another bug though, when you mouse click formatted field its value is not "unformatted" before editing, which is happening with validation also. We'll update this thread when it will be resolved.

[Isomorphic]

This is fixed now, try the next nightly build (Nov 26 or above).