Anton Backer

I can also reproduce the issue on [browserstack](https://browserstack.com). Can one of you try loading up Chrome 123 on browserstack and trying it there?

Take a snapshot of your entire universe down to the atoms—reproducibility is a precious gift!

I was running into a similar issue earlier today but eventually traced it to a bug of my own. Can you provide some sample code to demonstrate the bug you're...

Yes: ```jsx {(provided) => ( {items.map((item, index) => ( {(provided) => ( )} ))} {provided.placeholder} )} ``` `{provided.placeholder}` is where the magic happens.

Ah, yes, I don't think that's possible with this library. From what I've seen in the source, the way DND works is that it adds an invisible placeholder at the...

The issue is not 100% reproducible, but here are a few observations: - ~I have a sneaking suspicion and/or superstition that it helps to make and clear selection on a...

Ok, finally got a video: https://github.com/adobe/react-spectrum/assets/13100/1c0d276a-f88b-4d83-ba03-18288f1851d4 Here I reproduced the issue first, then started recording. In the recording, I'm using a trackpad with tap-to-click enabled, and each action is a...

I'm starting to believe that tap-to-click is **essential** to reproducing the issue, and selecting a second item via cmd+click is not essential.

@piecyk: multi-select via Cmd+tap and Cmd-click work for me in the above sandbox in chrome 124 and firefox 124 (macOS)

Related: I'm seeing this in the context of a Checkbox, where a press (combined with `continuePropagation`) sometimes makes it through to the parent component **when using tap-to-click** on a trackpad,...