bugs

With the new changes of the showroom, now in my phone I can't click in the equipments of the stash when I zoom in, making it impossible to change equipments. I just can re-order them. Is anyone having the same issue?

Tried on two different phones, I was able to swap equipment after zooming in on both of them

Haven't played on phone for at least a decade so I wouldn't know, but in browser I have to click the item several times every now and then to get the click to register.

It is definitely pretty strict with it's distinction between a click and a drag, maybe that can be smoothed out a little

I'm able to reproduce this as well. I tried a couple quick fixes and haven't gotten it to work yet, will keep poking at it.

Could you just disable the drag when hovered on an item link?

I think I have a fix for this (while still allowing the whole row to be draggable!), but I want a little more time to test it before pushing it live. I'll try to play around with it more after work today.

This should be fixed now. Please let me know if anyone is still having issues on mobile (or otherwise with the stash).

Details: I ended up upgrading from some pretty old stuff (jQuery UI + Touch Punch) to a much newer library (SortableJS). The old approach was doing some (probably) funky stuff on mobile to translate "touch" events into mouse actions, whereas the new approach processes touch events directly. I also added a delay for touch events only - this means that on mobile, you can't drag the row unless you hold on it for at least 150ms. This is a very short time, but long enough that just regular tapping on an item name will open its details as expected (rather than incorrectly triggering the drag). Desktop behaves the same as before - you can drag immediately without delay. Another side benefit of switching to this more modern library is that there's now a nice little animation of rows moving around as you drag, which I find makes it a little more clear what's happening.

Given that I replaced the original implementation with a totally new JS library to solve this bug, there's the potential for having introduced some other odd behavior, so please be on the lookout for anything unusual.

And thanks for the helpful bug report!

Thanks for solving this!