Note that it is possible to disable compatibility checking by adding a boolean 'extensions.checkCompatibility' through about:config.
The global scope is just there, any JavaScript included by an overlay should run within it. The function calls are in elements.xul within chrome://dta/content/integration/ (View > Page Source to look into it), while the object containing the functions is defined in the elements.js.pooz wrote:Where are these scopes and method-calls written, from that you wrote these codes?
Trypooz wrote:Is there a way, to call a bookmark/specific URL in a new Tab also by a keycommand?
Code: Select all
gBrowser.selectedTab = gBrowser.addTab(getShortcutOrURI('keyword',{}));
Stating to support maxVersion of 3.0.* (the * is not wildcard character, it means infinity) would be claiming something impossible to know. As stated before, It is not my responsibility to work around an issue the Mozilla devs intentionally introduced, they could have chosen to treat a maxVersion of 3.0 as 3.0.* instead of loading that burden unto the extension authors.kriegaex wrote:When I update Firefox or Thunderbird, keyconfig often is the only add-on which does not work because of a compatibility check. This could be fixed easily by specifying something like 2.0.* as MaxVersion for TB and 3.0.* for FF.
Note that you should have been notified that "This update will cause some of your extensions and/or themes to stop working until they are updated." before you upgraded.
Sadly "minor version upgrade"s did far too often break extension, as did keyconfig not that long ago because Firefox 3.0.2 changed a "~10 year old behavior in a breaking way".kriegaex wrote:In the very improbable case of a minor version upgrade really interfering with keyconfig, [...]
On my list of things to consider. Note that keyconfig displays it currently in the same way as Firefox would in the menu.dubsey wrote:1. OK, as on Opera the hotkey for home page is Ctrl + SPACE . But on the current Keyconfig I'm using it does not say "SPACE" instead it says nothing at all as in "ctrl + " can this be fixed for the next version so that spacebar is shown
Assuming you meant the toolbar (as there should be a Tools > Keyconfig…), I've added this to my list, but with a low priority. You likely can create your own buttons with Custom Buttons or Custom Buttons².dubsey wrote:3. What about a nice little menu icon for Keyconfig, so that we can optionally access Keyconfig via the menu bar
My latest post regarding Mozilla Add-ons seems still to be valid (note the comment posted February 9, 2009 on the extension page). Even if all the issues would finally be completely gone, by now I'm wondering if the pain maintaining an entry over there would be worth it at all.dubsey wrote:4. Anything on publishing this highly useful on 'firefox addons' website and then using this thread for all development builds etc
Tools > Add-ons lists the version, context menu > About <extension> the author and contributors.dubsey wrote:5. Waht about a basic 'options' window where we can see addons version properly, as well as authour's name [...]
The wording is slightly off in keyconfig, a restart should be never necessary, some changes will only take effect on new windows (resetting a key, updating the key displayed in menu), simple editing should take effect immediately. Adding a button for this might be an overkill since I hope to remove any need for it in the future. Note that a button for this was supposed to be included in Firefox.dubsey wrote:[...] a menu option to 'restart firefox' with a confirm box
You should be able to assign those likejek60 wrote:[...] can I use keyconfig to map ctrl-a, ctrl-n, ctrl-b, ctrl-f, ctrl-n, ctrl-p, and ctrl-w to do the emacs action while in edit boxes?
Code: Select all
goDoCommand("cmd_charPrevious");
Code: Select all
goDoCommand("cmd_selectBeginLine"); goDoCommand("cmd_delete");
If you want to use the original shortcuts outside edit boxes, you could use something like:
Code: Select all
if(commandDispatcher.focusedElement instanceof Components.interfaces.nsIDOMNSEditableElement) {
goDoCommand("cmd_charNext");
} else {
gFindBar.onFindCommand();
}