Was this defect not corrected last year ???
Last year I reported the problem with the
on User Input sections NOT being triggered BEFORE the
on Click (or
on Success) sections for
Date fields when the user ...
a) changed the values via keyboard (instead of using the Calendar Widget)
b) followed it up with a click of the Form Button
As I recall ... after a number of interim measures, this issues was reported as fixed.
I also recall verifying it at the time.
Today, one of my clients reported a problem ... which after considerable investigation shows that the defect is NOT fixed.
The (Stateless) Form is setup so that the on User Input section of a Date field updates another (disabled, Single Line Text) field with the corresponding Day of Week ... this works fine as long as ...
- the user uses the Calendar widget to update the Date field ... and then clicks on the Form Button
- changes the date via keyboard and clicks elsewhere first before clicking on the Form Button
But it does NOT work if the user changes the date via keyboard and then clicks on the Form Button ... the old (before update) value of input.Day_of_Week is available to the on Click section ... and the on User Input section code is invoked AFTERWARDS ... causing the insert command to store an incorrect value in the database.
In case the Support Team needs proof, I have setup an example in my Lab Application.
I need to know ...
a) Was this defect not fixed last year ? ... if so, how/when did it get re-introduced ?
b) When can we expect this to be fixed ?
Gaev