[Popper] Allow setting default props in a theme

[hafley66]

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

I realize now that its very difficult to add defaultProps for Portal, as its used by both modal and popper in base, so it wont inherit the default props.

It came as a surprise that its not possible to default the props for Portal, but I think everything either uses Modal/Popper/or Popover, which all have Portal props passed, so this would add ability to pass defaultProps to the Popper component and allow deeper defaulting

Closes #30116

Will not solve the portal issue, but I believe Popper is last component to not have defaultProps for container, so this will still cover the rest of the Portal'd elements.

[hafley66]

@DanailH @m4theushw Is this a feasible PR/approach?

[mui-pr-bot]

Details of bundle changes

Generated by 🚫 dangerJS against 1827a46

[michaldudak]

Thanks for your contribution. Your implementation seems to be working well. Could you, however, add a test to verify it?

Does this resolve #30116?

[siriwatknp]

👋 The migration PR has been merged.

Please follow these steps to make sure that the contents are all updated. (Sorry for the inconvenience)

1. pull latest master from upstream to your branch
2. if your PR has changes on the *.md or demo files, you are likely to encounter conflict because all of them have been moved to the new folder.
   2.1 revert the change on those markdown files you did
   2.2 pull latest master from upstream (you should not see conflict)
   2.3 make the changes again at docs/data/material/*
3. run yarn docs:api
   • you might see the changes in docs/pages/material/api/* if your PR touches some of the components
   • it is okay if there is no changes

If you are struggle with the steps above, feel free to tag @siriwatknp

[kanoshin]

@hafley66 just a friendly ping. I faced the same issue you have with Shadow DOM. Do you have time to add the unit test @michaldudak requested? I think he wants to have a test similar to the one Modal component has https://github.com/mui/material-ui/blob/master/packages/mui-material/src/Modal/Modal.test.js#L57.

[hafley66]

Unfortunately, I have too many reasons to remove shadow dom (it is breaking selenium tests that are expecting iframes), so I can no longer spend time on this. Plus, recent changes in data grid are why I needed this, and there are other ways to solve Popper props there too

[mui-bot]

Details of bundle changes

Generated by 🚫 dangerJS against 9547027

[michaldudak]

I added the test. Everything seems to be working well.
Thanks for the implementation!

[oliviertassinari]

We need to update https://mui.com/components/popper/. This is no longer true:

https://bundlephobia.com/package/@mui/[email protected]

https://bundlephobia.com/package/@mui/[email protected]

For those that only care about the change, they can still use https://bundlephobia.com/package/@mui/[email protected]

So I think that we can update https://mui.com/components/popper/#unstyled too to mention the bundle size.