914827 - conole.log does not work on webapprt

Status: RESOLVED WONTFIX

(Toolkit Graveyard :: Error Console, defect)

Description

[k]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0 (Beta/Release)
Build ID: 20130903162616

Steps to reproduce:

1. Install some webapp using ConsoleAPI (like console.log() function).
2. Run this app using `webapprt-stub -jsconsole1.
3. Type "console.log('test');' in 'Code' input and click "Evaluate".



Actual results:

Nothing is written to the console. 


Expected results:

Log messages should be printed to the console; both from application code and from evaluation input.

Comment 1

[k]

Can reproduce this bug on my custom build firefox (from mozilla-central).

Comment 2

[k]

jsconsole option of webapprt uses "old style" browser console. I did check that ConsoleAPI does not work in the same console (which can be run with ctrl+shift+j) in firefox 23.

This console is replaced by a new one (from devtools) in newer versions of firefox. New console does support ConsoleAPI. I belive that webapprt should also be changed to use this new browser console.

Comment 3

[k]

To clarify:

-jsconsole option still opens old conole in new versions of firefox. Only ctrl+shift+j (or "brower console" in "web tools") was changed.

Comment 4

[Marco Castelluccio [:marco]]

Is it possible to restore the old behavior and let the console API print in the error console?

Comment 5

[Brian Grinstead [:bgrins]]

The Error Console has been removed in favor of the Browser Console (see Bug 1278368), and the component is going to be removed.  If this bug is also relevant in the Browser Console, please reopen and move this into Firefox -> Developer Tools: Console.

Comment 6

[Zack Weinberg (:zwol)]

I am mass-reopening and re-componenting every single one of the Toolkit:Error Console bugs that appear to have been closed without anyone even *glancing* at whether they were relevant to the Browser Console.

If you want to close a whole bunch of old bugs -- FOR ANY REASON -- it is YOUR RESPONSIBILITY to check EVERY SINGLE ONE OF THEM and make sure they are no longer valid.  Do not push that work onto the bug reporters.

(It's okay to close bugs that haven't been touched in years when they don't have enough information for you to figure out whether the problem is still relevant to the current software - the reporter probably isn't coming back to clarify.  But that is the ONLY situation where it is okay.)

(I'm going to have to do this in two steps because of the way the "change several bugs at once" form works.  Apologies for the extra bugspam.)

Comment 7

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

webapprt has been removed, so it would seem this is no longer needed.