[Bug]: Coachmark does not work with React 18 Strict Mode when isCollapsed=true

[LR17]

Package

react

Package version

8.120.7

React version

18.3.1

Environment

System:
    OS: Windows 11 10.0.22631
    CPU: (24) x64 12th Gen Intel(R) Core(TM) i9-12900F
    Memory: 10.42 GB / 31.72 GB
  Browsers:
    Edge: Chromium (127.0.2651.74)
    Internet Explorer: 11.0.22621.3527
  npmPackages:
    @fluentui/react: 8.120.7 => 8.120.7
    @types/react: 18.3.5 => 18.3.5
    @types/react-dom: 18.3.0 => 18.3.0
    react: 18.3.1 => 18.3.1
    react-dom: 18.3.1 => 18.3.1

Current Behavior

Coachmark is not visible (just the beak), the popup cannot be opened. When isCollapsed=false the popup is displayed correctly

Expected Behavior

To see coachmark

Reproduction

https://codepen.io/LR17/pen/LYwNMjj

Steps to reproduce

1. Click "Show coachmark" button

Are you reporting an Accessibility issue?

None

Suggested severity

High - No workaround

Products/sites affected

No response

Are you willing to submit a PR to fix?

no

Validations

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

[Shaykoo]

@LR17 Can I take this one?

[LR17]

@Shaykoo Sorry, what do you mean?

[TristanWatanabe]

Can confirm repro that Coachmark is not visible in React 18 strict mode

[tudorpopams]

Hello folks, support for v8 components is very limited from our side, especially for React 18 which could be considered "new" in terms of v8.

We do, however, accept contributions, so feel free to submit a PR if you have a solution for this problem.

[microsoft-github-policy-service[bot]]

This issue has not had activity for over 180 days! We're adding Soft close label and will close it soon for house-keeping purposes. Still require assistance? Please add comment - "keep open".

[microsoft-github-policy-service[bot]]

Because this reported issue has not had any activity for over 180 days, we're automatically closing it for house-keeping reasons.

Still require assistance? Please, create a new issue with up-to date details and latest version of Fluent.