if I have a calendar event that spans multiple days, if the date range entered spans the current date, the date parse should be improved to understand that the date range is intended to include the current date. what happens today is that the start date gets moved ahead one year and the date range gets all messed up. this is particularly annoying when editing an event that is a date range in the middle of the range.

as an example, today is October 4, 2007
-if I enter a new event as ‘10/5 – 10/10 foo’ then all is well. event ‘foo’ runs from 10/5/2007 – 10/10/2007
-if I enter (or edit) an event as ‘10/3 – 10/8 bar’ then what I end up with is an event ‘bar’ from 10/8/2007 (the end date) to 10/3/2008 (the start date pushed ahead a year)
since I’m entering the date range as ‘10/3 – 10/8’ it would be nice if the calendar recognized this date range as the current year. (eg. 10/3/2007 – 10/8/2007)

This is a RIDICULOUS bug. Trying to grapple with this today and it’s taking the piss.

Not only does it mess up on initial entry, every time an entry is edited, the original (wrong) start date is remembered in the input field.