[Feature]: Custom boundary for autoSize in Popper

[miroslavstastny]

Library

React Northstar / v0 (@fluentui/react-northstar)

Describe the feature that you would like added

autoSize prop in Popper settings currently uses overflowBoundary. Add configuration option for the autoSize to use a separate boundary.

That feature is required for a Dropdown component scenario.
Codesandbox with repro: https://codesandbox.io/s/v0-dropdown-overflow-vj5xzf?file=/example.js

The Dropdown list in the example has the following options applied:
positionFixed: true to allow the dropdown list to overflow the message it is rendered in
autoSize: "width-always" to fix the width of the list to match the dropdown input (required when fluid and positionFixed are used at the same time)
overflowBoundary and flipBoundary set to the scroll container to correctly flip the dropdown list
unstable_disableTether: "all" to allow the dropdown list to cover the input if there is not enough space

With this config the autoSize uses the overflowBoundary to set the dropdown list width which is incorrect:

Have you discussed this feature with our team

No response

Additional context

No response

Validations

• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[miroslavstastny]

We should test and eventually fix in v9 first, only after that decide what to do next.

[JustSlone]

Agree, let's solve this in v9, then backport to v0 based on customer need / cost tradeoff.

I assume @microsoft/teams-prg is taking point given the assignment in board, correct if wrong.

CC: @smhigley and @microsoft/cxe-coastal

[msft-fluent-ui-bot]

Because this issue has not had activity for over 150 days, we're automatically closing it for house-keeping purposes.

Still require assistance? Please, create a new issue with up-to date details.

[microsoft-github-policy-service]

Because this issue has not had activity for over 150 days, we're automatically closing it for house-keeping purposes.

Still require assistance? Please, create a new issue with up-to date details.

[microsoft-github-policy-service]

Because this issue has not had activity for over 150 days, we're automatically closing it for house-keeping purposes.

Still require assistance? Please, create a new issue with up-to date details.