fullcalendar confusion with UTC and local date
<p>I do let fullcalendar initialize normally. So it represents current date. (Midnight->midnight, 1day, 1h slots)</p>

<p>From some other datasource I get data with timestamps. The format is "YYYY-MM-DD HH:mm" (transmitted as a string, no timezone information)</p>

<p>So I convert that string to a moment object and test against fullcalendar.start and .end to see if it is within. </p>

<pre><code>moment("2016-04-07 00:00") == $('#calendar').fullCalendar('getView').end
</code></pre>

<p>This results in <strong>false</strong> though the following command</p>

<pre><code>$('#calendar').fullCalendar('getView').end.format("YYYY-MM-DD HH:mm")
</code></pre>

<p>returns</p>

<pre><code>"2016-04-07 00:00"
</code></pre>

<p>I also tried to compare with diff</p>

<pre><code>moment("2016-04-07 00:00").diff( $('#calendar').fullCalendar('getView').end,"minutes")
</code></pre>

<p>which returns</p>

<pre><code>120
</code></pre>

<p>Some research on the calendars.end object in Chrome Dev Tools revealed that it internally is represented as</p>

<pre><code>2016-04-07 02:00 GMT+0200
</code></pre>

<p>This looks strange to me. I am in timezone 2h ahead of GMT. So it should correctly say 2016-04-07 00:00 GMT+0200, should it not?
This also explains why the diff test above resulted in 120 minutes. </p>

<p>Can someone help? I do not get where the conversion problem comes from. I am using only dates with no timezone information. And as said above, fullcalendar initalizes with no gotodate information and shows a time bar from 00:00 to 00:00. So why does it come that there is this 2h difference?</p>