Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Events with no T in datetime not rendering Safari/Mac #4610

Closed
nbcnc opened this issue Apr 5, 2019 · 7 comments

Comments

Projects
None yet
4 participants
@nbcnc
Copy link

commented Apr 5, 2019

This issue only seems to apply to FullCalendar on Safari/Mac (Safari Version 12). I haven't seen this problem in any other browser.

In FullCalendar v4.0.1, events with full times as the start or end (YYYY-MM-DD HH:MM:SS) do not display. However, when the start or end are entered as simple dates (YYYY-MM-DD), they do display.

Here's an example:
https://jsfiddle.net/marcparillo/79mk20p8/

@arshaw

This comment has been minimized.

Copy link
Member

commented Apr 5, 2019

Confirmed.

If you place a T between the date and time, like 2019-04-06T04:30:00, things will work cross-browser. https://jsfiddle.net/uobth91c/

Regardless, I will get this to work cross-browser.

@arshaw arshaw added the Confirmed label Apr 5, 2019

@arshaw arshaw added this to the next minor milestone Apr 5, 2019

@arshaw

This comment has been minimized.

Copy link
Member

commented Apr 5, 2019

@Uudis, in the other thread, you mentioned the dates are requested with the T. Does this happen when FC calls a JSON event feed?

@arshaw arshaw changed the title Events not rendering Safari/Mac Events with no T in datetime not rendering Safari/Mac Apr 5, 2019

@piernik

This comment has been minimized.

Copy link

commented Apr 11, 2019

When can we expect this bug fixed? I't major issue for my clients.

@aravael

This comment has been minimized.

Copy link

commented Apr 11, 2019

i have the same one problem

@aravael

This comment has been minimized.

Copy link

commented Apr 14, 2019

@arshaw, any updates for this issue?

@arshaw

This comment has been minimized.

Copy link
Member

commented Apr 24, 2019

this is fixed in v4.1.0

@nbcnc

This comment has been minimized.

Copy link
Author

commented Apr 24, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.