[DataGrid] Fix GridPanelAnchor positioning

[k-rajat19]

• I have followed (at least) the PR section of the contributing guide.

Closes #15005

Before: https://codesandbox.io/p/sandbox/condescending-tereshkova-ytknq9
After: https://codesandbox.io/p/sandbox/mui-mui-x-x-data-grid-forked-sh3fw2?file=%2Fsrc%2Fdemo.tsx

[mui-bot]

Deploy preview: https://deploy-preview-15022--material-ui-x.netlify.app/

Generated by 🚫 dangerJS against 971a563

[oliviertassinari]

The change makes sense, but if we look at the root, it seems strange that we need this gridPanelAnchor DOM node. I wonder if we couldn't remove it and instead rely on an existing DOM, e.g. .MuiDataGrid-topContainer.

[k-rajat19]

Hi @oliviertassinari ,
this approach has been decided to use here before that we relied on column header DOM which is inside the top container.
and I feel like we should stick to the current approach, though I haven't given any try to whether we can get rid of this extra element or not.

[oliviertassinari]

this approach has been decided to use here

Ok, so the child .MuiDataGrid-columnHeaders doesn't work. Now, why would its parent .MuiDataGrid-topContainer not work?

[k-rajat19]

On surface it looks like this approach was chosen because of the positioning issues of the preference panel
if we reference panel to the top container, then in case of horizontal scroll panel will be scrolled also and becomes invisible.
@romgrk can you confirm this? if you still remember the details since the change was made more than one year ago 😅

[cherniavskii]

@k-rajat19 Correct – topContainer didn't work, that's why I added panel anchor:

[oliviertassinari]

Ok, thanks, so nothing else can be used here, nice regression fix 👍.

---

Off-topic. One thing we could consider in the future is to change the anchor of the filter panel bested on the trigger. There is quite a long distance for the mouse to travel: https://mui.com/x/react-data-grid/filtering/

Screen.Recording.2024-10-21.at.16.10.17.mov

Related to #6419.