1121737 - -jsconsole flag should open new Browser Console

Status: RESOLVED WONTFIX

(Firefox Graveyard :: Webapp Runtime, defect, P3)

Description

[(not reading bugmail) Nick Desaulniers [:\n]]

OSX 10.8.5.  After building (mach build) with a modified webapprt/content/webapp.js and webapprt/content/webapp.xul, then installing a packaged app (outlook.com), the changes are reflected in the xul but not the JS file.  I can see my changes to webapp.js in my objdir, but even dump statements or syntax errors don't log anything in the installed application.  I've tried uninstalling and reinstalling the app every time between builds, clobber builds, `rm -rf ~/Library/Caches/outlookcom-95fdd31e7961793317aad4f0ccc43faf`, `rm -rf ~/Library/Application\ Support/outlookcom-95fdd31e7961793317aad4f0ccc43faf`.

Myk has confirmed.

Comment 1

[(not reading bugmail) Nick Desaulniers [:\n]]

I've also tried uninstalling all of my versions of FF and still saw this.

Comment 2

[(not reading bugmail) Nick Desaulniers [:\n]]

Also, does not seem to make a difference for freshly installed apps (mykzilla) or hosted (mykzilla).

Comment 3

[(not reading bugmail) Nick Desaulniers [:\n]]

seems like if you run the app from the command line with `-debug <port number>` then you can connect dev tools from another running process of FF and see console.log and Cu.reportError, but not dump.

Comment 4

[Marco Castelluccio [:marco]]

This might be related to bug 988062. Have you tried clearing the cache and the profile before reinstalling the app?

Comment 5

[Myk Melez [:myk] [@mykmelez]]

I just helped \n troubleshoot, and actually the changes are being reflected, but console.log and Cu.reportError calls aren't being logged to the Error Console (which opens when you pass the -jsconsole flag), nor are dump calls being written to stdout.  So the various logging statements that \n added to webapp.js appeared not to be reflected, although they actually were.

I'm unsure about dump, but some investigation with the -debug flag and remote developer tools reveals that console.log and Cu.reportError are writing to the Browser Console.  And passing -jsconsole to Firefox opens the Browser Console.

So the issue here is probably that the Error Console is broken now that Firefox has made -jsconsole open the Browser Console, and the runtime should open the Browser Console too in that case.

(Unsure about dump, that may be a different issue.)

Comment 6

[Myk Melez [:myk] [@mykmelez]]

Per bug 1238079, we're going to disable the desktop web runtime and remove it from the codebase, so we won't fix these bugs in it.