Closed
Bug 2088788
Opened 11 days ago
Closed 10 days ago
Add haptic feedback to onboarding buttons, links, toggles and page swipes
Categories
(Firefox for Android :: Onboarding, enhancement)
Tracking
()
RESOLVED
FIXED
161 Branch
| Tracking | Status | |
|---|---|---|
| firefox161 | --- | fixed |
People
(Reporter: towhite, Assigned: towhite)
References
Details
(Whiteboard: [android-activation-trust] [fxdroid])
Attachments
(1 external file)
Add haptic feedback to the onboarding flow so interactions feel more responsive:
- Buttons and links on every onboarding card, including the Terms of Use links and the manage privacy preferences dialog, play a confirmation haptic (
HapticFeedbackType.Confirm). - The switches in the manage privacy preferences dialog play
ToggleOn/ToggleOffto match the new state. - Swiping between onboarding cards plays a gesture-end haptic when the pager settles on the new page. Advancing with a button does not trigger it, to avoid a double buzz.
Everything is gated behind a new FeatureFlags.onboardingHapticsEnabled flag, enabled on Nightly and debug builds only, so it can be tried on-device before deciding whether to ship it.
Implementation notes: the wrapping helpers (hapticOnClick, hapticOnLinkClick, hapticOnCheckedChange) live in the onboarding package for now. They are the first tap haptics in the tree (existing usages are all long-press, or Confirm on pull-to-refresh), so if another surface wants them they should move to android-components compose/base alongside LongPressIconButton.
Updated•11 days ago
|
Comment 1•11 days ago
|
||
(via GitHub webhook, authenticated as shared-secret)
Pushed by icedicedcoffee@proton.me:
https://github.com/mozilla-firefox/firefox/commit/ea0a0b11be23
https://hg.mozilla.org/integration/autoland/rev/a8441150bee8
Add haptic feedback to onboarding buttons, links, toggl… r=lottie,corentin
Comment 3•10 days ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 10 days ago
status-firefox161:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 161 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•