copy is not successful NotAllowedError: The Clipboard API has been blocked #5775
Comments
|
Looking into the source for vscode it looks like the iframe allows clipboard read and write, so I wonder if this has something to do with the gesture not being connected directly to the action With some research it looks like browsers have security features that protect against clipboard access that isn't associated with user actions |
|
We're an iframe inside an iframe here. VS Code iframes the Dart-Code extensions webview, and the webview then has to iframe DevTools (we can't set a raw URL for the first iframe, we can only set its html contents). I suspect we just need to put the same I've opened Dart-Code/Dart-Code#4540 about this. |
|
I've been digging into this, but been unable to fix. I added some notes about this to Dart-Code/Dart-Code#4540. It seems like passing clipboard access cross-origin in iframes isn't working (this might be the cause of our other issue - microsoft/vscode#129178). Some people are falling back to older clipboard APIs that don'thave the same permissions requirements, but since this is handled by Flutter I don't know if that's a simple option. One possibility could be to pass the text up to the parent iframe via postMessage where we can write to the clipboard, but it feels a bit weird to be doing that in DevTools. Thoughts? |
|
Since this same setup seems to work outside of VS Code (nested iframes crossing origins with |
CoderDake
added
the
P2
 Adds a fallback behaviour for copying which will allow copy buttons to actually work in VSCode. NOTE: success toasts will no longer show in VSCode though. I've also added some logging just in case a user is looking at their console when a copy fails. Hopefully this provides enough information that the unhide-able error doesn't look suspicious.  Related to Dart-Code/Dart-Code#4814 Fixes #5775
 Adds a fallback behaviour for copying which will allow copy buttons to actually work in VSCode. NOTE: success toasts will no longer show in VSCode though. I've also added some logging just in case a user is looking at their console when a copy fails. Hopefully this provides enough information that the unhide-able error doesn't look suspicious.  Related to Dart-Code/Dart-Code#4814 Fixes #5775
 Adds a fallback behaviour for copying which will allow copy buttons to actually work in VSCode. NOTE: success toasts will no longer show in VSCode though. I've also added some logging just in case a user is looking at their console when a copy fails. Hopefully this provides enough information that the unhide-able error doesn't look suspicious.  Related to Dart-Code/Dart-Code#4814 Fixes #5775 Mirror package:web version from Flutter SDK
While testing log copying behaviour in VSCode, I noticed that the copy button is no longer working, when using it in the context of VSCode.
Alternatively, I have run Dart Devtools from the command line using
flutter run -d chrome. When running devtools like this, the copy functionality seems to work just fine.The following is the log message that is output in the vscode developer console when the copy fails.
DevTools version: 2.23.1
Connected Device:
CPU / OS: x64 (64 bit) macos
Dart Version: 3.1.0-63.1.beta
Flutter Version: 3.11.0-1.0.pre.1 / beta
Framework / Engine: 74e4b092e5 / 992cdb6cd4
Connected app type: Flutter native (debug build)
The text was updated successfully, but these errors were encountered: