[data grid] Columns selection component losing anchorElement/scroll state about mui-x HOT 5 CLOSED

@russ0133 in the meantime could you try to replicate this in a minimal live code example? It looks like you have some customization regarding the placement and content of the columns panel in place, right?

Especially helpful would be to know if you memoize the panel in some way or not!

There's no memoization. And yeah, the component itself is inside a MUI Popper and we pass the ref to the button to the columns panel component, the anchorEl being the "Columns" button in the toolbar.

I've tried setting the anchorEl without the ref and instead through slotProps in but with no success. Will try to get a minimal live code going and debug further. This seems to only happen when the server updates - if it's only on the frontend side, then it doesn't "remount" the component.

from mui-x.

Hey @russ0133 and thanks for opening an issue here.
I suspect this is due to the improvement we made on the header rendering.
Let me look into this.

@romgrk if you have any hint please feel free to comment as well! 👍🏼

from mui-x.

@russ0133 in the meantime could you try to replicate this in a minimal live code example?
It looks like you have some customization regarding the placement and content of the columns panel in place, right?

Especially helpful would be to know if you memoize the panel in some way or not!

from mui-x.

Resolved the issue by not passing props directly to the toolbar function:

toolbar: (props) => TableToolbar({ ...props, tableId, filterButtonRef, columnPanelRef })

Instead passing the props on the slotProps in the DataGrid:

        slotProps={{
          toolbar: {
            setFilterButtonEl,
            tableId,
            filterButtonRef,.
            columnPanelRef,
          },
        }} 

Also followed this codesandbox and instead of useRef, I'm using useState

https://codesandbox.io/p/sandbox/old-forest-9dlvdd?file=%2Fsrc%2FDemo.tsx%3A12%2C31-16%2C2

from mui-x.

⚠️ This issue has been closed. If you have a similar problem but not exactly the same, please open a new issue.
Now, if you have additional information related to this issue or things that could help future readers, feel free to leave a comment.

@russ0133: How did we do? Your experience with our support team matters to us. If you have a moment, please share your thoughts in this short Support Satisfaction survey.

from mui-x.