Just cross posting issue reports: http://code.google.com/p/fbug/issues/detail?id=5812 http://code.google.com/p/fbug/issues/detail?id=5813
Honza On Aug 15, 12:21 pm, Jan Honza Odvarko <[email protected]> wrote: > Good point. > > I like the ideas, please create a new issue report for this so, > it isn't forgottenhttp://code.google.com/p/fbug/issues/list > > We can discuss further underneath of the bug report > > Thanks for the tips! > > Honza > > On Aug 15, 12:14 pm, Markus Staab <[email protected]> wrote: > > > > > > > > > maybe also the "breakpoint"-panel could show for each breakpoint a link to > > the function in which it was set (so we have an anchor for the context menu > > to activate "Log Function Calls". > > > Am Mittwoch, 15. August 2012 12:12:25 UTC+2 schrieb Markus Staab: > > > > in javascript we use anonymous functions in a lot of places. at the moment > > > it seems to be not possible to activate the "Log Function Calls" option > > > for > > > those anonymous functions. > > > > The problem actually is, that nowhere is a link to the function object, so > > > one can open the context menu. > > > There it would be nice to have an expression in either the watch or > > > stack-panel (or both?) which represents the funtion in which the current > > > breakpoints resides. -- You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at https://groups.google.com/forum/#!forum/firebug
