You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the Motion documentation website, when clicking the “SOURCE” button below an interactive example, a code preview appears. However, when clicking the “Copy” button next to the displayed code, nothing is copied to the clipboard.
Steps to reproduce
1. Go to the react-quick-start
2. Find an interactive example, example enter-animation
3. Click the “SOURCE” button in the example
4. A code preview appears
5. Click the “Copy” button next to the displayed code
6. The code is not copied to the clipboard
Expected behavior
Clicking the “Copy” button should copy the displayed code to the clipboard.
Video:
Apologies for the low video quality. If it’s unclear, I’d be happy to provide a higher-quality recording.
Recording.at.2025-03-10.20.28.40.mp4
Environment details:
OS: Mac OS Sequoia Version 15.3.1 (24D70)
Browser: Version 133.0.6943.143 (Official Build) (arm64)
I also tested this on Edge and Arc browsers on my computer, and the issue persists.
The text was updated successfully, but these errors were encountered:
Describe the bug:
On the Motion documentation website, when clicking the “SOURCE” button below an interactive example, a code preview appears. However, when clicking the “Copy” button next to the displayed code, nothing is copied to the clipboard.
Steps to reproduce
1. Go to the react-quick-start
2. Find an interactive example, example enter-animation
3. Click the “SOURCE” button in the example
4. A code preview appears
5. Click the “Copy” button next to the displayed code
6. The code is not copied to the clipboard
Expected behavior
Clicking the “Copy” button should copy the displayed code to the clipboard.
Video:
Apologies for the low video quality. If it’s unclear, I’d be happy to provide a higher-quality recording.
Recording.at.2025-03-10.20.28.40.mp4
Environment details:
I also tested this on Edge and Arc browsers on my computer, and the issue persists.
The text was updated successfully, but these errors were encountered: