[Bug]: dev docs positioning components some pop overed comonents lost their target when rtl, ltr switched

[ohiomanbo]

Component

Other...

Package version

none

@microsoft/fast-element version

none

Environment

none

Current Behavior

https://react.fluentui.dev/?path=/docs/concepts-developer-positioning-components--docs&globals=storybook_fluentui-react-addon_dir:ltr

hi first of all i'm not good at using english
and this is not a review of library, just a report on your docs site

in your teams docs site(upper link), there are some examples which set to be shown always
(http://react.fluentui.dev/?path=/docs/concepts-developer-positioning-components--docs#match-target-size)

and if you change ltr <-> rtl, they briefly lost their own parent(target) and replaced to left top postition.

in my experience, this is speculated to be a phenomenon where a temporary ref is lost due to a conditional rendering or layout change.

Expected Behavior

dismiss pop overed components when they lose ref target or keep their own position

Reproduction

http://react.fluentui.dev/?path=/docs/concepts-developer-positioning-components--docs#match-target-size

Steps to reproduce

1. go to link on content
2. and click ltr, rtl switch button
3. look left and top corner

Are you reporting an Accessibility issue?

None

Suggested severity

Urgent - No workaround and Products/sites are affected

Products/sites affected

No response

Are you willing to submit a PR to fix?

no

Validations

• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• The provided reproduction is a minimal reproducible example of the bug.

[behowell]

Hi @ohiomanbo, when I try this, it seems like a transient issue, and the popovers move to the correct anchor briefly after switching to RTL. Is that what you're seeing, or is the page broken for you after switching to RTL?

If it's just a transient issue, this is probably a Won't Fix, given that it doesn't affect the ability to use the documentation page, and doesn't affect production code.

[miroslavstastny]

Keeping this one open for now, we would like to understand the root cause.