Extensions' keyboard shortcuts don't work

izk666

modedit split from https://forum.vivaldi.net/topic/31027/keyboard-shortcuts-not-working-with-extensions

After spending some time researching I have discovered something "funny": The keyboard shortcuts for extensions only works if the browser is in english language (UK or US).
If you use spanish, french or german don't work at all. (I haven't tried all the list of languages available. Just those).

Can someone check it?

PS: I didn't realize that it's the mac forum and I use Windows. Perhaps could be the same error.

izk666

I have found a way to use keyboard shortcuts: just set Vivaldi's language to english (UK or US).
If you use spanish, german or french shortcuts don't work. I haven't tried other languages, but I suppose that they fail too.

Can someone confirm if the trick works?

izk666

@gwen-dragon Bug reported as VB-46540.

jrperez

@izk666 Might be, I use US both on Windows and Mac and extension shortcuts work on Win but not on Mac

silicium

I have the same Issue, recent OSX Version, recent vivaldi version, recent 1password X version.

Problem exist on two macs with the same configuration.
I'am able to change the Keyboard Shortcut in the Settings, which might mean that the extension is generally able to catch the shortcuts at least in the extension configuration page.

I've tried several combinations with either command, option or control key to avoid some platform specific <command> key issues. It didn't changed anything.

The issue does not exist on Google Chrome

silicium

I've now also changed locale settings from UK to US, which changed nothing.
beside that i've tried:

Full Keyboard Access: Inherit from System Preferences
Allow Keyboard Shortcuts: Disable (to omit vivaldis shortcut "interception")
Space for Fast Forward: Disable

Dear Vivaldi Developers, would you please give us some updates about that issue?
Main Reason for me is the use of 1password. 1password is forwarding their requests to Vivaldi because its an Vivaldi issue. I'am sure if it is only 1password related, you will get a free team account for testing implementation!

dakira

As was stated in the Windows thread regarding this topic, this seems to be related to language.

On mac I cannot change the language of Vivaldi, to test this, tough. I'd happily switch to English if this allows me to use extension shortcuts.

watain666

Same issue here
Vivaldi version: 2.3.1440.60 (Stable channel) (64-bit)
OS: Ubuntu 18.04.2 LTS

jrperez

@dakira Maybe on Windows that's the case but not on MacOS. At least not in mine, I'm using the latest Vivaldi in English on MacOS Mojave and the extension shortcuts don't work (and they never worked before either with any previous Vivaldi or MacOS version, and I've been always using the English version).

izk666

@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).

Ayespy

@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.

dajjen

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

GianMarcoTavazzani

@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.

supersaiyansubtlety

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 : /

Gaëlle

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?

xyzzy

@gaelle The bug that I'm following for this issue is VB-14668.

xyzzy

@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.

kizunal

@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.

xyzzy

@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.

jrperez

@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.