Michael Rennie

This one kind of goes hand-in-hand with issue #25, but when I was last fixing a bug I recall that we have odd dependencies across the source - for example...

We should investigate using Socket.io for comms, it has support for everything we could ever want, it just looks like it is more geared towards Node.js, but perhaps there is...

We should be using require.js to control the loading of tools and other optional code

Currently for all of our commands that allow you you to ask for some or all of some information held in Crossfire (getBreakpoints, getTools, etc) we preface the command with...

DOM tool is not ever unregistered from the window document

1

CF 0.3a11 + FB 1.10 + FF 12 When the DOM to is registered to attaches itself to window.document. When you disconnect the client and the tool is unregistered it...

This is a clone of the issue 4464 from the Firebug issue tracker: http://code.google.com/p/fbug/issues/detail?id=4464

This is a clone of issue 4409 from the Firebug issue tracker: http://code.google.com/p/fbug/issues/detail?id=4409

Clone of issue 4462 from the Firebug issue tracker: http://code.google.com/p/fbug/issues/detail?id=4462

This is a clone of issue 3357 from the Firebug issue tracker: http://code.google.com/p/fbug/issues/detail?id=3357

Crossfire will need to be modified to support the WebSockets handshake protocol if we want to work with WebSockets. http://en.wikipedia.org/wiki/WebSockets#WebSocket_Protocol_Handshake State of websocket support for FF4: https://bugzilla.mozilla.org/show_bug.cgi?id=616733 Some useful references:...