[Bug]: Incorrect Positioning doc link

[mgilarmo]

Component

Popover

Package version

9.72.2

React version

18.3.1

Environment

System:
    OS: Windows 11 10.0.26200
    CPU: (16) x64 Intel(R) Xeon(R) Platinum 8370C CPU @ 2.80GHz
    Memory: 35.18 GB / 63.95 GB
  Browsers:
    Chrome: 143.0.7499.170
    Edge: Chromium (143.0.3650.96)
    Internet Explorer: 11.0.26100.1882
  npmPackages:
    @fluentui/azure-themes: ^8.6.18 => 8.6.146
    @fluentui/jest-serializer-merge-styles: ^8.0.26 => 8.0.47
    @fluentui/react-components: ^9.72.2 => 9.72.9
    @fluentui/react-icons: ^2.0.218 => 2.0.316
    @fluentui/react-portal-compat: ^9.0.167 => 9.2.27
    @types/react: 18.3.1 => 18.3.1
    @types/react-dom: 18.3.1 => 18.3.1
    react: 18.3.1 => 18.3.1
    react-dom: 18.3.1 => 18.3.1

Current Behavior

The link to the positioning docs in the Popover attributes is incorrect. Clicking on the link brings you to:
https://storybooks.fluentui.dev/react/iframe.html?path=/docs/concepts-developer-positioning-components--docs
(note the inclusion of "iframe.html")

Expected Behavior

The correct link seems to be:
https://storybooks.fluentui.dev/react/?path=/docs/concepts-developer-positioning-components--docs

it looks like it is correct in:

• https://storybooks.fluentui.dev/react/?path=/docs/components-combobox--docs
• https://storybooks.fluentui.dev/react/?path=/docs/concepts-migration-from-v8-components-keytips-migration--docs

Reproduction

https://storybooks.fluentui.dev/react/?path=/docs/components-popover--docs

Steps to reproduce

Click on link in Popover attributes:
https://storybooks.fluentui.dev/react/?path=/docs/components-popover--docs

Are you reporting an Accessibility issue?

no

Suggested severity

Medium - Has workaround

Products/sites affected

No response

Are you willing to submit a PR to fix?

yes

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.