Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    Strange behavior with date validator in ListGrid

    Hi,

    there is a strange behavior with validators in combination with date fields in listgrids.

    I modified your inline data example to demonstrate it:
    http://www.smartclient.com/#inlineData

    Just replace the original code with the below one and click on "Try it":

    Code:
    isc.ListGrid.create({
        ID: "countryList",
        width:500, height:224, alternateRecordStyles:true,
        canEdit: true,
        editEvent: "click",
        listEndEditAction: "next",
        validateOnChange:true,
        fields:[
            {name:"countryCode", title:"Code"},
            {name:"countryName", title:"Country"},
            {name:"capital", title:"Capital"},
            {name:"from", title:"from",type: "date", validators:[{type:"required"}]},
            {name:"until", title:"until", type: "date", validators:[{type:"required"}]}
        ],
        data:[
            {countryCode:"US", countryName:"United States", capital:"Washington, DC"}
        ]
    })
    My modification:
    - canEdit:true
    - listEndEditAction:"next"
    - validateOnChange:true
    - added two date fields ("from" and "until") with validators

    Ok, now add a new record, place the cursor to the Capital or Country field and click directly on the date picker to choose a date for the "from" or "until" field without moving the cursor to one of the date fields. After you've picked any date from the picker, it will not appear in the grid.

    Can you reproduce this case? I think this could be a bug or what do you think?

    Cheers

    #2
    Not reproducible with the latest code.

    Comment


      #3
      It seems to depend on the browser. I'm using Firefox 5.0 and 3.6 and with both it doesn't work.
      See my screencast: http://www.youtube.com/watch?v=YEugz3faAJ8

      I tried the same test with Chrome 13.0.782.32 beta-m and it works fine. What browser did you use?

      Comment


        #4
        Did you check this behavior with Firefox in the meantime?

        Comment


          #5
          Thanks for your help identifying this. We've now fixed it - the fix will be present in the upcoming 8.1 release.

          Comment


            #6
            Is there a date set for this 8.1 release?

            Comment

            Working...
            X