I'm not quite sure if this issue is intended to describe an existing or prior 
bug or if it's a feature request.

However, using ChromeDevTools 3.4 with Chrome 18.0.1025.168 and Eclipse 3.7 
using WIP 1.0, I DO NOT see browser console messages echoed to the Eclipse 
console.  (I wish I did, in fact.)

When the debugger is enabled, it's impossible to see browser console output 
anywhere, as enabling Web Inspector in Chrome disables the remote debugger, at 
present.  I would love to either see the browser console echoed to a console 
session in Eclipse, or be able to use Web Inspector while debugging.

As a very hacky work around, I wrote an Eclipse plugin that launches a 
WebSocket server and echoes anything sent to it to the Eclipse console, along 
with a Javascript include that instruments console.log to effect the 
redirection.  To display filenames and lineNo in the eclipse console, I sadly 
have to parse a stack trace from a new Error in the javascript, which just 
feels slow and dirty, and the instrumented console.log, of course, now doesn't 
display the proper filename or lineNo when displayed in the native Web 
Inspector, as they're masked by the new console.log functions location.  And, I 
hate having to inject a stupid websocket-remote-console.js file into any page I 
want to debug.  I would much rather the ChromeDevTools allow for console 
viewing inherently.

And if I were to get all my wishes, an Eclipse "remote browser console" would 
be a REPL, executing any commands given in the browser page context, and 
clicking on any console message would jump, locally in Eclipse, to the source 
line that triggered it. 

Failing that, if the debugger allowed concurrent access to a page on the chrome 
debugging port, then we could easily just have the Eclipse internal browser 
point to the debugging port and show the Web Inspector in all it's REPL-ly 
goodness. 

So, if this Issue is meant to be a feature request for "browser console echoed 
to eclipse console," I second it.  If, rather, it's claiming a bug that the 
browser console IS echoed to the eclipse console, then it's sadly been fixed 
already.

Original comment by sejm...@gmail.com on 2 May 2012 at 4:51

console.log writes to eclipse console #43

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions