Archives For console

>”Heads Up Display” status:

Console work (bug 534398): Removed all /browser/ aspects of this patch. Asked Vlad for first-pass review.

I am sure it still needs some “distilling”, etc.

Filed more bugs to block the tracking bug 529086
Created a JS sandbox/interpreter interface. This seems to be an EARLY mock up of “JS Workspaces” as Mr. robcee likes to call them.

Actually got some key bindings working on the input textbox: ctrl-a, ctrl-e, and to some extent “history” (up arrow, down arrow)

All code is checked into user repo:

Began working on implementation of HTTP traffic observation and understanding of how “Load Groups” work. (thanks Mossop)
Latest screen grab is here, again this is with zero thinking/commiseration about UI (with UX team), etc…:

Try build is cooking this evening, will update when it is finished. Here they are:

We grilled Fajitas on Thursday at work, OH YEAH!


Answer first pass review with code and comments, keep on working on HTTP observation, console JS evaluation.

> The current console patches are found on bug 545266 and bug 546708 – also try builds will start once things are actually usable – I hope end of next week. It turns out that trying to attach (and keep attached) an arbitrary object on a nsIDOMWindow is a it of a pain – from outside the window’s constructor. sicking told me about his patch for detecting new windows (before content scripts run) and attaching objects to them: bug 549539 – which landed late today. Yay. With this patch on trunk it should be trivial now to detect window construction and attach a console.


Work with the new window detection hooks to implement the observer that keeps window consoles re-appearing. Every load of the browser creates a new nsIDOMWindow – news to me, anyway.


I may need some initial “WIP CSS” help to pretty up the logging output. I’ll try my hand at it next week after I have gotten the initial event handling worked out.