Add visual feedback for failed clipboard write on older browsers

[Chucks1093]

Summary
On older browsers where the Clipboard API is unavailable, copy actions fail silently with no user feedback. A fallback that detects the failure and shows a brief error message or manual-copy prompt prevents user confusion.

Scope

• identify copy-to-clipboard actions that use the Clipboard API
• add error handling that catches clipboard write failures
• show a brief error message or fallback prompt when the write fails

Acceptance Criteria

• a clipboard write failure shows a visible error or fallback message
• the fallback does not appear when the clipboard write succeeds
• the error handling does not suppress the original failure for debugging

Contributor coordination: if you pick this up, reach out in Telegram for updates or clarification: https://t.me/accesslayerorg

[LaahAbba]

@LaahAbba has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hi I'm a full stack developer I'll like to work on this issue because It picks my interest and Ive got experience with similar projects I'll have it solved in 24 hours or less

ℹ️ Repo Maintainers: To accept this application, review their application or assign @LaahAbba to this issue.

[Jerry-Tekh]

@Jerry-Tekh has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hi, maintainer I can work on this issue and implement all the necessary fix for the visual feedback

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Jerry-Tekh to this issue.

[iwayemi5]

@iwayemi5 has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

I'd like to work on this as I have reviewed the scope and I should have a PR ready in 50minutes

ℹ️ Repo Maintainers: To accept this application, review their application or assign @iwayemi5 to this issue.

[N-i-xx]

@N-i-xx has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Dear maintainer
Please assign me this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @N-i-xx to this issue.

[khanavi272-spec]

@khanavi272-spec has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

I would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @khanavi272-spec to this issue.

[michaelvic123]

@michaelvic123 has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

please assign

ℹ️ Repo Maintainers: To accept this application, review their application or assign @michaelvic123 to this issue.

[extolkom]

@extolkom has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Please assign me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @extolkom to this issue.

[drips-wave]

Congratulations, @N-i-xx! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @N-i-xx: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊