Closed
Bug 249824
Opened 22 years ago
Closed 21 years ago
Event bug for p.m. times "Your start time is after your end time" when it's not
Categories
(Calendar :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: peterg.miller, Assigned: mostafah)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040614 Firefox/0.9
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040614 Firefox/0.9
Any time I try to ajust the end time for an afternoon event using the clock
widget I get the error above, or the event goes into the morning!
Reproducible: Always
Steps to Reproduce:
1.Double click calendar on pm time
2. Enter a Title
3. Click the Clock for the End time
4. Select a new time after the start (> default 1 hr)
5. Click OK
Actual Results:
Error message "Your start time is after your end time"
Expected Results:
Created a longer event
I have not been able to reproduce this bug.
Can you provide the calendar version number (help | about calendar, yyyymmddhh-cal)
Can you provide specific date and times that cause this bug?
Are you clicking on the second row of hours in the time picker?
0 1 2 3 4 5 6 7 8 9 10 11
12 13 14 15 16 17 18 19 20 21 22 23
So to pick 4pm, click on the box below 4, i.e., 16.
Comment 2•21 years ago
|
||
WFM, TB 0.8 (20041024) and extension 2004100812
However I don't use AM/PM for time so it might be something with locales?
(In reply to comment #1)
> I have not been able to reproduce this bug.
>
> Can you provide the calendar version number (help | about calendar,
yyyymmddhh-cal)
>
> Can you provide specific date and times that cause this bug?
>
> Are you clicking on the second row of hours in the time picker?
> 0 1 2 3 4 5 6 7 8 9 10 11
> 12 13 14 15 16 17 18 19 20 21 22 23
> So to pick 4pm, click on the box below 4, i.e., 16.
>
Calendar 2004110411-cal (just installed). Has been happenning on all versions
for months.
(In reply to comment #1)
Any afternoon date displays the bug, for example 2004/11/11 2:00. Double click
the 2-3 pm box, drop down the end time, click on 17, tab, tab again and the
message appears.
Yes, clicking on second row.
Pete
(In reply to comment #2)
> WFM, TB 0.8 (20041024) and extension 2004100812
> However I don't use AM/PM for time so it might be something with locales?
I am using stock standard settings, and am not typing in any am/pm indicators
either. My timezone is set to Australia/Sydney.
I am still not able to reproduce this bug.
On w2k,
set timezone to Sydney (GMT+10) (click right on clock in toolbar)
set time format to h:mm:ss tt (settings | control panel | Regional Options)
TB 0.9 or FF1.0, 2004110411-cal.
After opening calendar, verify Help | About shows
Mozilla Calendar
2004110411-cal
Go to week view.
Double-click the 2pm box on thu 11/11.
The New Event dialog appears, dates 11/11, start time 2:00 PM, end 3:00PM
Click the downward pointing triangle button next to 3:00pm.
The time picker appears show two rows of hours.
Click 17.
17 is highlighted, and end time becomes 5:00 PM
type tab
The picker disappears, the 5:00 PM is selected.
type tab
5:00 pm is no longer selected, outline appears around next control label,
"This event lasts all day"
Seems to work fine.
(A remote possibility is that somehow old calendar files are being read instead
of the new xpi. This bug was originally reported last summer, around the time
that calendar switched
from installing into the (program files) firefox directory
to installing into (documents and settings user application data) profile
extensions directory,
so maybe the old file is hanging around somehow.
A. For example, is there a file
c:\Program Files\Mozilla Firefox\chrome\calendar.jar ?
To clean this up, uninstall firefox and delete its
c:\Program Files\Mozilla Fireox
directory, then reinstall firefox from scratch.
B. You can also try starting it up with a clean profile. Move your old profile
directory and restart firefox, or run firefox command with parameter
firefox.exe -profilemanager
See http://www.mozilla.org/support/firefox/profile )
This bug is repeated on my site and I managed to get a way to "solve" it. The
time format in Reginal Options is very critical:
tt hh:mm:ss => NG
tt h:mm:ss => NG
HH:mm:ss => OK
H:mm:ss => OK
hh:mm:ss tt => OK
Hope this is helpful.
Thanks, Rupert. Pete, does your PM appear before or after the time?
If Pete's format does not have tt before the time like Rupert's, then Rupert's
bug is a separate bug.
Rupert, is tt before the time the default for some region(s)? Which region(s)?
What strings are used for tt? AM and PM? or 午前 and 午後 ? Or something else?
My region is Taiwan and OS is Windows ME. The items for time format are { "tt
hh:mm:ss", "tt h:mm:ss", "HH:mm:ss", "H:mm:ss" }; the items for AM is { "AM", "
上午" }; the items for PM is { "PM", "下午" }.
My original setting that caused bugs was {"tt hh:mm:ss", "AM", "PM"}. My setting
now is {"HH:mm:ss", "AM", "PM"} and it works well.
Comment 10•21 years ago
|
||
I'll assume Pete's problem is not the same as Rupert's.
I added Bug 270724 to address Rupert's problem.
| Reporter | ||
Comment 11•21 years ago
|
||
(In reply to comment #8)
> Thanks, Rupert. Pete, does your PM appear before or after the time?
> If Pete's format does not have tt before the time like Rupert's, then Rupert's
> bug is a separate bug.
>
> Rupert, is tt before the time the default for some region(s)? Which region(s)?
> What strings are used for tt? AM and PM? or 午前 and 午後 ? Or
something else?
Hi,
It turns out this was a Regional Settings problem, in that the time format was
set to "h:mm:ss tt", but the AM/PM indicators were blank. Changing the
indicators to the proper settings or to "H:mm:ss" fixed the problem. It is
strange that this has not affected any other of my programs, but there you go!
Thanks for your help guys.
Pete
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
Comment 12•20 years ago
|
||
The bugspam monkeys have been set free and are feeding on Calendar :: General. Be afraid for your sanity!
QA Contact: gurganbl → general
You need to log in
before you can comment on or make changes to this bug.
Description
•