HUD activation not completely consistent with Launcher/Toolbar/App lens activation

Bug #1181301 reported by Tim Peeters
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu UX
Fix Committed
High
Oren Horev

Bug Description

To activate the HUD from an app, you have to swipe up from the bottom of the screen until the HUD button appears, and then continue your swipe until the finger is on top of the button to activate it, and then release.

For a toolbar, or for hiding the hud, the behavior is slightly different and those are shown/hidden depending on the position where you release your finger or the speed and direction of the swipe when releasing. Something similar happens for the Launcher, if you swipe further to the right when the launcher is fully visibile, you go to the apps lens.

Can this behavior be tuned so that you don't have to exactly position your finger on the HUD button when releasing? Now you have to "hover" over the button to make it "active". For example, the HUD button can be active if you hover over it, or if your finger is in the part of the screen above the HUD button. Like that you can quickly open the hud by doing a fast long swipe upwards without paying attention to where the button appears.

Summary: I want to do a fast long swipe up from the bottom-edge to activate the HUD. If I want to activate the HUD really fast like that now, it is very likely that I 'miss' the HUD button and don't activate the HUD

update
---------
This is being addressed through a new persistent behaviour of the HUD icon

Tim Peeters (tpeeters)
description: updated
John Lea (johnlea)
Changed in ubuntu-ux:
assignee: nobody → Oren Horev (oreneeshy)
Oren Horev (oreneeshy)
description: updated
Changed in ubuntu-ux:
status: New → Fix Committed
importance: Undecided → Medium
importance: Medium → Low
importance: Low → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.