"Copy" button on page when mounting doesn't work
See original GitHub issueHi,
When running drive.mount('/content/drive')
and clicking on the link generated by it, we arrive on a page that contains a code which we can copy using a button (or manually copy/pasting). This “copy” button doesn’t work and leads to a lot of people thinking Colab has a timeout issue (see #1538). In order to copy correctly, one needs to manually copy and paste.
It would be great to see it fixed! Thanks in advance!
Issue Analytics
- State:
- Created 3 years ago
- Reactions:7
- Comments:6 (3 by maintainers)
Top Results From Across the Web
In reactJS, how to copy text to clipboard?
Use this simple inline onClick function on a button if you want to programatically write data to the clipboard. onClick={() => {navigator.clipboard.
Read more >[SOLVED] Copy and Paste Not Working on Windows 10
Copy and paste not working properly on your Windows 10 PC? Here's the real fix! Try these fixes and make your broken copy-paste...
Read more >How to Fix When Copy-Paste Isn't Working
It might be just a temporary glitch, and by restarting the device, you might be able to fix it.
Read more >Implementing copy-to-clipboard in React with Clipboard API
Here, I've set up the component ClipboardCopy , which accepts the property copyText . This will be the text that we want our...
Read more >Fix Copy and Paste Not Working in Chrome
If copy-paste is not working on Chrome, this may indicate the webpage you're visiting is using a special script that's blocking text ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It’s not about the button per se. No matter how I would copy, authentication always fails.
OK, we believe the fix on the oauth2 page is now live everywhere, so this should be working again.
Thanks again everyone for the reports!