Firebug support for script debugging

Old Firebug ticket about this topic: http://code.google.com/p/fbug/issues/detail?id=83

Related FB thread: http://groups.google.com/group/firebug/browse_thread/thread/5edb8f0...

(from [298f0087d1f531476b5c5977bb743dfc8a1c167b]) New (FF3.5+ only) injection logic, Firebug debugger support [#13 Firebug support for script debugging state:resolved]

This is a pretty important commit that has impact on several aspects of WM.
The original goal was to allow script developers to debug their script using Firebug's debugger [1].
In order to allow this, a new injection logic has been put in place, taking into profit new FF3.5+ evalInSandbox() features [2].
As a consequence:

- support for FF<3.5 is removed
- scripts are no longer wrapped into an anonymous function
- the @unwrap tag thus is deprecated

As a side note, this commit also paves the way for a coming @jsVersion header tag.

[1] #13 Firebug support for script debugging [2] https://developer.mozilla.org/en/Components.utils.evalInSandbox#Opt... http://github.com/ocornu/webmonkey/commit/298f0087d1f531476b5c5977b...

what are the steps in firebug to find the display object properties of a web page. I have several link buttons that i need to macro