touch-packages team mailing list archive

[Vesa Rautiainen <1440360@xxxxxxxxxxxxxxxxxx>]

The reporter is correct with this one. The long left edge swipe action
(currently focusing to the left most scope if I remember correctly)
should not be triggered until user actually performs the long left edge
swipe and releases it towards right. In the current implementation this
is the case when an application is focused but when a child scope is
focused action is triggered as soon as user swipe passes the launcher
edge i.e. when the long swipe gesture starts. And that's why it can be
accidentally triggered when intention was just to open the launcher.


** Changed in: ubuntu-ux
     Assignee: Paty Davila (dizzypaty) => Vesa Rautiainen (vesar)

** Description changed:

  Steps to reproduce the issue:
  1 - open e.g. Ubuntu Store scope (from the app scope) or Youtube scope (from the video scope)
  2 - (shortly) swipe from the left to invoke launcher
  
  Expected outcome:
  The launcher can be used to open a pinned app (while the current scope is still kept in the background) or dismissed to return to the current scope.
  
  Actual outcome:
  The current scope will immediately be closed and the first (main) scope (typically the app scope on devel-images and the Today scope on RTM) will be shown.
  If I understand the current design guidelines correctly this is the expected behaviour for a full left-to-right swipe, but not for a short swipe from the left to invoke the launcher.
  
  This behaviour can be observed on both the current devel-proposed and
  RTM images.
+ 
+ -----------------------------
+ Desired UX
+ 
+ - Don't trigger the "go to home" action yet when the long swipe is
+ started but when user releases the finger and all the long swipe
+ parameters are fulfilled (distance threshold and direction)
+ 
+ - Also trigger "go to home" action when any other scope is focused.
+ Currently action is triggered only when app is focused and when a child
+ scope is focused but not when one of the dash scopes is focused.

** Changed in: ubuntu-ux
       Status: Triaged => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1440360

Title:
  Incomplete long-left swipe resets dash

Status in Ubuntu UX:
  Fix Committed
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce the issue:
  1 - open e.g. Ubuntu Store scope (from the app scope) or Youtube scope (from the video scope)
  2 - (shortly) swipe from the left to invoke launcher

  Expected outcome:
  The launcher can be used to open a pinned app (while the current scope is still kept in the background) or dismissed to return to the current scope.

  Actual outcome:
  The current scope will immediately be closed and the first (main) scope (typically the app scope on devel-images and the Today scope on RTM) will be shown.
  If I understand the current design guidelines correctly this is the expected behaviour for a full left-to-right swipe, but not for a short swipe from the left to invoke the launcher.

  This behaviour can be observed on both the current devel-proposed and
  RTM images.

  -----------------------------
  Desired UX

  - Don't trigger the "go to home" action yet when the long swipe is
  started but when user releases the finger and all the long swipe
  parameters are fulfilled (distance threshold and direction)

  - Also trigger "go to home" action when any other scope is focused.
  Currently action is triggered only when app is focused and when a
  child scope is focused but not when one of the dash scopes is focused.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1440360/+subscriptions