It would be great to be able to swipe the toolbar tray off the screen once it's activated. This is a more natural way to dismiss the menu.

Screenshot of an iPhone simulator showing the toolbar side tray open. There is an arrow with the label swipe point to the left indicating that a user would be able to swipe in that direction to dismiss the open toolbar tray.

CommentFileSizeAuthor
swipe-toolbar-tray-off.png115.76 KBjessebeach
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Bojhan’s picture

Category: task » feature
Issue tags: +Usability, +mobile, +d8mux
LewisNyman’s picture

Are you thinking of implementing a third party library to help with this? I wrote the gestures from scratch in my prototypes because I wanted one to one movement but there are some nice libraries out there like hammer.js that dO a lot of heavy lifting.

jessebeach’s picture

nod_ suggested hammer.js as well. I think it's a great starting point.

LewisNyman’s picture

Issue tags: +toolbar-followup

taggin

nod_’s picture

We should 'hardcode' it, I don't want yet another lib at this point (unless we start putting gestures all over the place but it's way late for that…)

LewisNyman’s picture

Issue tags: +JavaScript

It seems strange to have one off gestures in a few UIs. This doesn't set up consistent expectations. Maybe we should push this to 9.x or a point release?

nod_’s picture

Version: 8.x-dev » 9.x-dev
Issue summary: View changes
LewisNyman’s picture

Version: 9.x-dev » 8.x-dev

Now that the menu button is the furthest away from a thumb it could be and it also stays open when you go to the next page, I think this is less of a nice to have and more essential. I can implement this without a library if it means we can get this in 8.x?

Wim Leers’s picture

I agree.

Bojhan’s picture

I agree, we shouldn't shy away from interactions that are perceived as "nice-to-have" - that is what differentiates between usable and delightful.

nod_’s picture

+1 to no library.

LewisNyman’s picture

Issue tags: +frontend
Wim Leers’s picture

Now that the menu button is the furthest away from a thumb it could be and it also stays open when you go to the next page, I think this is less of a nice to have and more essential. I can implement this without a library if it means we can get this in 8.x?

If this is the main reason, shouldn't we do #2103247: Clicking menu links in the administration menu tray should close the admin menu tray, while in a narrow viewport where the toolbar is positioned on top of the content instead?

Though I'd honestly prefer this over that.

LewisNyman’s picture

Version: 8.0.x-dev » 8.1.x-dev
Status: Active » Postponed

We haven't really progressed with touch specific UX stuff in D8 and it's a little hard to start adding gestures in now, we should probably used a library to keep implementation consistent. Let's focus on #2103247: Clicking menu links in the administration menu tray should close the admin menu tray, while in a narrow viewport where the toolbar is positioned on top of the content because that is so annoying.

Wim Leers’s picture

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.0-beta1 was released on March 2, 2016, which means new developments and disruptive changes should now be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

nod_’s picture

Status: Postponed » Active
Issue tags: -JavaScript +JavaScript

I guess, let's try it?

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.