Where does the bug appear (feature/product)?
Grok Bot
Describe the Bug
On Grok Bot mobile Settings, a touch that starts on a toggle/control and then becomes a scroll/swipe still activates that control. The user meant only to scroll; settings flip by accident.
Wrong pattern: finger-down on a toggle (or similar control) + move to scroll → control still commits (toggle flips).
Right pattern:
- Tap = touch down + up with little/no movement → OK to change the control
- Scroll = touch down + move past swipe threshold → scroll only; do not activate the control under the finger
Safety / security impact: This is not only annoying. Dense Settings lists include protective toggles (e.g. Agent guards). Scrolling the page can accidentally turn Agent guards (or similar protections) off when the user never intended a settings change.
Steps to Reproduce
- Open Grok Bot on mobile → Settings.
- Place thumb/finger on a toggle (e.g. Agent guards or any switch) and immediately swipe to scroll without a deliberate tap.
- Observe: the toggle/control activates or flips while scrolling.
- Contrast: tap the same control and lift without scrolling → intentional change (OK).
Expected Behavior
Scroll gestures that begin on a control must not activate that control. Only a clean tap (press + release without swipe past scroll threshold) should toggle/change settings — especially for safety-related toggles like Agent guards.
Operating System
Other
Version Information
Grok Bot 1.10.0 (9930) · runtime 48efc505bd159c0f20dd2b252542a8e63a682beb · embedded bundle · channel production
Additional Information
- Desktop not claimed for this report (mobile Settings scroll/touch).
- Dual-path: in-app SendFeedback also submitted
- Does not block Settings entirely; easy to flip settings (including protections) unintentionally while scrolling
- Conversation ID: Gap (Settings UI chrome — not chat-specific)
- Emailed [email protected]
- Related FR: Grok Bot: let dismiss of weekly usage-limit banner stick (X keeps coming back) (different ask)
Does this stop you from using Cursor
No - Cursor works, but with this issue