Comment 11 for bug 1291455
Revision history for this message
| Bill Filler (bfiller) wrote Re: Screen and input should be disabled with proximity sensor when on greeter | #11 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
This is actually working per the design we agreed on some months back (I can't seem to find the bug that has the discussion thread).
Here are the points, I believe:
1) You do want the screen to light up even when the proximity sensor is covered on an incoming call. If the phone is in your purse or bag and it's ringing you need to be able to see it. This is how iOS works, probably Android as well.
2) The incoming call notification is modal. You can only interact with it and there is no other input available that you can accidentally interact with (i.e. indicators, launcher)
3) You have to swipe to answer/decline a call which is difficult to do accidentally
4) The quick reply could be an issue, but even that requires 2 taps. One tap to show the menu then another to select the option.
If there is an issue with 4 happening automatically we should revist the design of the notification.
I think the bottom line is that every notification that occurs when the phone is locked needs:
a) to always be modal so no other actions can be taken on the ui (think this is true already)
b) needs to use swipe to perform an action, not tap