[Bug]: unable to copy to clipboard content within storybook doc blocks

[spmonahan]

Library

React Components / v9 (@fluentui/react-components)

System Info

n/a

Are you reporting Accessibility issue?

no

Reproduction

https://react.fluentui.dev/?path=/docs/components-textarea--default

Bug Description

Actual Behavior

1. Type some text into a Fluent Textarea
2. Copy the text
3. Paste the text
4. Whatever was previously in your clipboard is pasted

Expected Behavior

I should be able to copy text from a Textarea.

textarea_copy_paste.mp4

Browsers

• Firefox 117.0.1 (64-bit) Windows 11
• Edge 117.0.2045.36 (Official build) (64-bit) Windows 11

Logs

No response

Requested priority

High

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.

[ganitx]

I couldn't replicate this issue in Edge Version 117.0.2045.41 (Official build) (64-bit) Windows 10, Firefox Windows 10, and Chrome. Copy and paste works by selecting and using keyboard shortcuts in windows 10.

[Hotell]

this is also happening for Field https://react.fluentui.dev/?path=/docs/components-field--default within storybook docs. outside storybook everything works as expected so this must be some very weird storybook clipboard hijacking.

note: also present on web-components v3 docsite https://web-components.fluentui.dev/?path=/docs/components-textinput--text-input

when you press cmd/ctrl+c there is this storybook popup shown "copied"

this seems to be fixed in storybook 7 ( carbon is on v7 https://react.carbondesignsystem.com/?path=/docs/components-textarea--overview )

[Hotell]

confirmed this is SB bug and they have no plans to fix it for v6 unfortunately storybookjs/storybook#18611 (comment)

[Hotell]

@behowell ran into similar thing some time ago #24135.

With v6 only workaround is to stopping rendering show code functionality - which for these more complex control is not something we should do. thoughts ?

[spmonahan]

Perhaps we should upgrade to v7? @TristanWatanabe upgraded another repo to v7 so he can probably comment on the effort required.

[microsoft-github-policy-service]

Because this issue has not had activity for over 180 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 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.

[mltejera]

Hey is there an ETA on the v7 upgrade? This bug is making some of the theme tooling on our site unusable... like, if it were a product this would be a sev 0, work through the weekend, we're breaking SLA and losing money bug.

[EdDaWord]

+1 to Mason's point. In cases like createV9Theme

There's no way to actually copy the output, even inspecting the HTML only gets you 80% of the output. It'd be amazing if we could upgrade to v7.

[Hotell]

like, if it were a product this would be a sev 0, work through the weekend, we're breaking SLA and losing money bug.

thanks for your input. as you can see this has been opened almost a year ago with no complaint besides internal core team.

Hey is there an ETA on the v7 upgrade? This bug is making some of the theme tooling on our site unusable... like, if it were a product this would be a sev 0, work through the weekend, we're breaking SLA and losing money bug.

it's planned for this Quarter - you can check all planned work within our Unified Project Board

[robertpenner]

This copy hijacking was affecting my work as well.

[Hotell]

closing #30858