Bug-1773681 Showing Paste button for navigator.clipboard.readText()

[rebloor]

Description

This change addresses the dev-docs-needed requirement of Bug 1773681 Enable showing "Paste" button for navigator.clipboard.readText() when called from Addons which don't have clipboardRead permssion.

The changes include:

• a release note.
• an update to the Interact with the clipboard article. In addition to aligning the documentation with this change, references to the deprecated document.execCommand methods were removed.
• an update to the clipboard section on the Pesmissions page to remove references to the deprecated document.execCommand methods.
• an update to the Clipboard API overview page's Security consideration section to align the documentation with this change.

Related issues and pull requests

Notes in the BCD updated in mdn/browser-compat-data#28587

[github-actions]

This pull request has merge conflicts that must be resolved before it can be merged.

[github-actions]

Preview URLs

• /en-US/docs/Mozilla/Add-ons/WebExtensions/Interact_with_the_clipboard
• /en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/permissions
• /en-US/docs/Mozilla/Firefox/Releases/147
• /en-US/docs/Web/API/Clipboard_API

Flaws (1)

Note! 3 documents with no flaws that don't need to be listed. 🎉

URL: /en-US/docs/Mozilla/Add-ons/WebExtensions/Interact_with_the_clipboard
Title: Interact with the clipboard
Flaw count: 1

• broken_links:
  • Link /en-US/docs/Web/Security/Secure_Contexts is a redirect

External URLs (1)

URL: /en-US/docs/Mozilla/Firefox/Releases/147
Title: Firefox 147 release notes for developers (Beta)

• https://bugzil.la/1773681 (1 time) (Note! This may be a new URL 👀)

(comment last updated: 2025-12-11 17:19:01)

[dotproto]

Be aware that this change does not accurately reflect how to work with the clipboard in extensions across browsers. Specifically, Chrome does not expose navigator.clipboard to extension service workers and offscreen documents cannot access navigator.clipboard due to the API's document focus requirements. As a result, Chrome extensions have to fall back to using the deprecated document.execCommand() APIs in an offscreen document or using navigator.clipboad in a different context (content scripts or extension pages).

While I strongly feel that we should target cross-browser extension develpment, I don't want to block this PR or require a rewrite at the moment. That said, if we don't integrate cross-browser develpment in this revision, we may need to revise this article again in the coming months. @rebloor, do you have any preferences on how we should proceed?

[rebloor]

@dotproto I've added the additional Chrome information. I'd checked for any additional information prior to making the changes and couldn't find anything suggesting there were any further considerations. Do you have a link to any Chrome documentation?