Closed Bug 256979 Opened 20 years ago Closed 11 years ago

Times are always assumed AM, even if it makes no sense

Categories

(Calendar :: Sunbird Only, enhancement)

x86
Windows 2000
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: bugzilla, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040707 Firefox/0.9.2 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040707 Firefox/0.9.2 The standard for a time entered as just a number is AM. If this will result in the end time being before the start time, shouldn't we automatically assume the user means PM? Not really a bug, but a heuristic like this (or saying <6:00 is probably AM) can be the difference between functional and pleasant. Reproducible: Always Steps to Reproduce: 1. 2. 3.
This is probably better desribed as a enhancement in the severity option.
Severity: minor → enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true
I don't like this one. If we assume that a time is PM to prevent it from being before the start time, this could cause problems if a user wants to edit an end time first. Consider the scenario: 1.) I schedule a meeting starting at 14:00, ending at 15:00. 2.) I'm told there's a conflict, and the meeting needs to finish by 11:00am. 3.) I open the event and change the end time to 11:00am first, because that's what's on my mind, planning to change the start to 10:00am next. 4.) If calendar assumes the time is PM, because it is before the start time, it will change the end time to 23:00, which is definitely not what I want. I would be required to change the start time first, which I don't think should be necessary. Note: It would need to be changed on the fly, as I've described, otherwise there would be issues with the 'Your start time is before your end time' warning. The only other place to change it would be on clicking the OK button, but this would be even worse, since an event could go through with the warning still being displayed. Nominating for WONTFIX.
QA Contact: gurganbl → sunbird
I think the problem here is that you set a time in 24h system, but it displays the time in 12h system. It's not assuming am, because am isn't a factor? IMHO if there's going to be a fix for this problem, the solution would be having an am/pm selector and switching the whole process to 12h system. So I'd agree with the wontfix.
Reassigning all automatically assigned bugs from Mostafa to nobody@m.o Bugspam filter: TorontoMostafaMove
Assignee: mostafah → nobody
Sunbird development has been suspended.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.