This still is a problem for us. I am entering a number of all day events...camps, holidays that sort of thing, and it continues to show up as 2 days. For example, I enter 'New Years Day' on Jan 1 as all day event and it comes up showing from 1st - 2nd Jan (2 days). Im in Australia, using Mac OS, Safari. I have also tried it on Mozilla, with the same results. It's getting frustrating as camp dates appear to start a day earlier and finish a day later than is the case.

Try this work-around. Not the best, but it works. Add the event giving it an Event Name and optionally an Event Description. However, don't select "All day event" and leave the Start/Stop times as they defaulted. Then, click Create Event. After you're returned to the calendar click the event you just created and then click Edit event details and location. This time, select "All day event", make any other changes you want, and click Update Event. You should now see your all day event on a single day the way you want it. Give it a try.

Am having the same problem, and it impacts all day repeating events that have a later date that falls on a DST change. For example, I create Fast Sunday on January 3, 2016 repeating for the whole year. At least one of those repeat first Sundays of the month falls on DST change, so every fast sunday now shows Sunday through Monday year long. This has never been an issue in past years (this is my fourth year preparing the stake calendar).

Tried to create a one day event on another day and drag it over, but that fails on March 8 2016 (Start of DST) and it converts it into a two day event. My local time zone is Pacific if that makes a difference. The attachment shows what is entered and how it displays.

We have had issues calendaring events for this entire year. If I schedule an event for 3 days it schedules it for 4 or 5 days. I scheduled YW Camp Monday through Saturday and it scheduled it through Sunday. Most of the time it adds an extra day at the beginning and an extra day at the end. When is this going to get fixed?

The release went out today, Try it out. However, we detected a problem with setup/takedown times. When you create a new event, those fields should be "none" by default, but they are blank causing an error message if the user doesn't set it to "none." We will try to fix that fast or will need to roll back the release because it is pretty confusing to the user because the error message just says data fields are incomplete.