fix(apk-ux): modernize SelectionFab haptic interaction model and touch inputs#1207
Conversation
…h inputs Modernizes the SelectionFab component's haptic interaction model by removing manual pointerdown haptic triggers and replacing them with the declarative v-tactile directive on all interactive buttons. Synchronizes the test suite.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
Generated by: .github/nightly-prompts/12-apk-ux.md
Reasoning:
[UX Issue]: Manual pointerdown event listeners and direct useHaptics haptic feedback triggers in SelectionFab were legacy interaction patterns.
[Impact]: Breaks visual parity and declarative brokered haptic touch interaction consistency with the rest of the PWA shell inside Android WebView.
Changes:
Frontend-PWA/src/shared/ui/SelectionFab.vuev-tactilehaptic brokering directive.pointerdownevent listeners and direct haptics triggers.Frontend-PWA/src/shared/ui/ui-tests/SelectionFab.spec.tsv-tactiledirective instead of direct manual haptic triggers.Verification:
Log Updates:
PR created automatically by Jules for task 15426047079553209136 started by @AlbiDR