It's no longer possible to set up Ctrl-Tab as a QuicKey shortcut

[Maxxim69]

This is a duplicate of issue #120, expressed more clearly in the hope of attracting attention and getting the issue resolved.

I have two Windows machines where I installed QuicKey for Edge months ago, configuring them to use Ctrl-Tab as a QuicKey shortcut. Both are running the latest version of Edge at the moment, and everything works as intended.

Now I'm failing to do the same on a third Windows PC, also running Microsoft Edge Version 129.0.2792.52. When I paste the code block from Step 5 in the instructions into the console area of DevTools and pass the security check, I get the following response:

Promise {<pending>}
[[Prototype]]: Promise
[[PromiseState]]: "fulfilled"
[[PromiseResult]]: undefined

None of the "Switch to ... tab" hotkeys change to Ctrl-Tab, however.

[eiwe]

I'm having the same issue. I hope this will receive some attention as this is the key feature I'm looking for.

[fwextensions]

Thanks for the bug report. Did you install QuicKey from the Chrome webstore or the one in Edge? It sounds like the one from the Edge store, which I'm still working on getting updated. If the version for QuicKey that you see in the Extensions window in Edge is 1.7.4, then it's the Edge version.

If you're looking for the code from the old instructions for step 5 of option 1:

   chrome.developerPrivate.updateExtensionCommand({
       extensionId: "mcjciddpjefdpndgllejgcekmajmehnd",
       commandName: "30-toggle-recent-tabs",
       keybinding: "Ctrl+Tab"
   });

Or option 2:

   chrome.developerPrivate.updateExtensionCommand({
       extensionId: "mcjciddpjefdpndgllejgcekmajmehnd",
       commandName: "1-previous-tab",
       keybinding: "Ctrl+Tab"
   });
   chrome.developerPrivate.updateExtensionCommand({
       extensionId: "mcjciddpjefdpndgllejgcekmajmehnd",
       commandName: "2-next-tab",
       keybinding: "Ctrl+Shift+Tab"
   });

I need to update the page to handle Edge instructions better. It detects that you're on Edge and swaps in the ID for the Edge store version, but isn't taking into account that that version is behind the Chrome store. But even once they're back in sync, you can install from the Chrome store even on Edge, so either version could be installed, and the webpage itself can't tell.

[Maxxim69]

Thanks for looking into this issue! I'm running QuicKey version 1.7.4 installed from the Edge extension store.
Do you suggest I upgrade to version 2.0 from the Chrome webstore? (Will the extension continue updating automatically if I do?) Or is it better for me to wait until you (or Microsoft) get around to updating the Edge store version?

[fwextensions]

@Maxxim69 you can install the version from the Chrome webstore, though then you'll have two instances of QuicKey (both of which will auto-update), since they have different IDs in the two stores.

I plan on updating the Edge store to be in sync with Chrome, but I wanted to work on a few fixes before auto-updating everyone to the 2.0 codebase, as there were some vague reports of things not working that I'm trying to investigate.

If you decide to try the Chrome store version, I'd appreciate any feedback you have!

[xixixi721]

Has anyone figured out how to resolve this issue on Edge?