Cannot copy paste in dev tools
-
As a web developer this is ridiculously bugging me for that I have to two-finger of highlighted text to select COPY and PASTE in the popup menu, instead of simple Ctrl+C/V... a lot of effort to write codes!
-
ctrl/command + X won't cut either.
-
@dachy Yes, agreed, very frustrating, hopefully it will be fixed soon.
I've had to downgrade to a previous version (5.2.2623.48) until this is fixed, it creates unnecessary friction while developing and you then lose focus 😔
Then also remember to turn automatic updates off (unlike me) 🤦
-
I had to switch to Brave for development until this is fixed. I already miss my stacked tabs. Hopefully this will be resolved soon.
-
It seems that copy paset can be done while the context menu is displayed on devtools.
This is only a temporary workaround. -
@avladov just downgrade to a previous version of Vivaldi and you still have your stacked tabs...
-
Just installed the latest push, seemingly a minor update having nothing to do with this fix. Shame~
-
@scpio said in Cannot copy paste in dev tools:
@avladov just downgrade to a previous version of Vivaldi and you still have your stacked tabs...
Sometimes just unsure how previous it should be... too many versions.
-
@scpio I don't want to do that. I get it might fix the issue, but for me using an older browser version is bad in general.
There might be security holes that were patched in the newer version. It's not worth the risk, no matter how small it is.
-
FYI, this issue seems to be getting a lot of attention internally at the moment. It looks like the devs might be close to having a fix in place but I don't really want to say anything more (or get anybody's hopes up) until I actually see it fixed in a "pre-Snapshot" internal build and the internal testers confirm that the fix does not break anything else. (Keyboard shortcuts are a complicated thing in Vivaldi.)
The active bug for this glitch is now VB-89832
-
@avladov Yes absolutely - I recommend using the previous version for any internal development where use of devtools is required.
And for your general web browsing use the latest version which includes patches for all known vulnerabilities.
@dachy [5.2.2623.48] is an older version that doesn't have the bug.
Yes, it's very inconvenient but as @xyzzy says, there should be a fix soon 🤞🏼🤞🏼🤞🏼
And I'd like to take this opportunity to say thank you to the devs for making such a great browser, and leading the way with so many innovative features.
-
FYI, VB-89832 has been fixed internally. The fix should make it into the next Snapshot build for further testing. However, it is still too early to say whether the fix can be back-ported and released in a 5.3 Stable update.
-
Great thanks @xyzzy - snapshot here: https://vivaldi.com/blog/desktop/chromium-bump-and-accent-from-page-vivaldi-browser-snapshot-2722-3/
-
Okay that snapshot resolves the issue - but is there any way to have the Snapshot use the existing profiles/preferences?
-
Ahh got it.
--args --user-data-dir=(backup your user data dir first!)
Default location:
/Users/{USER}/Library/Application Support/VivaldiGreat, thanks. Looking forward to this bugfix making it to a proper release in the near future 🤞🏼
-
@scpio Whatever you do, DO NOT launch a Snapshot build such that it uses your active Stable profile. Instead, make a copy of it and point your user-data-dir at the copy.
Here's why: Vivaldi profiles are NOT backwards-compatible. If you launch Vivaldi (Stable), which (compared to Snapshot) is an older Vivaldi version, your profile will probably get corrupted. If you run Vivaldi Stable and Vivaldi Snapshot concurrently, using the same profile directory, it is virtually guaranteed that the profile will get corrupted.
-
Yes, very good point, thanks @zyzzy.
I did copy the default folder to 'VivaldiCopyForSnapShot' first and then used:
--args --user-data-dir= /Users/{USER}/Library/Application Support/VivaldiCopyForSnapShot👍🏼
-
Just installed new update (5.3.2679.68) and this is STILL NOT FIXED. WTF!!! When will it be resolved?
-
@Deralict The fix for VB-89832 was fairly extensive and I presume that it was deemed to risky to back-port into a 5.3 update at this time. If no issues/regressions/side-effects are reported by Snapshot testers, the fix may make it into the next 5.3 update... or we might have to wait for 5.4 Stable to get released.
-
Hey guys, this is super annoying. Please, do something.
