Closed
Bug 1032981
Opened 10 years ago
Closed 10 years ago
[B2G][Clock]After pressing 'Stop' when an alarm goes off, the check mark does not disappear in the clock app
Categories
(Firefox OS Graveyard :: Gaia::Clock, defect)
Tracking
(b2g-v2.0 unaffected, b2g-v2.1 affected)
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
b2g-v2.0 | --- | unaffected |
b2g-v2.1 | --- | affected |
People
(Reporter: astole, Assigned: mcav)
References
()
Details
(Keywords: regression)
Attachments
(2 files)
When an Alarm that is set to never repeat goes off and the 'Stop' option is selected instead of snooze, the check mark stays on the alarm as if it is still set instead of it getting removed. The alarm does not go off again. Repro Steps: 1) Update a Flame to BuildID: 20140701072955 2) Open the Clock app 3) Set an alarm 4) When the alarm goes off press 'Stop' 5) Open Clock app again Actual: Check mark is not removed from Alarm Expected: After pressing 'Stop' the check mark is removed from the Alarm 2.1 Environmental Variables: Device: Flame 2.1 BuildID: 20140701072955 Gaia: 34a52e7f024cc3d0e3aade94970773d2555f5ccb Gecko: ffb8b976548b Version: 33.0a1 Firmware Version: v122 Repro frequency: 2/2, 100% See attached: Video, logcat
Reporter | ||
Comment 1•10 years ago
|
||
Attaching video and adding qawanted to check other devices and builds.
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.1:
--- → affected
Flags: needinfo?(pbylenga)
Keywords: qawanted
Comment 2•10 years ago
|
||
Nominating to block, the visual active state (on) does not match the actual state of the alarm (off). Also note this isn't a repeating alarm.
blocking-b2g: --- → 2.0?
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Assignee | ||
Comment 3•10 years ago
|
||
Please do not nominate issues to block 2.0 unless they have been confirmed affected in the v2.0 branch. Testing locally, this does _not_ reproduce on v2.0, only on master. This bug appears to be a regression from bug 1001568. Investigating now.
Assignee: nobody → m
Status: NEW → ASSIGNED
blocking-b2g: 2.0? → ---
Assignee | ||
Updated•10 years ago
|
status-b2g-v2.0:
--- → unaffected
Comment 4•10 years ago
|
||
Understood, nominating to block 2.1, confirmed doesn't reproduce on 2.0. Regression, requesting a window. Environmental Variables: Device: Flame 2.0 Build ID: 20140701000201 Gaia: 8fb5e2a9ad1025ee7d247b90af7499766afadd28 Gecko: 5da69a493324 Version: 32.0a2 (2.0) Firmware Version: v122
blocking-b2g: --- → 2.1?
Assignee | ||
Comment 5•10 years ago
|
||
Attachment #8449018 -
Flags: review?(mmedeiros)
Updated•10 years ago
|
QA Contact: ddixon
Updated•10 years ago
|
Keywords: regressionwindow-wanted
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage+][lead-review+]
Comment 6•10 years ago
|
||
Comment on attachment 8449018 [details] [review] Link to Github pull-request: https://github.com/mozilla-b2g/gaia/pull/21245 LGTM!
Attachment #8449018 -
Flags: review?(mmedeiros) → review+
Assignee | ||
Comment 7•10 years ago
|
||
master: https://github.com/mozilla-b2g/gaia/commit/52d8e1354ae5456a9c0cb30f9c365b74385e69fd Clearing nom, as 2.1 === master.
Status: ASSIGNED → RESOLVED
blocking-b2g: 2.1? → ---
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•