Benedict Etzel
Benedict Etzel
This is due to Chrome's new(?) cross-domain iframe permissions, which it doesn't grant to our extension. I've tried using the permissions API locally to test whether we can request permission,...
Related: https://github.com/w3c/webappsec-feature-policy/issues/322 In the long-term we'll have to ask Twitch to enable this, but for now a workaround is probably the best. It seems like this changed behaviour was actually...
What happened here is that Chrome implemented a new permission system for clipboard, in the name of web security (great!). This means that browser will be able to better negotiate...
The Chromium change [is making progress](https://chromium-review.googlesource.com/c/chromium/src/+/2164248/). Looks like the feature policy has now been split up into `clipboard-read` and `clipboard-write` to match the permission, so once this is shipped we'll...
Fallback has been added in ceef05a0b1452a983f10e4c61c10b0656897c241, waiting for Twitch approval.
1.0.1 with the fallback is live on Twitch. Keeping this issue open to track Chrome and Twitch implementing the feature policy.
Great, thank you!
As a funny twinkle to all of this, we've now discovered that the `clipboard-write` permission is not required when using the old `document.execCommand('copy')` API in Chrome. As Twitch has been...
We're happy with the current solution and don't necessarily need to wait for Twitch to whitelist those permission properties.
I'd guess duplicate timestamps, specifically when the time resets and a new line has a time stamp from before the line above it.