[TOPBLOCKER] [notification] incoming call snap decision should prevent edge interaction on greeter

[Bill Filler]

rtm build 88 on krillin

Steps to reproduce:
- unlock the phone
- call the phone
- when the incoming call snap decision is displayed, all access to the edges is blocked and the dialog is modal, as it should be
- now lock the phone
- call the phone

Expected results:
- all access to the edges is blocked and the snap-decision is modal, as is the case when the phone is unlocked

Actual results:
- the launcher can be swiped and the top panel can be interacted with. the edges are not blocked as they should be

This is related to #1358343 [notifications] [design] too easy to answer a call by accident. We need this to be fixed so users don't inadavertently interact with the indicators or launcher when the phone is there pocket and an incoming call arrives. This fix, coupled with the fix to the snap decision to have a swipe to answer would prevent most of the problems that can occur.

[Bill Filler (bfiller)]

Marking this critical as it's quite easy to mistakenly interact with edge components when trying to get phone out of your pocket when it's ringing

[Bill Filler (bfiller)]

This is what was discussed in the design meeting today. The incoming call notification (and other notificaitons) that occur on the lock screen should be modal.

[Mirco Müller (macslow)]

This is actually related to the frontend of the notifications. Thus needs to be filed against unity8. The backend (unity-notifications) only deals with queue-logic.

[Olga Kemmet (olga-kemmet)]

The notification should be modal on lock screen AND greeter.

[Mirco Müller (macslow)]

Is this bug really meant for RTM? It was initially marked as "Critical" - and I've taken over this for the change in affected package - and would thus also imply it being targetted for RTM. Can some of the stakeholders please comment.

[Michał Sawicz (saviq)]

> Is this bug really meant for RTM? It was initially marked as "Critical"
> - and I've taken over this for the change in affected package - and
> would thus also imply it being targetted for RTM. Can some of the
> stakeholders please comment.

It's still Critical, has the rtm14 tag and even a target date -
touch-2014-10-30, so yeah, it's meant for RTM.

[Launchpad Janitor (janitor)]

This bug was fixed in the package unity8 - 8.01+15.04.20141030~rtm-0ubuntu1

---------------
unity8 (8.01+15.04.20141030~rtm-0ubuntu1) 14.09; urgency=medium

  [ Michael Terry ]
  * Provide 'passphrase' as a field of Components.Lockscreen
  * Fix a race between Qml loading and DBus registration that caused
    problems when jenkins tried to unlock the phone.
  * Set domain explicitly for the Dialogs component because the welcome
    wizard wants to import it. (LP: #1381731)
  * When greeter or lockscreen has focus, show active call panel. (LP:
    #1378872)

  [ Ted Gould ]
  * Set the default OOM score for the dash (LP: #1379786)

  [ Michał Sawicz ]
  * Revert lp:~unity-team/unity8/flickables-speed-workaround to avoid
    risk in RTM.
  * Updated behaviour for zoomable image, workaround for sourcesize (LP:
    #1333187)

  [ Michael Frey ]
  * Added a check for Proximity to determine if we show the lock screen.
    (LP: #1378012)

  [ Ying-Chun Liu ]
  * Add non-interactive code into GenericScopeView. (LP: #1384441)

  [ Mirco Müller ]
  * Also use modal nature of snap-decision notifications when
    greeter/lockscreen is shown. This fixes LP: #1378827. (LP: #1378827)

  [ Michael Zanetti ]
  * Make the launcher update on dconf changes (LP: #1376707)
  * exit spread on background tap (LP: #1368261)
  * Use an index instead of a scope id in DashCommunicator (LP:
    #1376044)

  [ Andrea Cimitan ]
  * Updated behaviour for zoomable image, workaround for sourcesize (LP:
    #1333187)

  [ Daniel d'Andrada ]
  * Make TouchGate synthesize QMouseEvents for mouse-based target items
  * Don't specify a distanceThreshold as it conflicts with
    hintDisplacment
 -- Ubuntu daily release <email address hidden> Thu, 30 Oct 2014 21:43:42 +0000

[Launchpad Janitor (janitor)]

This bug was fixed in the package unity8 - 8.01+15.04.20141030-0ubuntu1

---------------
unity8 (8.01+15.04.20141030-0ubuntu1) vivid; urgency=medium

  [ Michael Terry ]
  * Provide 'passphrase' as a field of Components.Lockscreen
  * Fix a race between Qml loading and DBus registration that caused
    problems when jenkins tried to unlock the phone.
  * Set domain explicitly for the Dialogs component because the welcome
    wizard wants to import it. (LP: #1381731)
  * When greeter or lockscreen has focus, show active call panel. (LP:
    #1378872)

  [ Ted Gould ]
  * Set the default OOM score for the dash (LP: #1379786)

  [ Michał Sawicz ]
  * Revert lp:~unity-team/unity8/flickables-speed-workaround to avoid
    risk in RTM.
  * Updated behaviour for zoomable image, workaround for sourcesize (LP:
    #1333187)

  [ Michael Frey ]
  * Added a check for Proximity to determine if we show the lock screen.
    (LP: #1378012)

  [ Ying-Chun Liu ]
  * Add non-interactive code into GenericScopeView. (LP: #1384441)

  [ Mirco Müller ]
  * Also use modal nature of snap-decision notifications when
    greeter/lockscreen is shown. This fixes LP: #1378827. (LP: #1378827)

  [ Michael Zanetti ]
  * Make the launcher update on dconf changes (LP: #1376707)
  * exit spread on background tap (LP: #1368261)
  * Use an index instead of a scope id in DashCommunicator (LP:
    #1376044)

  [ Andrea Cimitan ]
  * Updated behaviour for zoomable image, workaround for sourcesize (LP:
    #1333187)

  [ Daniel d'Andrada ]
  * Make TouchGate synthesize QMouseEvents for mouse-based target items
  * Don't specify a distanceThreshold as it conflicts with
    hintDisplacment
 -- Ubuntu daily release <email address hidden> Thu, 30 Oct 2014 21:43:42 +0000