Thanks for the response. I was actually making errors in two places, both
with the <=. I think my other question of how can I turn off this stack
trace still applies. Like I said, I'm using ba-debug and am quite happy with
it's dealings with the console. What was causing me a great deal of
confusion was the error message in Firebug before the traditional console
error, which from what my co-worker well versed in Java tells me is the
stack trace. I was expecting this:
chart.series[0] is undefined
[Break On This Error] chart.series[0].remove(false); ChartBase.js (line
172)
Turns out this is the second error message I see.
What is/was confusing me was this:
Communication with the server failed: TypeError: chart.series[0] is
undefined
console.error(message); t5-con...uery.js (line 64)
Ajax failure: Status 200 for #{request.url}: TypeError: chart.series[0] is
undefined
t5-con...uery.js (line 56)
In the JS world as far as I was thinking, the AJAX is done, as we have
already received data (success). Why am I getting an AJAX error? In the
single threaded JS world, there's usually some causality between the first
error and a second error, so I concentrated on the first error I saw.
Can you explain why there was a log output added like this? The stack trace
is really throwing my debugging off. Can it be turned off at all? Going
forward, I'll just ignore the first message and concentrate on the error
with the line number that one usually sees without the Tapestry console log
if it can't be.
Much appreciated.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Problems-with-console-log-tp5121207p5121484.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
