search

sidewinderlabs / backplanejs

Other
12 stars 3 forks source link

Valid data failed to be recognised when validating with @resource-less submission #87

Open backplane-import opened 13 years ago

backplane-import commented 13 years ago

Imported from backplanejs Google Code issue 87.

Reporter alex.sansom@webbackplane.com
Date 28 Jul 2010 12:21:16 PM UTC

What steps will reproduce the problem?

Scenario 1 (setting instance data via xf:input)

  1. Open the attached form
  2. In the Applicant 2 -> National insurance number input type: ab121212c
  3. FocusOut of the field, noting the field is now styled as valid (no red background)
  4. Click the 'Validate' trigger. Note the validation message says that the data is invalid

What is the expected output? What do you see instead?

I expect that after entering the valid national insurance number and clicking the 'Validate' trigger, to see the 'Validation:' message change to 'Form data is valid' as, although the submission will fail, it will fail because of a 'resource-error' rather than a 'validation-error'.

Please use labels and text to provide additional information.

This is strange because, if you:

Scenario 2 (setting instance data via xf:select1)

  1. Open the attached form
  2. Change 'Do you have a national insurance number?' select1 to 'No'. Note that the now relevant 'Why not?' field is invalid.
  3. Select a value for 'Why not?', making it valid (no red background)
  4. Click the 'Validate' trigger. Note the validation message says that the data is valid

Both scenarios do basically the same thing, set some instance data but when the data is set with xf:input, it's not recognised as valid.

Ticket status set to Accepted

Priority: Medium Type: Defect

Attachments

nino.html (16.8 KB)

backplane-import commented 13 years ago

Comment by markbirbeck on 28 Jul 2010 8:54:19 PM UTC

I'm assigning this to Frankie because the issue seems to have arisen after the latest changes were incorporated.

Updates

Owner set to fdintino

backplane-import commented 13 years ago

Comment by markbirbeck on 6 Aug 2010 2:59:36 PM UTC

This issue was updated by revision 48c291065b0ce3ebd794867b223766b5c569ca03 (originally 7834ee2f7e).

Although there is obviously an issue here, it seems that it is not to do with the 'xforms-submit-error' handling code, as these tests show.