834607 - [clock] clock does not respond to multiple alarms set at the same time

Status: RESOLVED INVALID

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

Description

[Leo]

1. Title :clock does not respond to multiple alarms set at the same time.
2. Precondition : set multiple alarm at same time with different label and snooze time.
3. Tester's Action : Alarm ringing >> user snoozes alarm.
4. Detailed Symptom (ENG.) : when user snoozes the alarm, except one alarm all others will be turned off.
5. Gaia Source Version : b506bdbd5bcdb042e3a8ca5d62856ae5d683c176
6. Expected : Since each alarms have different label and snooze value, these alarms should be considered as independant alarm and handled independantly. Android can used for reference.
7.Reproducibility: Y
1)Frequency Rate : 100%
8.Comparison Results : 
1)Model Comparing : 
9. Attached files: 
1)Log : 
2)Test Contents : 
3)Video file :

Comment 1

[Gene Lian (I already quit Mozilla)]

I think the platform has already covered this case. That is, the Alarm API will fire 2 separate system messages to the Gaia, when multiple alarms are programmed at the same time.

Comment 2

[Gene Lian (I already quit Mozilla)]

(In reply to Gene Lian [:gene] from comment #1)
> I think the platform has already covered this case. That is, the Alarm API
> will fire 2 separate system messages to the Gaia, when multiple alarms are
            ^ multiple
> programmed at the same time.

Comment 3

[[e-mail], [e-mail]]

Gaia system will show attention screen by app do window.open() with attention property. The attention screen is designed for some urgent event which is needed to block user immediately. For the current architecture of attention screen module, it supports only one screen for each apps. If we want to have a multiple attention screen for each alarms, we will need to have some discussion to find out a suitable architecture in Gaia system app. 

For the current behavior, it will turn off the previous alarms since we can show the active alarm only. The behavior is fixed by (Bug 804394 - [Clock] if more than one alarm is set and goes off and the screen lock is placed, only the top alarm is disabled.).

Alive,
Would you have some suggestion, if we want support multiple active alarms?

Comment 4

[Gene Lian (I already quit Mozilla)]

Just a quick suggestion. I don't think it's necessary to show separate attention screens for multiple alarms (fired at the same time) if the screens actually reveal the same information. Popping up one screen for one alarm is more like an engineer's intuition.

Comment 5

[(inactive after 6/18) Alive Kuo [:alive]]

"In case" we need this:
https://groups.google.com/forum/?fromgroups=#!topic/mozilla.dev.gaia/dQJOQE-Y8l4
See app-specific (5), make attention screen app-specific could also gain the benefit that we could have multiple attention screen for one app easily.

Current implementation of attention screen is impossible to do this because every thing is bind to app origin.

Comment 6

[[e-mail], [e-mail]]

Just add more information what I see in iOS. If we set multiple alarms with the same fire time, it will show multiple dialogs(the newer one is hover the previous alarms). Then, user will need to close them one by one.

I think that both the two behaviors has it's strength and weaknesses. We could hear some voice from UX.

Josh,
Could you please give some suggestion for the issue?

Comment 7

[Josh Carpenter [:jcarpenter]]

Hi guys, good catch. What timeline are you looking at this bug for? I do not see any release-specific flags on it. For 1.0 and 1.0.1 I would not worry about fixing this, since it's unquestionably an edge case, and the current "failure" still activates an alarm (fulfilling the user's actual need). 

Long term we can adopt a solution along the lines of iOS, but I'm not concerned about fixing this in the near future.

Comment 8

[Leo]

Not supported for v1.1