[Feature]: Allow user to not click deck after down-click (Firefox)

[meichthys]

Feature Summary

Allow user to not click deck after down-click

Detailed Description

Currently on desktop, if you down click the deck to draw a card, you cannot move the cursor away from the deck to stop drawing the card.

This does not seem to be an issue when playing on mobile or on Safari, but was observed on Firefox for desktop Screencast from 2024-01-13 22-46-30.webm

I'm not sure if this applies to any other browsers since most users said it was working fine for them.

[seriouslysean]

This is a pretty weird issue. I did a little digging after talking to @itsalaidbacklife and I don't know the actual solve, but I can say what I think it might be.

https://codepen.io/seriouslysean/pen/VwRbBJK

I set up listeners for click, mouseup and mousedown, and when you click it will increment the amount + 1 for the element and the document count if they trigger. The interesting thing is that this is the default JS behavior using bubble (not capture). This also aligns with the behavior where we don't fire any action if you mouse off the element in both cases whether it's an element listener, or a document listener for a specific element.

This means it's probably a v-card specific implementation and I would like to see some sort of reproduction there. I'm guessing that component is tracking a ref on mouse down, then firing against that ref on mouseup, but more work needs to be done to untangle it.

Edit: I also added a cached ref version that has the same functionality we're seeing in the vcard.

[seriouslysean]

This is an issue within Vuetify, so I filed a bug report with them to address it, https://github.com/vuetifyjs/vuetify/issues/19078.

@itsalaidbacklife my suggestion is to either do away with the VCard implementation and use a div or similar, or wait for a bug fix and let everyone know about the functionality in the meantime.

[meichthys]

Thanks for looking into it and filling the issue!

[itsalaidbacklife]

After further analysis, the issue is with firefox itself. It's not clear that we can fix this at this point, unfortunately. Hopefully firefox fixes their implementation of overflow: hidden

[itsalaidbacklife]

We can't really fix this because it's an issue with firefox itself