Closed Bug 981806 Opened 11 years ago Closed 11 years ago

[B2G][Clock]Timer option to add +1 Min intermittently becomes highlighted in dotted box with gray color scheme locked in place when selected more than once

Categories

(Firefox OS Graveyard :: Gaia::Clock, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(b2g-v1.3 unaffected, b2g-v1.4 affected)

RESOLVED DUPLICATE of bug 976197
Tracking Status
b2g-v1.3 --- unaffected
b2g-v1.4 --- affected

People

(Reporter: mclemmons, Unassigned)

References

()

Details

(Whiteboard: burirun1.4-1 [good first bug])

Attachments

(1 file)

When user accesses Clock App, taps Timer and selects either hours and/or minutes to begin the countdown, the +1 Min option appears. When user taps +1 Min, the display shows a dotted rectangular box around the text +1 Min. Though, user continued interaction with the +1 Min link intermittently causes the interior of the dotted rectangular box to become grayish in color and seemingly locked in place. This gives an unclear demonstration and does not change unless user taps the +1 Min link again. Throughout this experience, the minute section of the timer is adjusted properly over 90 percent of the time. On rare occasion, tapping +1 Min will not add time to the timer. Repro Steps: 1) Updated Buri to BuildID: 20140307040203 2) Tap Clock App 3) Tap Timer in lower central section of device screen 4) Select Hours and/or Minutes picker to desired start countdown for timer (i.e. 0 hours, 08 minutes) and tap Start 5) Tap +1 Min more than once up to ten times Actual: +1 Min display shows a dotted rectangular box around the text. Though, user continued interaction with the +1 Min link intermittently causes the interior of the dotted rectangular box to become grayish in color and appear locked in place Expected: +1 Min display shows a dotted rectangular box around the text yet continued interaction with the +1 Min link doesn't cause grayish colored interior within box to appear locked in place. Environmental Variables: Device: Buri 1.4 MOZ BuildID: 20140307040203 Gaia: 04eb7996543f114133d1367f834a4d88b68c60ac Gecko: b0e7f63c2138 Version: 30.0a1 Firmware: v1.2-device.cfg Notes: Repro frequency: (12/20, 60%) See attached: video clip - http://youtu.be/LNK8qfr6yq0, logcat (attached) ***Note: There was no current test case found that addresses this specific area of device. The closest area is https://moztrap.mozilla.org/manage/case/11314/
Unable to attach logcat referenced in Comment 0 due to Bugzilla technical issue.
This issue does not occur on Buri 1.3 There is no +1 Min feature on this build. Environmental Variables: Device: Buri 1.3 MOZ BuildID: 20140307004004 Gaia: e8bf7326ce5ed63bc8ef8b2cff1eba094887b9bf Gecko: 4efa30fe00e7 Version: 28.0 Base image: v1.2-device.cfg
Not a blocking regression, although it is a bit annoying to have the +1 min button have a small probability of failure.
Keywords: regression
(In reply to Jason Smith [:jsmith] from comment #4) > Not a blocking regression, although it is a bit annoying to have the +1 min > button have a small probability of failure. Actually not a regression, as this wasn't supported in 1.3.
Keywords: regression
Whiteboard: burirun1.4-1 → burirun1.4-1 [good first bug]
As the underlying cause is identical to that of bug 976197, marking as duplicate. Also renaming the title of that bug to more clearly express that the target bug is Clock-wide, not just Stopwatch.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: