Hi,
I get this error when loading a page of my project:
0x800a138f - JavaScript runtime error: Unable to get property 'value' of undefined or null reference.
MaskedEdit.debug.js
The code that fails is:
// normalize initial value (Date)
ConvFmtDateTime: function(input, loadFirst) {
var arr = this._SplitDateTime(input),
partdt = arr[0],
parttm = arr[1];
if(parttm.split(" ").length == 2)
parttm += " " + parttm.split(" ")[1];
partdt = this.ConvFmtDate(partdt, loadFirst);
parttm = this.ConvFmtTime(parttm, loadFirst);
return partdt + " " + parttm;
},
Input parameters are:
input = "2/12/2015 10:50:07"
loadFirst = true
parttm is undefined so the line "if(parttm.split(" ").length == 2)" throws the exception.
Regards,
Josep
Comments: Hi, Josep, I tried to reproduce this MaskedEditExtender behavior in AJAX Control Toolkit v4.1.50927 and it behaves exactly like it does in the latest version of the toolkit. So, I think it is currently much easier to a add leading zero to the loading value, because analyzing this value inside _SplitDateTime() function requires a lot of changes in the MaskedEditExtender's code, which can lead to numeric errors.
I get this error when loading a page of my project:
0x800a138f - JavaScript runtime error: Unable to get property 'value' of undefined or null reference.
MaskedEdit.debug.js
The code that fails is:
// normalize initial value (Date)
ConvFmtDateTime: function(input, loadFirst) {
var arr = this._SplitDateTime(input),
partdt = arr[0],
parttm = arr[1];
if(parttm.split(" ").length == 2)
parttm += " " + parttm.split(" ")[1];
partdt = this.ConvFmtDate(partdt, loadFirst);
parttm = this.ConvFmtTime(parttm, loadFirst);
return partdt + " " + parttm;
},
Input parameters are:
input = "2/12/2015 10:50:07"
loadFirst = true
parttm is undefined so the line "if(parttm.split(" ").length == 2)" throws the exception.
Regards,
Josep
Comments: Hi, Josep, I tried to reproduce this MaskedEditExtender behavior in AJAX Control Toolkit v4.1.50927 and it behaves exactly like it does in the latest version of the toolkit. So, I think it is currently much easier to a add leading zero to the loading value, because analyzing this value inside _SplitDateTime() function requires a lot of changes in the MaskedEditExtender's code, which can lead to numeric errors.