Skip to content

Use sort handle for signups on trip admin tab to make it scrollable on mobile#115

Open
collinmay wants to merge 1 commit intoDavidCain:masterfrom
collinmay:trip-admin-signup-drag-handles
Open

Use sort handle for signups on trip admin tab to make it scrollable on mobile#115
collinmay wants to merge 1 commit intoDavidCain:masterfrom
collinmay:trip-admin-signup-drag-handles

Conversation

@collinmay
Copy link
Copy Markdown

Re-addresses #105.

On mobile, the active area for starting drag-and-drop for signups on the admin spans almost the entire width of the screen, making it very difficult to scroll. By reducing the active area for starting a drag-and-drop operation to a smaller icon, it makes it much easier to scroll the page on mobile, while reducing the chance of accidentally reordering signups.

Here's a recording of what it looks like to use the page in firefox dev tools simulating a mobile device. The cursor icon bugginess is an artifact of simulating touch inputs with a mouse.

Recording 2026-01-24 at 17 40 37

On my actual phone, the scrolling experience is much more comfortable and the active area for beginning a drag is big enough to hit when I do mean to hit it.

On desktop, the cursor only switches to the grab icon when you are hovering over the drag handle.

image

I've left the other usage of ui-sortable in the lottery ranking selection alone. There are some minor CSS changes, but the cursor still behaves properly there.

image

On mobile, the active area for starting drag-and-drop for signups on the admin
spans almost the entire width of the screen, making it very difficult to
scroll. By reducing the active area for starting a drag-and-drop operation to a
smaller icon, it makes it much easier to scroll the page on mobile, while
reducing the chance of accidentally reordering signups.
@collinmay collinmay force-pushed the trip-admin-signup-drag-handles branch from 7fad384 to 1285988 Compare January 24, 2026 23:01
@DavidCain
Copy link
Copy Markdown
Owner

I like this idea. Let me try it out and I'll likely merge it. Thanks for the work here. I was really hoping I'd have completely replaced this flow by now, but alas.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants