Created attachment 8807146 [details] Spectacle.J29290.png User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0 Build ID: 20161025164528 Steps to reproduce: when you get a JS error in the console, there's an arrow to toggle the backtrace. Unfortunately, the backtrace is in shown in a box with a fixed height, so you can never see the complete backtrace at one glance, but instead have to scroll through it, which is quite bad from a usability perspective. Actual results: See attached screenshot Expected results: The entire backtrace should be visible
It seems to be fixed in beta.
Thanks for reporting. Our new console frontend should enable you to see the entire trace when expanding it. That UI is currently enabled on nightly and we have Bug 1308219 opened for proceeding to other channels. Because it's just a matter of time before we change to this new UI, this isn't likely to get fixed in the current one. One thing that would be very helpful is if you could confirm that the trace UI is working how you'd like it to in a Nightly build.
Status: UNCONFIRMED → NEW
Depends on: 1308219
Ever confirmed: true
Priority: -- → P3
Summary: backtrace in console is not entirely visible → backtrace in console is not entirely visible (in 'old' console frontend)
(In reply to Brian Grinstead [:bgrins] from comment #3) > One thing that would be very helpful is if you could confirm that the trace > UI is working how you'd like it to in a Nightly build. I've tried the nightly now and it definitely much better now. Just two small remarks: - the line-height could be increased, right now the individual lines are very close together. They were a bit further apart in the old version - I don't really understand why there are two numbers at the end of each filename. I'm guessing that one of them is they line number in the file (but I'm not sure which one), but what is the other one supposed to be, the column number or something? I've attached a screenshot with what how it looks for me on Mac OS
You need to log in before you can comment on or make changes to this bug.