Closed
Bug 290910
Opened 20 years ago
Closed 18 years ago
Automatically set back to AM after selecting a time of PM and click some other fields.
Categories
(Calendar :: Internal Components, defect)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: weonheec, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ko-KR; rv:1.7.6) Gecko/20050318 Firefox/1.0.2 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; ko-KR; rv:1.7.6) Gecko/20050318 Firefox/1.0.2 I am using Korean version of Windows XP. In Event or Task edit menu, I can not set any of PM time in start and due time. It is automatically set back to AM after I click other field. Here AM and PM are actually equivalent Korean words. Reproducible: Always
Summary: Automatically set back to AM after selecting a time of PM and click some other fields. → Automatically set back to AM after selecting a time of PM and click some other fields.
Version: unspecified → Sunbird 0.2b
Comment 1•19 years ago
|
||
Does this bug still exist in Sunbird 0.3a2?
Reporter, Can you attempt this with the latest Sunbird nightly build (http://ftp.mozilla.org/pub/mozilla.org/calendar/sunbird/nightly/latest-trunk/) or with the Sunbird 0.3 release build? I attempted this both in my timezone and with the Asia/Seoul timezone setting, and I cannot reproduce the scenario you describe. Furthermore, if you have other details or more clear steps to recreate, please add those to the bug. I have removed the QAWanted flag from this bug since it does appear to be fixed in 0.3, but we'll wait to hear from the reporter before marking as WFM.
Keywords: qawanted
Comment 3•18 years ago
|
||
(In reply to comment #2) > I have removed the QAWanted flag from this bug since it does appear to be fixed > in 0.3, but we'll wait to hear from the reporter before marking as WFM. No response from reporter. Marking WFM.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
Updated•18 years ago
|
Status: RESOLVED → VERIFIED
Version: Sunbird 0.2b → Sunbird 0.2
You need to log in
before you can comment on or make changes to this bug.
Description
•