Closed
Bug 1091182
Opened 10 years ago
Closed 6 years ago
[Calendar] Week tab shows 24 hour format after turning off auto-time and then changing City
Categories
(Firefox OS Graveyard :: Gaia::Calendar, defect)
Tracking
(b2g-v2.1 affected, b2g-v2.2 unaffected)
RESOLVED
WONTFIX
Tracking | Status | |
---|---|---|
b2g-v2.1 | --- | affected |
b2g-v2.2 | --- | unaffected |
People
(Reporter: jlee, Unassigned)
References
()
Details
(Whiteboard: [2.1-exploratory-3])
Attachments
(1 file)
30.27 KB,
text/plain
|
Details |
Description: When turning off auto-time and then changing city the Week tab will appear with 24 hour format. 12 hour format is selected in Settings. Repro Steps: 1) Update a Flame device to BuildID: 20141029001202 2) Open Settings 3) Scroll to 'Date & Time' and select 4) Change city to New York 5) Make sure 'Set automatically' is checked on 6) Make sure hour format is set to 12 hour 7)Exit to Homescreen 8) Tap on Calendar app 9) Tap on Week tab 10) Notice 12 hour format 11) Exit to Homescreen 12) Tap on Settings 13) Unselect 'Set automatically' 14) Exit to Homescreen 15) Tap on Calendar app 16) On Week tab, notice 12 hour format 17) Exit to Homescreen 18) Select Settings 19) Change City to Los Angeles (Also make sure Time Format is still 12 hour) 20) Exit to Homescreen 21) Tap on Calendar app 22) Tap on Week tab 23) Observe Actual: When turning off auto-time, opening Calendar app, changing city in Settings, and then returning to the Calendar week tab, week tab appears in 24 hour format. Expected: 24 hour format will not appear in Calendar app unless user changes setting to 24 hour. Environmental Variables: Device: Flame 2.1 BuildID: 20141029001202 Gaia: eb0aab0f13c78c7ac378ad860e865c4b6eaf669f Gecko: 318019f80a8e Gonk: 48835395daa6a49b281db62c50805bd6ca24077e Version: 34.0 (2.1) Firmware: V188 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Notes: Needs app restart to correct Repro frequency: 100% See attached: video clip (http://youtu.be/gDDfHwZ6cIk), logcat (24hour_logcat.txt)
Reporter | ||
Comment 1•10 years ago
|
||
-Does not occur on 2.0 due to no 24 hour setting option. Device: Flame 2.0 (319mb)(Kitkat Base)(Full Flash) BuildID: 20141029000205 Gaia: 9f5b6f025e528fabfcc068782cb9b492cb51a7f9 Gecko: de8cfd54bf93 Gonk: 48835395daa6a49b281db62c50805bd6ca24077e Version: 32.0 (2.0) Firmware: V188 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 -Issue does not occur on 2.2. Device: Flame 2.2 Master (319mb)(Kitkat Base)(Full Flash) BuildID: 20141029040208 Gaia: 35e87ac4324f0f3abd93dcc70d61c9f37256a0f5 Gecko: 7e3c85754d32 Gonk: 48835395daa6a49b281db62c50805bd6ca24077e Version: 36.0a1 (2.2 Master) Firmware: V188 User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(dharris)
Not nominating this issue to block as it takes many steps and is recoverable
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
status-b2g-v2.0:
unaffected → ---
Flags: needinfo?(dharris)
Comment 3•6 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•