Cannot use `document.execCommand('copy');` from developer console
document.execCommand('copy') must be triggered by the user. It's not only from the console, it's anywhere that's not inside an event triggered by the user. See below, the click event will return true, but a call without event won't and a call in a dispatched event also.
console.log('no event', document.execCommand('bold'));document.getElementById('test').addEventListener('click', function(){ console.log('user click', document.execCommand('copy'));});document.getElementById('test').addEventListener('fakeclick', function(){ console.log('fake click', document.execCommand('copy'));});var event = new Event('fakeclick')document.getElementById('test').dispatchEvent(event) ;<div id="test">click</ha>See here:https://w3c.github.io/editing/execCommand.html#dfn-the-copy-command
Copy commands triggered from document.execCommand() will only affect the contents of the real clipboard if the event is dispatched from an event that is trusted and triggered by the user, or if the implementation is configured to allow this. How implementations can be configured to allow write access to the clipboard is outside the scope of this specification.
As an alternative, use the copy() command that is built in to the Chrome Dev tools. You can't use document.execCommand("copy") because that requires user action to trigger it.
The copy() command allows you to copy any string (or object as JSON). To emulate document.execCommand("copy") you can get the current selection with getSelection().toString():
copy(getSelection().toString())
If you need to actually test document.execCommand("copy") specifically (for example, to debug a script that uses it), and using the debugger isn't ideal for some reason, you can wrap your code in a click handler, and then click your page:
document.body.addEventListener("click", function() { console.log("copy", document.execCommand("copy"));}, false);
I believe, copy command requires to be having the focus on the browser, and when you go to Console and execute the command, the current window loses focus. But could be other reasons, as it worked if I give in setTimeout().