Closed Bug 283512 Opened 20 years ago Closed 18 years ago

New event's default date (by double click on day in month or multiweek view) is one day later

Categories

(Calendar :: Sunbird Only, defect)

x86
Windows 2000
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: jan, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041217 Build Identifier: Sunbird Standalone: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20050203 Mozilla Sunbird/0.2 If the current time is in the last 29 minutes (for multiweek view) or in the last 4 minutes (for month view) of a day, a new event's default date is one day later than the day you double clicked on. The default date is set to the next day only when double clicking, this bug does not affect the context menu "New event...". This bug is probably caused by the two getNewEventDate() functions. Reproducible: Always Steps to Reproduce: 1. Set your clock to 11:56 pm. 2. Double click on a day in multiweek or month view in order to add a new event. Actual Results: Default start date is on the next day. Expected Results: Default start date should be on the day you clicked on.
Summary: New event's default date (by double click on day in month of multiweek view) is one day later → New event's default date (by double click on day in month or multiweek view) is one day later
Confirmed in both Sunbird 0.2rc2 and Calendar 2005011112 (firefox, WinXP). It seems to be due to the conflict between getting today's date and rounding to the next 5 minute increment, which becomes 12:00am and hence, the next day. Why the multiweek view is rounding from the half-hour, I don't know though.
Status: UNCONFIRMED → NEW
Ever confirmed: true
It's nearly the same function, but in multiweekView.js the rounding/inc is done by 30 minutes rather than 5 minutes. So i guess this can be fixed quite easily.
*** Bug 290010 has been marked as a duplicate of this bug. ***
QA Contact: gurganbl → sunbird
*** Bug 315081 has been marked as a duplicate of this bug. ***
Removing gCalendarWindow.currentView will probably fix this bug, or at least make it much easier to fix.
Depends on: 329582
Reassigning all automatically assigned bugs from Mostafa to nobody@m.o Bugspam filter: TorontoMostafaMove
Assignee: mostafah → nobody
Works for me using Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.4pre) Gecko/20070331 Calendar/0.5pre Current system time is set to 23:57. Double clicking in the multiweek/month view creates an event that starts on the clicked day at 23:00 and duration as specified by preference calendar.event.defaultlength.
Also WFM with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.4pre) Gecko/20070417 Calendar/0.5pre -> Marking WFM.
Status: NEW → RESOLVED
Closed: 18 years ago
No longer depends on: 329582
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.