My favorites | Sign in
Project Home Issues
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 2086: dayClick does not return ambiguously timed moment - v2Beta
1 person starred this issue and may be notified of changes. Back to list
Status:  Done
Owner:  ----
Closed:  Mar 2014


Sign in to add a comment
 
Reported by astj...@gmail.com, Feb 6, 2014
1. Build from source on v2 beta branch.

2. Add the following to the "agenda-views.html" example:

dayClick: function(d, jsEvent, view) {
  console.log("DAY CLICK");
  console.log("HAS TIME?", d.hasTime());
  console.log("TIME", d.time());
  console.log("ZONE", d.hasZone());
}

3. Click on an all-day area vs. a time slot in any calendar view.

4. I note the following:

When clicking on an all-day area:

DAY CLICK 
HAS TIME? true
TIME  << Time object set to 00:00:00 >>
ZONE true 

When clicking on a time slot:

DAY CLICK 
HAS TIME? true 
TIME  << Time object set to whatever time >>
ZONE false 

---

From the documentation, I anticipated that d.hasTime() would return false for an all-day area (ambiguously timed). Instead, the only difference seems to be that a time-slot does not have a time-zone associated with it in this example.

Am I interpreting the docs wrong or is this a small bug?

Thanks!

Feb 6, 2014
#1 astj...@gmail.com
My bad. It looks like this was fixed in v2 beta2. I jumped the gun before pulling the latest. Sorry! Feel free to close this.
Mar 21, 2014
Project Member #2 adamrs...@gmail.com
(No comment was entered for this change.)
Status: Done
Sign in to add a comment

Powered by Google Project Hosting