Extensions' keyboard shortcuts don't work
-
@Gwen-Dragon Can you edit or modify a bug?
Since the new version 2.4 the shortcuts embedded onto the extensions stopped working in any language, included english (UK and US). -
@izk666 You can add a comment by replying to the email that notified you of the bug number. I modified the bug in Jira to reflect the current status, but you may also add a comment.
-
I use Linux (Solus 4.0 budgie) and Vivaldi 2.4.1488.36-67 and hotkeys are not working. This has worked before (don't remember which update made this fail).
I use the Alt+Q extension for changing between the last two tabs in the browser and it's so frustrating that this has stopped worked -
@Gwen-Dragon No news about Mac version problem? I would really regret to have to switch back to Opera Developer, which stopped for a while to nbe usable having lost the synchronisation.
-
Same issue here on macOS 10.14.4.
This seems like a fairly serious bug and one that I don't imagine would be particularly difficult to fix, surprising it's been in effect for at least 8 months now.
Back to chrome for now : / -
Sorry for the trouble and thanks for reporting.
@jrperez or any other person who reported it, would you share the VB-number of your report so I can follow it up internally please? -
@gaelle The bug that I'm following for this issue is VB-14668.
-
@supersaiyansubtlety This is actually a not-so-simple bug to fix. Keyboard handling in Vivaldi is a lot more complicated than it is in Chrome/Chromium. Vivaldi has its own customizable keyboard shortcuts. Extensions can have assigned shortcuts, and their background scripts can also listen for certain actions. Vivaldi also needs to process access key shortcuts for web sites in a way that coexists as harmoniously as possible with other keyboard shortcuts. There are lots of things going on in the background, on different code paths, and key actions have to be processed correctly for the scope and context. At a low level, keyboard processing is also different on Windows, Linux and Mac, and Chromium has its own internal quirks that vary by platform that also present additional challenges.
This issue is actively being worked on and, bit by bit, the pieces are coming together to finally get extension keyboard shortcuts working in Vivaldi. (That's my understanding, from an outsider's perspective.) Hopefully, @gaelle can provide additional details as to where things currently stand.
-
@xyzzy I don't know if it helps but I'm having a similar issue however if I change from "In Vivaldi" to "Global" it seems to cause the shortcuts to work. Any idea why this is?
EDIT: Or not? Doesn't seem consistent anymore.
-
@kizunal It's issues like this that a group of people internally are working on fixing. VB-14668 is the main bug for getting extension keyboard shortcuts working, and then there are a bunch of other bugs for specific/related issues that were either reported separately or identified in testing... e.g. cases when a background script is listening for certain key actions. The team needs to get all of these fixed, and verify that things are working correctly and consistently across all platforms.
-
@gaelle sorry for the late answer, the VB-number of my report is VB-44682.
By the way, I received an email just some days ago informing me that with the new Vivaldi version the problem should be fixed. It's not. Just for info.
-
@jrperez Thanks for the update. FYI, your bug got closed as a duplicate of VB-14668, and that bug has also since been reopened. I've noted in the active bug that this issue still has not been fixed for you and included a link to your most recent comment in this thread.
Please also note that even when VB-14668 gets fixed, there is still more follow-on work that needs to be done, and there are a handful of additional open bugs that still need to be fixed in order to complete the work to get extension keyboard shortcuts working.
-
@xyzzy thanks for the info!
-
Has there been any progress on this? A macOS user says they've been told this functionality should work, and on Windows it seems to be language-specific.
I have my language set to English (US), and I can set shortcuts on the Extensions page (which, thanks to some breaindead Chrome dev, is hidden behind a hamburger menu in the top-left in a weird little menu all by itself), but "In Vivaldi" has never worked. For most extensions, that's the only option, but when "Global" is an option, it... almost works? Things get very strange if an incognito window has focus, and obviously some of these shortcuts are things that I'd like to be able to use normally when another application has focus. Most notably, there's some shortcuts that I'd like to be able to use in Chrome, which I still have to keep installed and running because of the numerous little problems that keep me from switching to Vivaldi full-time.
I know it's been repeated a million times, but a public bug tracker, even if it was read-only, would be a HUGE help here. I can't begin to comprehend the thought process that concludes the massive "bug status thread" is a reasonable way for users to request status updates, but having a page that allows users to search for existing issues and see their status on their own would somehow create an unreasonable burden on developers who currently have to deal with a ton of duplicate issues because it's impossible to know what has and hasn't already been reported. /rant
-
It is a bit more work, but is not difficult to set custom shortcuts for any extension in vivaldi. You can set the extension to ANY KEY SEQUENCE YOU DESIRE.
- Turn on debug mode from the extensions page.
- Find the long string of lowercased letters that represents the extension in question from the chrome extensions page.
- Search for the location of the folder with this name on your system.
- Navigate to the folder in question.
- Go to this site and get the keycodes for the desired shortcut key sequence.
- Back up the extension directory in its entirety.
- Search the directory for the file or files containing the term 'ctrlKey' or 'shiftKey'. Edit the file(s), replacing the relevant numeric keycodes with the desired ones found on the site above. If you do not understand the logic in these lines (there should only be a few of them), there are plenty of places to get help online. It is trivial for any programmer/Javascript programmer to understand. Ask them.
- After editing the file, go back to chrome extensions menu for the extension in question and click on "load unpacked extension". Select the exact same location of the extension you just edited.
- Open a new tab and test. If the key sequence does not trigger your extension, restart and test again. If still nothing, re-edit file. If you break something (you will not break vivaldi doing this, you will only break your extension), replace the extension with the backed up copy.
I am on mobile, but will go back and clean this up when I get to a computer.
-
The problem still exists...
I can make the shortcut work, but only if set to "Global".
This is not acceptable because it conflicts with shortcuts of other programs.
It is very annoying if you disable/enable things by accident (when in some other program..)Any progress in this?
-
the last working Vivaldi is 2.9.1745.22.
on later version the Bitwarden Autofill Shortcut (CTRL+SHIFT+L) is broken.I have got several Standalone Vivaldi versions and can reproduce this misbehavior reliably (older Vivaldi versions can handle Bitwarden Autofill whereas newer Vivaldi versions can't).
Latest GoogleChrome has no issues. -
Same for me. I thought it was another program stealing the shortcut (originally AMD's settings app did but I've rebound that), but if I'm not the only one with the issue then it might be a Vivaldi issue.
I haven't tried rebinding the extension shortcut to see if that fixes it, though.
-
Same problem with me. It is a bug in Vivaldi. I told this behavior to the developer of Bitwarden and he created a bug report for this (https://github.com/bitwarden/browser/issues/1092). Actually I don't have a bug report id / number.
Because of this problem I'm still using version 2.9.1705.41 of Vivaldi browser. Here autofill shortcut works fine. Just installed the new release 2.10.1745.26 of Vivaldi and the problem still exists.
Hopefully the bug will be fixed soon so I'm able to upgrade to the latest 2.10 build of Vivaldi.
-
Is there a bug tracker where you can see all bugs reported? I would like to know if the bug the developer reported is in work / progress already or if there is a snapshot which fixes this bug. Any ideas?