Open GoogleCodeExporter opened 9 years ago
The following solution fixes the problem.
Original comment by intern...@gmail.com
on 12 Sep 2007 at 11:09
Attachments:
Forgot to update this issue, after testing further the patch above exposes a
really
funny error in Firefox - if used it will sometimes generate dates with the time
zone
GMT+200, which, if we were living on Jupiter would be quite reasonable.
The following method of setting the date plays nice with Firefox:
public Date getValue()
{
JavaScriptObject o = getDateJsObj(jsObj);
Date date = null;
if (o != null)
{
date = new Date(getFullYear(o) - 1900, getMonth(o), getDate(o));
}
return date;
}
private native int getFullYear(JavaScriptObject dt)/*-{
return dt.getFullYear();
}-*/;
private native int getMonth(JavaScriptObject dt)/*-{
return dt.getMonth();
}-*/;
private native int getDate(JavaScriptObject dt)/*-{
return dt.getDate();
}-*/;
private native JavaScriptObject getDateJsObj(JavaScriptObject df)/*-{
var val = df.getValue();
return (val == '' || val === undefined) ? null : val;
}-*/;
Original comment by intern...@gmail.com
on 21 Sep 2007 at 7:58
I think it might be related to issue 225
http://code.google.com/p/gwt-ext/issues/detail?id=225
Original comment by pgil%agn...@gtempaccount.com
on 6 Mar 2008 at 10:53
This should fix it... Will try to incorporate in in SVN soon.
http://extjs.com/forum/showthread.php?p=167193
Original comment by mlim1...@gmail.com
on 30 Sep 2008 at 6:07
This is still not fixed!!!! See this
http://www.extjs.com/forum/showthread.php?t=28875&page=4
We are still on gwt-ext-2.0.6 and planning to upgrade to SmartGWT in near
future. This bug hit us bad and
our U.S clients have started reporting problems of their critical applications
crash. Would it be possible for you
to urgently incorporate this fix and provide a patch for gwt-ext-2.0.6 or
suggest a workaround. Thanks
Original comment by visha...@gmail.com
on 15 Mar 2010 at 1:11
Original issue reported on code.google.com by
intern...@gmail.com
on 12 Sep 2007 at 10:17