Austin Keener

I can reproduce this. Thank you for the report.

A fix for this was just merged. It will be deployed in the next 24hrs

Is this still happening?

I can repro this. It is possible currently to create an onboarding prompt and provide `emoji_id` but also provide `emoji_name` as null. This is, of course, incorrect. We need to...

> When attempting to send 1x1 pixels https://upload.wikimedia.org/wikipedia/commons/c/ca/1x1.png, I can reach 66 pixels without issue, but 67 pixels returns: In this case it has nothing to do with the size...

I would expect that the ordering of refs received would be stable between renders (and between Vue2 and Vue3). Without it being stable it makes things like "focus the first...

The problem originates from the fact that `patchKeyedChildren` iterates in reverse-order https://github.com/vuejs/vue-next/blob/ba89ca9ecafe86292e3adf751671ed5e9ca6e928/packages/runtime-core/src/renderer.ts#L2049-L2051 This means that any `setRef` calls that occur in `patch` that rely on the `v-for : key` iteration...

This is actually pretty problematic for us in terms of migrating to Vue3. We have lots of accessibility functionalities that rely on being able to properly traverse our `$refs` for...

You may be able to work around this problem via passing the intended index of the ref to your `handleItemRef` and using it to set the ref into the array...

Interesting. Didn't know about [Node.compareDocumentPosition](https://developer.mozilla.org/en-US/docs/Web/API/Node/compareDocumentPosition).