[Ext] Console² 0.1 to 0.3.6.2

[Litegod]

Focus on report doesn't seem to work. When I get errors on my page, the console does not automatically popup.

Please note that Focus on Report doesn't work after you closed the console. You'd rather have to keep it open in the background or in the sidebar.

Alright, then I think it would be a nice feature to be able to let the console automatically open and focus itself on report. What do you think?

[old zeniko]

Alright, then I think it would be a nice feature to be able to let the console automatically open and focus itself on report. What do you think?

It would indeed be a nice feature. Unfortunately it's pretty difficult to get right and not that trivial to code. I won't do it myself, but I'll happily accept patches.

[amitg]

For some reason this extension never worked for me. It always shows all errors - no matter which toggle buttons I have pressed or depressed. Specifically I wanted to to see ONLY JS errors because the DW coded HTML is full of CSS errors and my page under development produces several errors ever time I refresh. I have to go through all to find of only one or two JS errors that I am interested in. I don't care about CSS errors then.

[old zeniko]

For some reason this extension never worked for me.

Of course, it'd be nice if you could at least guess what the reasons might be:
* do you see any console2 related errors in the console?
-> please post them

* in case you use a non-standard theme: does this issue also happen with the default theme
-> please tell us which theme is responsible

* does this issue also happen on a clean profile?
-> please consider using a clean profile

* does this issue also happen when you disable all other extensions?
-> please tell us which extension you had to disable to get it working

I realize that it's not easy to debug tool you need to debug itself, but OTOH this extension is pretty well and extensively tested and I've never heard of the behavior you describe.

[amitg]

Found the problem. There is an extension called JS Console Extra 0.2 by Jordan Callicoat. That was causing this this problem. As soon as I disabled this extension, everything is fine. Here is about page

<img src="http://img149.imageshack.us/img149/5361/jsconsoleextra6si.jpg">

I searched the internet but could not find anyone reporting this problem and so had to post it here. Thanks for the help. This extension is awesome and I knew it has to work or else I would have found something about it somewhere. Didn't know where to start. Your questions gave me enough clues to get to bottom of it. Thanks again.

[Philip Chee]

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060704 MultiZilla/1.8.2.0i Mnenhy/0.7.4.0 SeaMonkey/1.5a

JS Error in latest SeaMonkey trunk:

Code: Select all

Error: _("ConsoleToolbarPalette") has no properties
Source file: chrome://console2/content/seamonkey-hack.xul
Line: 32

Additionally when in the SeaMonkey sidebar:

Code: Select all

Error: Component returned failure code: 0x80004003 (NS_ERROR_INVALID_POINTER) [nsIDOMXULElement.appendChild]
Source file: chrome://console2/content/seamonkey-hack.xul
Line: 45

Phil

[old zeniko]

@Phil: Could you please determine with which nightly this issue was introduced and venture an educated guess at which patch might be responsible (after having made sure that this doesn't happen on a clean profile)?

[Philip Chee]

Tested with ZIP builds on a fresh new profile.
Regressed between 2006063009 and 2006070110.

Bonsai Query

The only likey stuff (that I can see) are the changes to jasrray.c made by Igor. But I'm probably wrong.

Phil

[old zeniko]

@Phil: Thanks. The "culprit" is rather bug 282188 which (so far partially) implements Toolkit's toolbars for SeaMonkey. The latest <a href="http://www.haslo.ch/zeniko/software/console2-dev.xpi">testing version</a> (0.3.5.4+) should fix this issue (note that the Customize Toolbar dialog is currently missing).

[Philip Chee]

The "culprit" is rather bug 282188 which (so far partially) implements Toolkit's toolbars for SeaMonkey.

I'd never have guessed. Without looking at the .xbl, I don't see how it would have affected getElementById().

p.s. Now that SeaMonkey has renamed the menu item for the javascript console to "Error Console" there are now two of them. Could you change your label to "Console2" or "Error Console2"? Thanks muchly.

Phil

[Philip Chee]

Without looking at the .xbl, I don't see how it would have affected getElementById().

Oh wait, in Firefox, the startup code removes the "BrowserToolbarPalette" from the DOM. So this is generic to <toolbarpalette> not just the one in the main browser window.

[Edit] Argh. the DOM Inspector is borked on this trunk build so I can't check.

Phil

[old zeniko]

Now that SeaMonkey has renamed the menu item for the javascript console to "Error Console" there are now two of them.

I've respun the nightly to hide the menu item for SeaMonkey's own JavaScript/Error console. That's similar to what I do for Firefox/Thunderbird already and gets rid of an unneeded redundancy.

[Philip Chee]

Now that SeaMonkey has renamed the menu item for the javascript console to "Error Console" there are now two of them.

I've respun the nightly to hide the menu item for SeaMonkey's own JavaScript/Error console. That's similar to what I do for Firefox/Thunderbird already and gets rid of an unneeded redundancy.

Please don't do that. Multizilla does the same. Who's going to win? Multizilla's error console or Console2? Besides if either of these breaks it would be nice to have access to a working error console to see what was happening. Sometime back Multizilla's implementation of the error console broke (too many firefoxisms). Luckily I could still call up Console2 to see what was happening. This time the breakage in Console2 was merely cosmetic. What happens if I don't have access to *any* working error console at all?

Please reconsider. Besides the people who install Console2 are what I would think of as power users who wouldn't be confused by having an extra Console2 menuitem.

Phil (Please, Pretty Please, with sugar and cream and strawberries on top?)

[old zeniko]

You can always get the original JavaScript console back by either calling <code>toJavaScriptConsole();</code> (e.g. from a custom toolbar button, through keyconfig, etc.) or get the menu item back by adding the following to your userChrome.css:

Code: Select all

#toolsPopup > menuitem[oncommand="toJavaScriptConsole();"] {
   display: -moz-box !important;
}

I don't see normal users (which happen to be using this extension as well) need both consoles at the same time, and power users can always follow one of the two ways mentioned above...

[Philip Chee]

Code: Select all

#toolsPopup > menuitem[oncommand="toJavaScriptConsole();"] {
   display: -moz-box !important;
}

Ta. Phil