Why navigator.clipboard.writeText() Silently Fails When Users Switch Tabs

A subtle browser behavior can cause clipboard copy functions to fail without any visible error when users switch tabs or windows mid-operation. The Async Clipboard API requires the document to have active focus at the exact moment writeText() is called, not merely when the user first clicked. If an awaited operation — such as a fetch request — creates a timing gap between the click and the clipboard call, focus may have shifted, causing the browser to silently reject the promise with a NotAllowedError. Common fixes like loading spinners, try/catch blocks, or retries do not resolve the issue because they fail to address the root cause of lost document focus. The recommended solution is to pass a promise directly into ClipboardItem so the clipboard slot is claimed during the original click gesture, while the data resolves asynchronously afterward.