Closed Bug 898367 Opened 8 years ago Closed 8 years ago

[User Story] Start/Stop Stop Watch

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: pdol, Assigned: evhan55)

References

Details

(Keywords: feature, Whiteboard: [ucid:Productivity32])

User Story:

As a user I want to be able to start a stop watch and stop it at any point so that I can time an event.


Acceptance Criteria:

1. I can start the stop watch causing the elapsed time to visibly increment until it is stopped.
2. I can stop the stop watch after it has been started causing the elapsed time to stop incrementing until it is reset or restarted.
Accidental nom.  Not a blocking feature.
blocking-b2g: koi? → ---
Blocks: 898456
Assignee: nobody → achyland
I have not seen the wireframes for the stopwatch, and perhaps they answer my question, but I think we should get some clarity on the localization needs for a stopwatch.

Do digital stopwatches use the normal time display format of the locale, or are colons a universal hh:mm:ss separator for this application?

Setting needinfo on Axel.

Axel: the same question applies to the countdown timer feature, which is in bug 898353 et. al. Are countdown timers localized like times, or are they non-localized?
Flags: needinfo?(l10n)
CCing community@localization.bugs to have some feedback directly from localizers.

Even if it's overdoing, I would probably leave the separator localizable inside the app.
Flags: needinfo?(l10n)
Assignee: achyland → evelyn
Depends on: 909386
Depends on: 909394
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.