Closed Bug 230150 Opened 21 years ago Closed 15 years ago

Need a way to open a Sun Java Console on Firefox

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
minor

Tracking

()

RESOLVED WONTFIX

People

(Reporter: shankarunni, Unassigned)

References

Details

(Whiteboard: [WontFix'ed after bug 485984])

Attachments

(1 obsolete file)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031228 Firebird/0.7+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031228 Firebird/0.7+

Mozilla has a menu item to open the Sun Java Console (under Tools/Web
Development), that Firebird doesn't have. In fact, I haven't found any menu item
in FB to open the Sun Java Console.

There's no way to see debug output from an applet in Firebird, which usually
gets written to the Sun Java console. Can't open a file and write to it because
applets generally don't have permissions for this.


Reproducible: Always

Steps to Reproduce:
N/A. There's no menu item to open a Sun Java Console.

Actual Results:  
N/A.

Expected Results:  
A menu item under Tools, somewhere, to open the Sun Java Console.
This menu item might be useful in the developer tools extension, not a core
function though.  Confirming, adding to block the extension bundles bug so it
gets considered.
Blocks: 214269
Status: UNCONFIRMED → NEW
Ever confirmed: true
> might be useful in the developer tools extension..

Agree. Thanks.
Severity: major → minor
Is there a way to open a bug against the Developer Tools extension, and have it
be "major" there?  This is really quite important, and its absence will hurt
Java app testing on FB.
In my opinion Java console is mandatory, because I have no way to tell customers
to install something more to tell me what went wrong with the applet.

The fact is that Java (or java script for taht matter) console is not just a
development tool it is also a easy way to ask error reports. After all the most
errors that need the loging hapen to customers, because I simply can't test all
the billions of billions possible data configurations by my self. So if
something goes wrong I need to say try some other browser because you don't want
to install this and that so that you can report the errors to me.
For those that need a way around I just found out a trick that works for me.

Just point your browser to the following html and right mouse brings menu, from
which one can left click to open the java console.

i_want_java_console.html-------
<html>
<head>
</head>
<body>
<embed width="200" height="300"
code="ThisClassDoesNotExist.class"
type="application/x-java-applet"
codebase="../classes/"
</embed>
</body>
</html>
end of code-----
Summary: Need a way to open a Sun Java Console on Firebird → Need a way to open a Sun Java Console on Firefox
By the way, there *is* a "Show Java Console" extension on the Extensions
website, but it hasn't been updated since version 0.1. I had to hack its RDF to
get it to load on FF 1.0, but it works just fine.

Perhaps it can be pulled in to the Developer Tools component of the standard
installer?
*** Bug 290426 has been marked as a duplicate of this bug. ***
Assignee: bross2 → nobody
QA Contact: general
another way to open java console is to type/paste in javascript console on 1 line:

Components.classes['@mozilla.org/oji/jvm-mgr;1'].getService(Components.interfaces.nsIJVMManager).showJavaConsole();
There's an extension for this, as mentioned previously, and given that this really is only useful to applet developers out there, and adds no value to normal users I personally don't think we should add this back to the default UI.
it is also useful for users diagnozing applet problems, e.g. get the stack after an exception
Absolutely, but there's other ways users who want to do that can open the Java console. On Win32 you can get to it through the task bar and through the control panel, and on *nix you can run the java console app and enable the console, and I'm sure there's a way to do the same on the mac as well. So that IMO is not reason enough to ship it in the Firefox default UI.
(In reply to comment #12)
> [..] but there's other ways users who want to do that can open the Java console. 

But from the point of view of the user's interaction with the browser - this is one situation where parity with IE is a "good thing". IE provides a "Sun Java Console" menu item (added by the Sun Java VM installation, BTW). 

If there was a way for Java to add such a menu item to FF via some sort of FF registry or extension mechanism, we could push the responsibility for this to the Java packagers.

(And what do you know - we *do* have a mechanism like that - extensions. So really, we're talking about writing an extension to add such a menu item, that can be packaged with Java and installed. So is this an evangelism issue, then? 

Also, you *could* argue that we should have a "standard extension" (like the DOM inspector) that we could package with FF itself, if we can't get enough attention from Sun for this..)
I'm not sure how this bug is going to get handled, but the technical lead commented on how instancing the java console is going to get handled in the future in the following bug: https://bugzilla.mozilla.org/show_bug.cgi?id=460244
Comment on attachment 290669 [details] [diff] [review]
java console patch. needs localization


This code would only work on m-1.9.1, as bug 485984 removed OJI after that.
Attachment #290669 - Attachment is obsolete: true
R.WontFix, per comment 14 and comment 15.
Status: NEW → RESOLVED
Closed: 15 years ago
Depends on: 485984
Resolution: --- → WONTFIX
Whiteboard: [WontFix'ed after bug 485984]
Version: unspecified → Trunk
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: