Since i've wasted half my morning tracking this one down and submitting a request, thought i'd share it in the vain hope someone's come across it before.
I've attached a solution file that you can run and see the errors, aswell as some screenshots that i've sent to IG. I'm very unimpressed with the support responses, and the majority of fixes I get for these products are coming from other users, not Infragistics staff. Yes, i'm in a bad mood and venting.
Basically I have a datefield in a grid and i've set the webdatechooser as its default editor. I click it once, it goes into edit mode and all is sweet. If I click off that field, and then back onto it - it decides to convert the data into american date format, and any numbers over 12 are automatically converted to montghs and the year changes accordingly.
After much head scratching, javascript debugging and hacking and wasted time, I decided to create a sample app and beg forgiveness to the Infragistic Gods. Seemingly, the addition of the tag "Browser=XML" is the culprit, and when it's not there - the issue no longer occurs. But there's a acatch - with the removal of the Browser=XML tag, goes some nice AJAX paging functionality of the grid. Think rock, and hard place.
If anyone's got a solution to this, i'd appreciate it - if anyone else is having a similar problem, this may save you the half day I just spent.
Thanks for providing the case number. I see that this is under a different profile than the first post in this thread, which is why I couldn't find it before.
From what I can see in case number CAS-07653-21LNHT, and as you mentioned, this looks like a problem that occurred in the release build of 8.1, and was fixed in a hot fix for 8.1, as well as in 8.2. While it's unfortunate that this happened in the first place, and required some re-testing to address, I'm glad that the issue itself is resolved. Hopefully, this information will help anyone else who encounters a similar problem with 8.1.
I've made a note of the issues you're encountering on the support section on our website, so that we can look into it in more detail. I'm glad that you mentioned the browser version you are using, as this will likely help our research significantly.
Lastly, if you ever have any comments, questions, or the like about the quality of service provided by Infragistics Developer Support, please feel free to email me at dsmanager@infragistics.com with the details, and I'll be happy to investigate.
Setting the culture to en-AU will do it, but I assume any non-american culture will have the same issue. Case number relating to this request is CAS-07653-21LNHT and the response that I have recieved is to upgrade the version of Infragistics that I have from 8.1 to the latest hotfix. I have since rolled 8.2 over the top, and it no longer occurs in that version - unfortunately this error was occuring in production, and with the 8.2 upgrade numerous files were affected and were needed to be re-tested before hotfixing back to production. Feel free to go through many of the other support requests listed under the account, and you may get an appreciation for my frustration.
While I do have someone from infragistics responding however, is there any chance that you can fix the IG controls that are used to submit support requests? The version of IE I am using is IE6 6.0.3790.3959 SP2, and seemingly whenever I try to select a line of text mid sentence, or select previous lines the control will not allow me to do it - it's extremely frustrating also. I can attach a video of this behaviour also if req'd.
Have you already submitted a support request for this, and if so, what's your case number? You mention that you're "very unimpressed with the support responses," and I'm trying to find out more, but I can't find any existing support requests based on the information available. If you haven't already logged one, please simply let me know.
One of my staff has taken a look at the sample you've provided, and we don't encounter the error you've described. Based on what you've described, we suspect that this may be a culture setting issue, since we ran under an "en-US" culture. What's the culture used on your client machine?