Andy Hook

Thanks both for the examples, I can confirm this on my side. I'm going to mark this as a bug to look into. In the meantime one workaround could be...

@marckraw Seems this approach is attempting to pass refs to your standard function comps, the message wouldn't appear in prod as it's a dev only warning afaik. One solution would...

I did some investigation and cross-origin becomes an issue as we'd need access to `contentWindow` in order to bind focus / blur events. The main issue is the inability to...

Thanks @s-yadav , I haven't had a chance to look at this in depth but given that focus should be manually redirected upon removal I wonder if this is a...

Hi @ivanbanov , this is due to how focus events behave in this very specific case e.g. “focused within browser chrome but outside of viewport” , we did [entertain the...

> @andy-hook I wonder if one way to mitigate this here would be to handle things a bit like in `Tooltip` or `HoverCard` where when you blur out of the...

> It seems the original portal had some code to bail out of ssr. Do you mean [this](https://github.com/radix-ui/primitives/commit/3d7300931d46c9306b7ce5bf47601d85e3249842)? > Do we need similar for the new one? I think this...

Another solution is to pass a wrapper node to [`container`](https://www.radix-ui.com/docs/primitives/components/dialog#portal)

> I'd like to know if this hydration error also relates to this issue. I'm conditionally rendering a Dialog or Button based on viewport size. Not directly, no. The server...

It’s gotta be the reported pointer type changing during this interaction, my hunch is that [widening this](https://github.com/radix-ui/primitives/blob/39cd2de90c1c1b39ac5b28704af3b17eab16c36f/packages/react/menu/src/Menu.tsx#L703-L712) to include `pen` will help. Though we should probably review our pen handling...