touch-packages team mailing list archive

[Olivier Tilloy <olivier.tilloy@xxxxxxxxxxxxx>]

Public bug reported:

Filing this bug for webbrowser-app, but it’s likely that it’s affecting
other applications.

I’m not aware of design guidelines regarding the use of haptics feedback
when pressing/tapping UI elements on a touch device. In the UITK, it
seems that anything that is a button (including anything inheriting from
AbstractButton) will by default trigger a haptic response. List items
are not button, so tapping them doesn’t trigger haptic feedback. However
it’s pretty easy to build custom list items that embed an
AbstractButton, and thus introduce inconsistency.

An example of this inconsistent behaviour is the Settings screen in the
browser app: the first two items ("search engines" and "homepage") are
custom, they are haptics-enabled. The remaining items are not.

We need clear design guidelines. Once we have them, we need to go
through every UI element of the apps and fix them if they don’t comply
with the guidelines.

** Affects: ubuntu-ux
     Importance: Undecided
         Status: New

** Affects: webbrowser-app (Ubuntu)
     Importance: Medium
         Status: Triaged

** Changed in: webbrowser-app (Ubuntu)
       Status: New => Triaged

** Changed in: webbrowser-app (Ubuntu)
   Importance: Undecided => Medium

** Also affects: ubuntu-ux
   Importance: Undecided
       Status: New

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

Title:
  Inconsistent use of haptic feedback across the UI

Status in Ubuntu UX:
  New
Status in webbrowser-app package in Ubuntu:
  Triaged

Bug description:
  Filing this bug for webbrowser-app, but it’s likely that it’s
  affecting other applications.

  I’m not aware of design guidelines regarding the use of haptics
  feedback when pressing/tapping UI elements on a touch device. In the
  UITK, it seems that anything that is a button (including anything
  inheriting from AbstractButton) will by default trigger a haptic
  response. List items are not button, so tapping them doesn’t trigger
  haptic feedback. However it’s pretty easy to build custom list items
  that embed an AbstractButton, and thus introduce inconsistency.

  An example of this inconsistent behaviour is the Settings screen in
  the browser app: the first two items ("search engines" and "homepage")
  are custom, they are haptics-enabled. The remaining items are not.

  We need clear design guidelines. Once we have them, we need to go
  through every UI element of the apps and fix them if they don’t comply
  with the guidelines.

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