Closed Bug 361650 Opened 18 years ago Closed 18 years ago

Default event start time is 00:00 and not the next full hour

Categories

(Calendar :: Calendar Frontend, defect)

Lightning 0.3
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: andreas.treumann, Assigned: jminta)

Details

(Keywords: regression)

Attachments

(1 file)

REPRODUCTION:
=============

- choose File -> New... -> Event


RESULT:
=======

- the default start time is 0:00

EXPECTED RESULT:
================

Start time has to be on the next full hour. E.g. it is 9:40am the preselected time has to be 10:00am.

REPRODUCIBLE:
=============

- always
I mentioned this issue as a side note in Bug 360821 Comment #0, the regression range is the same as in Bug 360821. Probably also regressed by the checkin for Bug 346934.
I see this is indicated as Lightning only, but with Sunbird nightly 2006-12-05 (linux) i got the same problem...
Regression range:
 Works in Lightning/0.4a1 (2006110607); Fails in Lightning/0.4a1 (2006110708)
 Works in Sunbird/0.4a1 (2006110607);   Fails in Sunbird/0.4a1 (2006110706)
Component: Lightning Only → Calendar Views
Keywords: regression
QA Contact: lightning → views
Summary: Feature that 'Start time has to be on the next full hour' doesn't work → Default event start time is 00:00 and not the next full hour
Attached patch tidy things up — — Splinter Review
Tidying up a bunch of functions here.  If we don't have a startDate, or if the date is an all-day event (and hence came from the controller), we should set the hour.
Assignee: michael.buettner → jminta
Status: NEW → ASSIGNED
Attachment #247590 - Flags: second-review?(mvl)
Attachment #247590 - Flags: first-review?(lilmatt)
Comment on attachment 247590 [details] [diff] [review]
tidy things up

r=lilmatt
Attachment #247590 - Flags: first-review?(lilmatt) → first-review+
Comment on attachment 247590 [details] [diff] [review]
tidy things up

>Index: calendar/base/content/calendar-item-editing.js
>     if (!startDate) {
>         startDate = currentView().selectedDay.clone();
>+        startDate.isDate = true;
>+    }
>+    if (startDate.isDate) {
>         startDate = startDate.clone();

That means that without a startdate, you will clone twice. You should avoid that. It's overkill.

r2=mvl with that fixed.
Attachment #247590 - Flags: second-review?(mvl) → second-review+
Patch checked in, with nits picked.
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
verified with
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20061211 Calendar/0.4a1
Status: RESOLVED → VERIFIED
Whiteboard: [litmus testcase wanted]
Litmus testcase 3020 created
Whiteboard: [litmus testcase wanted]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: