Marija Najdova

It doesn't look like the issue contains reproduction for us to investigate. Please create a CodeSandbox with a reproduction and a better description of the problem.

It would work if you use the `Popper` component, e.g. https://codesandbox.io/p/sandbox/popover-issue-forked-7fxkvy?file=%2Fsrc%2FMyPopover.jsx%3A10%2C24. Is there a specific reason for using `Popover` vs `Popper`? Check the docs page for more details: https://mui.com/material-ui/react-popper/

Considering the number of issues you linked, it seems like this is common problem for people. It could be valuable to add a demo to teach people what are the...

> So there is a kind of true-false relationship of these functionalities on which you can address by adding more props to their APIs, or in my opinion one final...

Thanks for the report, looks like we missed handling function for the slotProps.paper, e.g. I see https://github.com/mui/material-ui/blob/next/packages/mui-material/src/Popover/Popover.js#L128. @DiegoAndai can you please check this?

Can you share a screen recording, it's not clear what place you are referring to. Thanks!

It's not clear from the description of the issue, but it is likely related to some version of vite (or the caching algorithm used). I would propose trying https://github.com/mui/material-ui/issues/32727#issuecomment-1211036631, https://github.com/mui/material-ui/issues/32727#issuecomment-1311143759...

I guess then we can consider this duplicate of https://github.com/mui/material-ui/issues/31835

Can you please provide a CodeSandbox (https://material-ui.com/r/issue-template-next), or a link to a repository on GitHub that reproduces the problem?

Alright, I can reproduce