Bugzilla – Bug 8860
Only the first sleep hit should require holding down
Last modified: 2009-09-08 09:30:32 UTC
Split from bug 7781. ------- Comment #24 From Matt Wise 2008-06-11 09:38:19 [reply] ------- I think our Snooze button still acts funny... I like that it takes 1-2 seconds of holding the bar down to get it to respond the first time, but once its up you should be able to quickly tap to skip from 15Min to 30 to 45 to 60 to 90 to Off without having to hold it down two seconds each time. Anyone else disagree?
Just to be clear, the bar is both sleep and snooze. The Snooze functionality (i.e. when the alarm is going off) should _not_ require a press and hold. Matt's suggestion for the sleep functionality is a good one.
One touch snooze has been broken at least since Monday. Mike
It should have been fixed in yesterday's checkins. It was working for me this morning. Both boom branch and new streaming.
If it is still broken, please file a separate bug. This isn't the place.
I'll test tonight, my alarm didn't go off at all this morning. Was likely due to other issues. Mike
Not fixed. I think this may have been closed by accident. The issue reported in the description is still current. My comments about things being fixed referred to the side issues that Mike raised.
Andy to have a look.
*** Bug 8904 has been marked as a duplicate of this bug. ***
In bug 8904 Caleb suggests continuing to hold the snooze bar down to cycle through times.
I prefer tapping, so that's what I'll look at implementing.
Anyone: Is there a reason the sleep button on the remote shouldn't always do the same thing as the snooze bar? For example, while on, pressing the remote sleep button sets the sleep time. The snooze bar shows the current time.
Fixed in change 22384.
Let's not change the behavior of the button on the remote. The reason we did this on the bar is because it's too easy to hit accidentally.