Closed
Bug 491478
Opened 16 years ago
Closed 16 years ago
Labels on all events are incorrect in the Month and Multiweek view (Jan 1, 99)
Categories
(Calendar :: Calendar Frontend, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: web, Unassigned)
Details
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_6; en-us) AppleWebKit/528.16 (KHTML, like Gecko) Version/4.0 Safari/528.16
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b5pre) Gecko/20090427 Calendar/1.0pre
All events on the calendar show up with the time and then Jan 1, 99 in the Month and Multiweek view. This has been in the last few weeks of nightly builds.
Reproducible: Always
Steps to Reproduce:
1. Switch to Multiweek or Month view
2. Add an event
Actual Results:
See screenshots:
http://qkpic.com/f301e
http://qkpic.com/0be0d
Expected Results:
The title of the item should appear in the label instead of the date Jan 1, 99
Reporter | ||
Comment 1•16 years ago
|
||
The second screenshot was to show that everything looks fine within the edit window. Just noticed the same date is showing up in the upcoming list at the top as well.
Comment 2•16 years ago
|
||
The views don't display the date inside the event box, only the time is displayed. For some unknown reason "Jan 1, 99" is appended to each time string in your setup. For example in the event list above the calendar view you see the correct date string + the correct time string + "Jan 1, 99".
I recommend that you check the time format settings of your operating system. (But don't ask me how to do this for Mac OS X.)
Updated•16 years ago
|
Version: unspecified → Trunk
Reporter | ||
Comment 3•16 years ago
|
||
Thanks,
for other afflicted with the same situation the change for Mac OS X is to go to the International Control Panel and remove the date from the Times format section.
Reporter | ||
Updated•16 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Updated•16 years ago
|
Resolution: FIXED → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•