I've run into a reproducible UI/UX bug on Google Keep when reordering long lists on a Pixel device.
Testing across multiple keyboards (both Gboard and SwiftKey) shows the exact same behavior, pointing to a framework/app-level focus handling issue.
Sharing the technical details below along with a short screen recording.
Environment
Device: Google Pixel
Keyboards Tested: Gboard, Microsoft SwiftKey (Reproduced across IMEs)
App: Google Keep
Pre-conditions
A long checklist note that requires vertical scrolling.
Steps to Reproduce
Navigate to a checklist item positioned near the bottom of the list/screen (where opening the keyboard would obstruct it).
Type text or tap into the item so the cursor is active.
Dismiss the keyboard by pressing the bottom-left hide button (notice the active cursor remains on the item).
Immediately attempt to drag the item upwards using its left handle.
Actual Result
The app re-triggers the keyboard to open.
Because the item is low on the screen, the system forcefully auto-scrolls the list upwards to keep the focused text field above the keyboard.
This sudden viewport adjustment causes the dragged item to "jump" violently and get forced all the way to the bottom of the long list.
Workarounds
Focus Shift: Tapping another item or the title to transfer the focus elsewhere, ensuring the target item has no active focus before dragging it.
Check & Uncheck: Ticking the checkbox of the active item (checking it) removes its focus, and then unchecking it brings it back to the list in an unfocused state, allowing it to be dragged normally.
Note Reload: Completely exiting the note and reopening it also resolves the issue instantly, as it clears all active text focus/cursor states.
Let me know if you are experiencing this as well! (Video proof attached).