Issue 2217: [beta] dayClick incorrect date with minTime
Status:  Released
Owner: ----
Closed:  Aug 2014
Reported by bhol...@snapappointments.com, Jul 28, 2014
On dayClick (and likely other functions as well) the returned time within the date is being calculated based on the minTime value. 

For example, if minTime is set to 08:00:00, when you click on a cell at 09:00, the returned time is 01:00 regardless (it treats minTime as 00:00:00).

If minTime is set to 10:00:00, when you click on a cell at 10:00, the returned time is 00:00.

Basically, the coordinates are accurate but the minTime is being ignored - the function assumes the entire calendar is being displayed.

The only way to get an accurate time within the 'date' value is to display the entire calendar. I would create the JSFiddle but the issue is straight-forward and I have spent a lot of time reporting previous bugs that get overlooked; obviously only so much can be done in the time available (and finding that time is difficult in Adam's case when managing an open source project - his dedication certainly cannot be questioned) but I have found 11 bugs in 2.1-beta1 and it would take less time for me to fix them myself than to report them with a specific JSFiddle each time. Also, as it is a beta, I have to assume they are aware of a number of these issues already.

Jul 28, 2014
Project Member #1 adamrs...@gmail.com
I can confirm this problem. Sorry about that. Will get it fixed.

For the other bugs you are having, if you haven't already reported them, I would really like to hear about them. Don't worry about a JSFiddle for each. Please just post a description of how to recreate. I'll ask follow-up questions if necessary.

Thank you so much for helping out with the beta
Summary: [skeleton] dayClick returning incorrect date (was: dayClick returning incorrect date (skeleton))
Status: Accepted
Labels: Type-Bug
Jul 28, 2014
#2 bhol...@snapappointments.com
Excellent - thank you. The last thing you owe me is an apology - you deserve an award.

As I mentioned before, my concern was that with all of the rapid progress you guys have been making recently, I would have to maintain several JSFiddle's and continually update them all with each new release in order to have the issues addressed (even if the applicable code is unchanged in an update, from your perspective you don't want to deal with reproducing issues that may have potentially been fixed already).

I understand the need for strict bug-reporting requirements in order to maintain a level of organization and control over this project (I know as well as anyone how often "bugs" are, in reality, user error). At the same time, I can only justify a limited amount of time to reporting what we discover.

I will get together a list of what we have found, compare to everything that has already been reported (you have already accepted the 2 bugs I have reported which were included in my count of 11 above) and provide descriptions on recreating them. I will list them out separately and then email you the links.

As always, appreciate all that you do.
Aug 14, 2014
Project Member #3 adamrs...@gmail.com
forgot to mention... this should be fixed in beta2
Aug 14, 2014
Project Member #4 adamrs...@gmail.com
(No comment was entered for this change.)
Summary: [beta] dayClick incorrect date with minTime (was: [skeleton] dayClick returning incorrect date)
Status: Implemented
Aug 14, 2014
Project Member #5 adamrs...@gmail.com
(No comment was entered for this change.)
Labels: milestone-skeleton
Aug 26, 2014
Project Member #6 adamrs...@gmail.com
This issue has been resolved with the official release of v2.1.0:
http://blog.arshaw.com/1/post/2014/08/fullcalendar-210-released.html

Please post any follow-up bug reports or feature requests as separate issues. Thanks.
Status: Released