[Ext] Console² 0.1 to 0.3.6.2
- onemen
- Posts: 1136
- Joined: October 15th, 2004, 7:48 am
-
- Posts: 0
- Joined: December 31st, 1969, 5:00 pm
Just another minor update: <a href="http://www.haslo.ch/zeniko/software/console2-dev.xpi">Console² v0.1.8.1+</a>. Allows you to remove single items (until you reopen the console). This might come in handy if you've got a single overlong item which pushes the line numbers out of sight - select, [Del] (or right-click -> Delete) and go on debugging... Additionally, the official way for copying all items is now Select All 'n' Copy ([Ctrl]+[A], [Ctrl]+[C]).
-
- Posts: 26
- Joined: May 18th, 2003, 12:39 am
- Location: Sweden
The access key for "Chrome" is hardcoded on line 80 in console2.xul:
Code: Select all
<menuitem type="radio" group="ctx" accesskey="h" observes="Console:modeCtxChrome"/>
-
- Posts: 275
- Joined: January 17th, 2005, 4:33 pm
zeniko wrote:A side effect of this extension is thus that you'll get page up/down and FAYT support in the Downloads and Extensions managers (see also <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=298993">bug 298993</a>). Please report any problems probably related to this, too.
0.1.8.1+ seems to make it impossible to uninstall an extension. i can disable, but trying to uninstall any extension results in the usual "loss of functionality" warning and no "will be uninstalled" message in the extension manager.
Returning to 0.1.8 fixes the issue. Otherwise a fantastic effort. Already missing FAYT in the EM.
rtk
-
- Posts: 0
- Joined: December 31st, 1969, 5:00 pm
<a href="http://www.haslo.ch/zeniko/software/console2.xpi">Console² v0.2</a> is a minor improvement for you (multiple selection, message deletion) but a big step towards a possible integration of the single patches into the trunk (the code resembles now pretty closely the original console's).
In case you want to take advantage of the improved richlistbox (FAYT for free), you'll have to edit the file chrome.manifest in the extensions installation directory - just remove the two comment signs at the bottom. If you wish, I can reenable it globally in the next release, since it's working pretty stable now (fixed the bug mentioned by rtk and some more; testing with the Extensions and Downloads managers showed no real difference - except for the improvements).
@Hasse: Fixed that. Thanks.
In case you want to take advantage of the improved richlistbox (FAYT for free), you'll have to edit the file chrome.manifest in the extensions installation directory - just remove the two comment signs at the bottom. If you wish, I can reenable it globally in the next release, since it's working pretty stable now (fixed the bug mentioned by rtk and some more; testing with the Extensions and Downloads managers showed no real difference - except for the improvements).
@Hasse: Fixed that. Thanks.
- wgianopoulos
- Posts: 1746
- Joined: July 23rd, 2003, 8:15 am
- wgianopoulos
- Posts: 1746
- Joined: July 23rd, 2003, 8:15 am
It is only necessary to disable console2 to restore the ability to uninstall extensions.
With console2 installed I get the following JavaScript errors when I try to uninstall.
Error: uncaught exception: [Exception... "Could not convert JavaScript argument arg 0 [nsIConsoleService.unregisterListener]" nsresult: "0x80570009 (NS_ERROR_XPC_BAD_CONVERT_JS)" location: "JS frame :: chrome://console2/content/console2.xml :: :: line 415" data: no]
----------
Error: gExtensionsView.goDown is not a function
Source file: chrome://mozapps/content/extensions/extensions.js
Line: 1028
Without console2 I get no errors.
This is all with this
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051002 Firefox/1.6a1
build.
With console2 installed I get the following JavaScript errors when I try to uninstall.
Error: uncaught exception: [Exception... "Could not convert JavaScript argument arg 0 [nsIConsoleService.unregisterListener]" nsresult: "0x80570009 (NS_ERROR_XPC_BAD_CONVERT_JS)" location: "JS frame :: chrome://console2/content/console2.xml :: :: line 415" data: no]
----------
Error: gExtensionsView.goDown is not a function
Source file: chrome://mozapps/content/extensions/extensions.js
Line: 1028
Without console2 I get no errors.
This is all with this
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051002 Firefox/1.6a1
build.
- wgianopoulos
- Posts: 1746
- Joined: July 23rd, 2003, 8:15 am
-
- Posts: 2777
- Joined: November 7th, 2002, 1:00 am
- Location: Japan
- Contact:
I've absolutely no problems uninstalling an extension with Console2 v.02.
I do often see warnings and errors, such as this one:
But I don't think these are related to this extension.
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a1) Gecko/20051002 Firefox/1.6a1 ID:2005100207
I do often see warnings and errors, such as this one:
Code: Select all
Error: document.getElementById("sanitizeItem") has no properties
Source file: chrome://browser/content/browser.js
Line: 1117
But I don't think these are related to this extension.
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a1) Gecko/20051002 Firefox/1.6a1 ID:2005100207
-
- Posts: 0
- Joined: December 31st, 1969, 5:00 pm
Again a nightly for those who want to use the new richlistbox: <a href="http://www.haslo.ch/zeniko/software/console2-dev.xpi">Console² v0.2.0.1+</a>. Hardly any new stuff, but fixes and work-arounds for some more listbox and richlistbox bugs (where the actual patches most probably won't make it into Firefox 1.5).
As for the warnings you see on trunk builds, these are due to ongoing development. As far as I can see, there is no serious work going on in any part related to Console². You might want to stick to branch nightlies for a while, if these errors bother you (there are hardly any strict warnings left on the branch, and just occasional uncaught exceptions which might just as well be caused by extension incompatibilites).
As for the warnings you see on trunk builds, these are due to ongoing development. As far as I can see, there is no serious work going on in any part related to Console². You might want to stick to branch nightlies for a while, if these errors bother you (there are hardly any strict warnings left on the branch, and just occasional uncaught exceptions which might just as well be caused by extension incompatibilites).
-
- Posts: 756
- Joined: May 15th, 2005, 2:31 am
I installed v2.0 from extensionsmirror.nl and got the normal entry in the EM, and one that says "Console2_0.1.8.xpi", which I cannot remove even after uninstalling the extension.
Edit: I am on Firefox 1.5 beta2 on Windows XP SP2
Edit: I am on Firefox 1.5 beta2 on Windows XP SP2
Linkify bug numbers - test: bug 258287
- mrtech
- Posts: 2007
- Joined: May 15th, 2003, 7:46 am
- Location: New York
- Contact:
-
- Posts: 756
- Joined: May 15th, 2005, 2:31 am
I tried renaming it and it doesn't work. Could you post a link to the bug?
Linkify bug numbers - test: bug 258287
- onemen
- Posts: 1136
- Joined: October 15th, 2004, 7:48 am
-
- Posts: 0
- Joined: December 31st, 1969, 5:00 pm
Another detail fixed: <a href="http://www.haslo.ch/zeniko/software/console2-dev.xpi">Console² v0.2.0.3+</a> should move the focus outline to the toolbar only when tabbing through. Seems to be quite an elegant solution to the accessibility issues.
@pile0nades: If it doesn't hurt, just move it down and ignore it . Maybe starting Firefox in Safe-mode allows you to get rid of it. Otherwise - if you dare - you can uninstall the extension and then edit all entries related to it out of the extensions.* files in your profile directory (make a backup first, use your favorite text editor and try not to mess around too much with the RDF file). If that's too risky, search this forum for help (I'm pretty sure I've seen this problem mentioned already) or start a new thread...
@pile0nades: If it doesn't hurt, just move it down and ignore it . Maybe starting Firefox in Safe-mode allows you to get rid of it. Otherwise - if you dare - you can uninstall the extension and then edit all entries related to it out of the extensions.* files in your profile directory (make a backup first, use your favorite text editor and try not to mess around too much with the RDF file). If that's too risky, search this forum for help (I'm pretty sure I've seen this problem mentioned already) or start a new thread...