584672 - JSTerm evaluation output needs truncation

Status: RESOLVED FIXED

(DevTools :: Console, defect)

Description

[Mihai Sucan [:msucan]]

Attachment: screenshot

At the moment, the result of the evaluation of any expression is not truncated, which can lead to really big results being displayed in the WebConsole output. We need to limit the output for each result.

To reproduce:

- Open www.robodesign.ro
- Open the WebConsole
- Type in the input: wf2_datalist
- Press Enter.

Expected result: I see a line or two from the wf2_datalist function source.

Actual result: The entire function source code is displayed.

I attached a screenshot to show how the result is displayed.

Comment 1

[Colby Russell :crussell (no longer Mozilla-ing)]

Sucks if you actually want to see the full output instead of the cauterized form, though.

Comment 2

[Mihai Sucan [:msucan]]

(In reply to comment #1)
> Sucks if you actually want to see the full output instead of the cauterized
> form, though.

True, but for that there's bug 573103. Once that is done, I presume we will be able to click on evaluation results to see the complete output if we desire.

Comment 3

[Dietrich Ayala (:dietrich)]

This is not a blocker - doesn't break or regress primary browser features.

I'm also not convinced truncation is desirable. I'd prefer immediate access to the output and scrolling through it, over truncation and having to click to see.

Comment 4

[David Dahl :ddahl]

(In reply to comment #3)
> This is not a blocker - doesn't break or regress primary browser features.
> 
> I'm also not convinced truncation is desirable. I'd prefer immediate access to
> the output and scrolling through it, over truncation and having to click to
> see.

Agreed, however, it may eventually be something that is confugrable, as some JSD objects will no doubt be immense. Back burner for sure.

Comment 5

[David Dahl :ddahl]

This bug makes me think we need pretty printed JS outputted to the console more than truncation - although truncation is a good idea if used via a pref.

Comment 7

[Sonny Piers [:sonny]]

This is likely to be fixed by inline object inspection.
However might still be a problem for strings such as document.body.innerHTML

Comment 8

[Mihai Sucan [:msucan]]

After a loong time. :)