Intent to prototype: Async clipboard API improvement for read()/readText() and write()

Skip to first unread message

Edgar Chen

Mar 6, 2023, 8:49:29 AMMar 6

Clipboard writeText API was shipped to security context in Firefox 63 [1], but the readText API is only exposed to web extensions

and read/write APIs are put behind `` pref, which is disabled by default. 

We are currently working on making read and readText APIs shippable to web pages by improving the security model.
This will show a context menu item to get user confirmation whenever the page tries to read the system clipboard programmatically
and the clipboard data isn’t from the same origin document.

For the write API, we are currently working on making the ClipboardItem constructor take a promise, which is resolved with
the actual write data, as the data type. And the write API also supports non-text type, i.e. image/png, now.



Standards Body
: W3C

Platform coverage
: All

Preference: `` for readText()
          `` for read()/write()

DevTools bug: N/A


Other browsers:

  • Blink: Shipped (M66) with clipboard permission checks.
  • WebKit: Shipped with the security model, which is similar to what we are implementing,




Best Regards,

Edgar Chen

Reply all
Reply to author
0 new messages