Skip to content
This repository has been archived by the owner on Jan 10, 2024. It is now read-only.

consider supporting Clipboard API #52

Open
jaked opened this issue Mar 2, 2023 · 1 comment
Open

consider supporting Clipboard API #52

jaked opened this issue Mar 2, 2023 · 1 comment

Comments

@jaked
Copy link

jaked commented Mar 2, 2023

feedback from @HiDeoo:

I tried adding a copy to the clipboard button but due to the iframe setup, it looks like it's not possible to use the Clipboard API as we get a DOMException: The Clipboard API has been blocked because of a permissions policy applied to the current document.. The iframe allow attribute is currently set to camera;microphone;xr-spatial-tracking. Is there any plan / thoughts regarding adding at least clipboard-write (clipboard-read may be too much) to the list of allowed permissions? (ref: https://web.dev/async-clipboard/#permissions-policy-integration - cross-origin syntax: https://stackoverflow.com/a/69741484/1945960)

@Hacksore
Copy link

Hacksore commented Mar 23, 2023

Started copying what @HiDeoo is doing but for package managers.

Sadly you need the clipboard-write on the iframe, are security considerations the blocker here atm?

image

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants