Originally Posted by
michaeld
I'm guessing this is an extjs bug?
I don't think so. I believe this is a defect in Ext.NET.
The issue appears to be a problem with how the DateTime object is serialized in the DisabledDates collection.
Here's a simplified .aspx code sample demonstrating how to reproduce the issue.
Example
<%@ Page Language="C#" %>
<%@ Register assembly="Ext.Net" namespace="Ext.Net" tagprefix="ext" %>
<script runat="server">
protected void Page_Load(object sender, EventArgs e)
{
this.DatePicker1.SelectedDate = DateTime.Today.AddDays(-10);
this.DatePicker1.DisabledDates.Add(new DisabledDate(DateTime.Today));
}
</script>
<!DOCTYPE html>
<html>
<head runat="server">
<title>Ext.NET Example</title>
</head>
<body>
<form runat="server">
<ext:ResourceManager runat="server" />
<ext:DatePicker ID="DatePicker1" runat="server" FieldLabel="Date" />
</form>
</body>
</html>
The DisabledDate is serialized to the following JavaScript... which is not correct:
disabledDates : [ new Date(1353394800000 - 0700) ]
Should be an easy fix.