[Isomorphic]

This support hasn't been added as yet, but *is* queued.

It *will* be added - but it isn't straightforward, and may be intrusive enough that it can't be implement into 5.0, which has been live for a long time.

We'll take a look at what's involved and update here when we have more information/

[pghosh]

Is there an update on timezone support for calendars? Our clients are getting anxious.

[Isomorphic]

We don't actually document full support for a display timezone in Calendars, but there are indeed some issues in this area - we'll look at completing such support in the comiong days and update here when we have more information.

[pghosh]

Yes it works fine if I remove defaultDisplayTimezone.

[Isomorphic]

We asked that you confirm that the Calendar is working if you remove the defaultDisplayTimezone - can you confirm that? We noticed you posted something about starting a new thread, but it wasn't clear if you were confirming the cause of the issue.

[pghosh]

This is a separate issue, related to your defaultDisplayTimezone - we'll take a look at that, but please confirm this works as you expect without a custom timezone.

Any progress on this issue?

[pghosh]

This is a separate issue, related to your defaultDisplayTimezone - we'll take a look at that, but please confirm this works as you expect without a custom timezone.

Should I start a new thread for that? Seemed to be related. I also noticed that the Calendar widget does not honor the specified default timezone instead it always uses the browsers timezone.

[stonebranch2]

Isomorphic,
I already confirmed earlier, the new issue was reported by a different user, "pghosh".
Regards

[Isomorphic]

This is a separate issue, related to your defaultDisplayTimezone - we'll take a look at that, but please confirm this works as you expect without a custom timezone.

[pghosh]

Still missing in July 30th build.

SGWT 5.0p 07/30/2015 10:24
GWT 2.3
Chrome 44.0.2403.125 m

@Override
public void onModuleLoad() {
	DateUtil.setDateInputFormat("YMD");
	DateUtil.setDefaultDisplayTimezone("-08:00");
	DateUtil.setShortDateDisplayFormatter(DateUtil.TOJAPANSHORTDATE);
	DateUtil.setShortDatetimeDisplayFormatter(DateUtil.TOJAPANSHORTDATETIME);
	new VLayout(4){{
		setWidth(600);
		setHeight(400);
		Calendar calendar = new Calendar();
		CalendarEvent[] data = new CalendarEvent[]{new CalendarEvent(1, "Event-1", "Event-1",
				new Date(2015 - 1900, 7, 1, 10, 0, 0), new Date(2015 - 1900, 7, 1, 11, 0, 0))};
		calendar.setData(data );
		addMember(calendar);
		addMember(new Canvas(){{
			setContents("Version: " + Version.getVersion() + " Build date: " + Version.getBuildDate());
			setAutoHeight();
		}});
	}}.show();
}

Seems to work when setDefaultTimezone is not specified.

[stonebranch2]

Working again now. Thanks

[Isomorphic]

In 5.1, there was a check that prevented refreshEvents() from updating cell HTML in the monthView, unless the month had changed. That was incorrect and has been removed for builds dated July 26 and later.

[stonebranch2]

The problem still persists with July 23 build.
Regards

[Isomorphic]

Please retest with a build dated July 23 or later and let us know if you still have issues.

[Isomorphic]

We have a bunch of fixes, for this and other issues, in 5.0 that haven't made it into 5.1 nightlies yet - they should hit in the next day or so - we'll let you know.