Ubuntu
ubuntu-ui-toolkit package

New bottom edge component is harder to flick up

Bug #1552928 reported by Michael Zanetti
42
This bug affects 8 people
Affects Status Importance Assigned to Milestone
Canonical System Image
Confirmed
High
Zoltan Balogh
Canonical System Image backlog
ubuntu-ui-toolkit (Ubuntu)
Confirmed
High
Zsombor Egri

Bug Description

I usually hold the phone in one hand and open the bottom edge by flicking up from the bottom with the thumb. This worked fine with the previous bottom edge, however, with the new one, there seems to be larger amount of dragging required. I keep on failing to open the bottom edge in the messages-app and clock app, now that they use the new component.

When dragging very slowly such an big required distance does make sense, but for quick flicks with the thumb, it should also take the speed and/or touch points history into account and reduce the required distance if it detects a fast flick gesture.

In the right edge implementation for instance, it tracks the touch points and already activates the gesture after a rather short distance (2 grid units), provided it is a one-way gesture with increasing distance from the edge in each recognized point. Such a logic would imo also make sense for the bottom edge.

Revision history for this message
Zsombor Egri (zsombi) wrote :

Do you do the same like here? http://bazaar.launchpad.net/~ubuntu-clock-dev/ubuntu-clock-app/trunk/view/head:/app/components/AlarmBottomEdge.qml#L39
No wonder then...

Revision history for this message
Michael Zanetti (mzanetti) wrote :

I haven't looked at the BottomEdge from a developer point of view yet (will do soon). This report is really from a user point of view. While such a flick from the bottom edge has always been revealing the bottom edge for me with the old implementations, the new implementation always requires me to try at least 3 times until I manage to pull it up.

Now I have no clue if this is an issue in the component or the apps using the component. However, so far I have seen two apps using the new component (messages and clock) and both show this same issue, which led me to report the bug on the component. If it is indeed an issue of how the apps are using the component, we should mark all those apps as affects too in this report. However, as so far 100% of the apps would be using it wrongly, I can't help but think the API would suggest to be used wrongly and maybe could/should be improved still.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu-ui-toolkit (Ubuntu):
status: New → Confirmed
Revision history for this message
Bob Harvey (bobharvey) wrote :

My secondary remarks in bug #1586680 are /exactly/ about this.

Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

I agree with the report as described and by default the edge should be easier to enable.
@zsombi I didn't understand your comment on the clock implementation

Changed in canonical-devices-system-image:
assignee: nobody → Zoltan Balogh (bzoltan)
importance: Undecided → High
milestone: none → 13
status: New → Confirmed
Changed in ubuntu-ui-toolkit (Ubuntu):
assignee: nobody → Zsombor Egri (zsombi)
Revision history for this message
Bob Harvey (bobharvey) wrote :

Can't believe you have pushed this out to OTA 13. People paid real money for the devices, it is a bit ripe shipping them unfinished and then delaying important fixes.

Revision history for this message
Michael Zanetti (mzanetti) wrote :

@Bob, I agree this bug is important to fix in order to provide a very smooth user experience. However, it's not like the bottom edge would not work at all currently. I for one am happy to see the other fixes accumulated for OTA 12 being released to the users and not being delayed even more because of an issue like this.

Andrea Bernabei (faenil)
Changed in ubuntu-ui-toolkit (Ubuntu):
importance: Undecided → High
Revision history for this message
Zsombor Egri (zsombi) wrote :

The BottomEdge design guides state that if a gesture ends less than 1/3rd of the screen, it should collapse back. There was no mentioning on quick flicks, and we discussed this with them back then, and we agreed that we will implemented the swipe gesture for now. I think we need to revisit this with design.

Pat McGowan (pat-mcgowan)
Changed in canonical-devices-system-image:
milestone: 13 → backlog
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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