I was waiting until it came out of beta. (I have enough difficulty
with my own code! :-) ). However, I just tried 1.3 beta 5, and
console.trace() worked there-- except when I called it from code
loaded by a frame. (Even in that case, it did output a trace, but not
a trace that had anything to do with my code.) I'll make a test case
for that if I get a chance.
But thanks-- there is at least a very helpful partial fix in 1.3!
--Paul
On Dec 10, 1:01 pm, John J Barton <[EMAIL PROTECTED]> wrote:
> The test case in SVN under /tests/issues/issue796.html works for me on
> Firebug 1.4.0a9.
>
> Are you running 1.3?
>
> jjb
>
> Paul Lynch wrote:
> > Hi,
> > I was wondering if someone knows whether issue 796 (http://
> > code.google.com/p/fbug/issues/detail?id=796) is going to be fixed
> > soon, or is waiting for a better test case. The last entry is
> > September. I have never seen console.trace() work, and it sure would
> > be a helpful feature when debugging my code.
> > --Paul
--~--~---------~--~----~------------~-------~--~----~
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
http://groups.google.com/group/firebug?hl=en
-~----------~----~----~----~------~----~------~--~---
