ddong wrote:I have ZERO knowledge... That's why i'm here asking for help. The problem with the original shortcut is that it doesn't work with azerty keyboard. Apparently mozilla team didn't care about that.
Which key combo was it supposed to be? I have some experience with finding strange control characters on an AZERTY keyboard, as mine is also AZERTY (a Belgian one, however, as described here, not a French one).
Edit: Mozilla does care about using their products with non-US keyboards and also for non-en-US languages, and I think I saw a bug somewhere about this problem, only I can't find it back right now.
Click on a tab in the group you want to switch to and you'll exit the view and be returned to Firefox. The tab you clicked on will be active and only the tabs in that group will be visible.
The keyboard shortcut, Ctrl + ` allows you to go to the next Tab Group and Ctrl + Shift + ` to the previous Tab Group.
That's it! The ` key is avalaible on azerty keyboard but you have to use alt and that, firefox doesn't want.
Click on a tab in the group you want to switch to and you'll exit the view and be returned to Firefox. The tab you clicked on will be active and only the tabs in that group will be visible.
The keyboard shortcut, Ctrl + ` allows you to go to the next Tab Group and Ctrl + Shift + ` to the previous Tab Group.
That's it! The ` key is avalaible on azerty keyboard but you have to use alt and that, firefox doesn't want.
Have you tried to: 1) Press and hold Ctrl 2) Press and hold AltGr 3) Press the other key(s) needed for ` 4) Release everything.
If that doesn't work, then maybe some other Ctrl key combination gives what is Ctrl+` on US-QWERTY. However this is less than certain, since Ctrl+` (where ` is 0x60) is not part of the ASCII control group (which define Ctrl+ anything from 0x3F (?) to 0x5F (_) and explicitly states that Ctrl+uppercase and Ctrl+lowercase are equivalent for letters A to Z). You might then be a victim of that bug I couldn't find back.
You might try Crtl + (the key at top left, left of the digit 1) on the far chance that Ctrl+` might not have moved from US-QWERTY to AZERTY even though ` itself did move. Otherwise, I don't know.
Is there a menu item for going to the next tab group (in the Go menu maybe?)? Then you might trigger the menus by keyboard (Alt+something, then the underlined letter in the menuitem name). Admittedly not an elegant solution. There ought to be a method name that you could call, but someone other than me will have to name it.
I have just tried keyconfig, and it is a very nice and useful addon.
I am using Mac, I have observed that when changing to a keybinding which uses the Alt key, when typed into the textbox, the character is translated into a special character. So if I type say, "Alt + S", it enters only ß (does not show Alt symbol). I would expect this behavior in the textbox, since that is what Macs do by default when using the Alt key. However, apparently because of this, keyconfig is not recognizing it as "Alt + S", and so there is no mapping done, and the command does not work. I can put the code <key key="S" modifiers="alt" command="some_command"/> into an overlay and it will work, so I know that that combination is valid on Mac. It is just that I cannot assign it to that using keyconfig.
If, however, the Alt key is combined with another modifier, eg, "Alt + Cmd + S", then "<Alt symbol><Cmd symbol>ß" appears in the textbox. I can assign it, and it will work, however, from then on, "<Alt symbol><Cmd symbol>ß" (with the special character) is what will always appear in the keybinding list.
So in the first case, Alt with no other modifer, keybinding cannot be assigned.
In the second case, Alt with another modifier, keybinding can be assigned, but the special character is used in the keybinding list. (and possibly in the keybinding itself?)
JavaScript error: chrome://keyconfig/content/keyconfig.js, line 419: props is undefined JavaScript error: chrome://keyconfig/content/keyconfig.js, line 424: props is undefined
ddong wrote:Hello, i'm trying to change the next/previous tab group keyboard shortcut. So i ended up downloading this extension. However, even after long searching, i couldn't find the code related to these actions.
Has anyone else noticed that the userChrome.css styles for the keyconfig window do not work anymore? Now all the text looks exactly the same. Is there any way to fix this? It was extremely useful. I noticed it in firefox 24, but it may have happened a few versions earlier and escaped my notice.
I am referring the userChrome.css styles listed on the first page of this thread, listed here again:
Thanks for the fix. I tried it and it sort of worked, but the styles still did not look exactly the same. There seems to be a logic problem in that it will only return at most one property whereas the original code could return up to 5 properties.
I tweaked the code here to get the desired result, though I'm not positive it's correct either:
Of course, with Gecko 21 or older (Firefox 21 or older, SeaMonkey 2.18 or older, and, I think, Thunderbird 21 or older), the "older" version of the code should be kept. All these versions are obsolete though AFAIK, except for "17esr" versions of Firefox and Thunderbird.
Just upgraded to TBird 24, and it appears to have broken some of my keyconfig commands. Specifically, the key I had bound to toggle message view from text<->html now has no effect (and produces no messages in the console). I was using this code:
Typing just the pref.getBoolPref("...") part in the console gives a "ReferenceError: pref is not defined" message. And this page https://developer.mozilla.org/en-US/doc ... eleases/24 seems to suggest that the pref object has been removed. But I was unable to get it working with "Services.prefs" as listed (though to be honest, I'm not even sure if that reference applies, or if the scope of the console is the same as keyconfig is seeing). And weirdly, hitting my bound key produces no output, error messages or anything.
mozillaZine is an independent Mozilla community and advocacy site. We're not affiliated or endorsed by the Mozilla Corporation but we love them just the same.