It is impossible to give clipboard access to iframes.
According to #https://github.com/w3c/webappsec-permissions-policy/issues/322#issuecomment-618009921 and this bug report, chrome versions 81-85 had broken iframe clipboard permissions. The feature policies clipboard-write and clipboard-allow were created to solve this issue, but the UHC seems to not recognize them. (The bug was fixed in Chrome 85, which was first used in Electron 10.0, a version newer than the UHC's Electron.)
The same iframe that works in modern browsers (<iframe ... allow="clipboard-read; clipboard-write;">) will fail in the UHC2.
Expected behavior
The parent window (the UHC) should recognize the policies and change behavior accordingly; this does not happen.
Screenshots
Desktop (please complete the following information):
Application version: v2.0.5
Asset pack version: v2
OS: MacBook Air (M1, 2020), running macOS Monterey 12.1 (21C52)
Additional context
iframe is meant to be used for the "share" button in this project. The iframe is in use here, with security policies functioning as expected.
Here is a link to a mod file which includes the iframe within its template.
It is impossible to give clipboard access to iframes. According to #https://github.com/w3c/webappsec-permissions-policy/issues/322#issuecomment-618009921 and this bug report, chrome versions 81-85 had broken iframe clipboard permissions. The feature policies
clipboard-write
andclipboard-allow
were created to solve this issue, but the UHC seems to not recognize them. (The bug was fixed in Chrome 85, which was first used in Electron 10.0, a version newer than the UHC's Electron.)To Reproduce Steps to reproduce the behavior:
<iframe ... allow="clipboard-read; clipboard-write;">
) will fail in the UHC2.Expected behavior The parent window (the UHC) should recognize the policies and change behavior accordingly; this does not happen.
Screenshots
Desktop (please complete the following information):
Additional context iframe is meant to be used for the "share" button in this project. The iframe is in use here, with security policies functioning as expected.
Here is a link to a mod file which includes the iframe within its template.