1363066 - Unable to collapse console.error message in console (old frontend)

Status: RESOLVED INVALID

(DevTools :: Console, defect, P3)

Description

[heathbo1]

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:54.0) Gecko/20100101 Firefox/54.0
Build ID: 20170418004027

Steps to reproduce:

Go to Developer Tools/Console.  Make sure Logging/Errors is checked.  Go to any website that logs an error.


Actual results:

Logged Error shows up in console.  Collapse triangle is closed but the content of the error is displayed.  Clicking the Collapse triangle has no effect.


Expected results:

Clicking the collapse triangle should should hide or show logged content.

Comment 1

[Brian Grinstead [:bgrins]]

Attachment: error-collapse.gif

Is there a particular page you can reproduce this on?  When testing locally I'm able to expand and collapse an error.

Here's a URL where I see the expand/collapse working: data:text/html,<script>console.error('test')</script>

Comment 2

[heathbo1]

The error is an "Unable to parse service response" error.
Nothing shows when I open the carrot.
All I have is a very big "Stack trace" under it.

Comment 3

[Brian Grinstead [:bgrins]]

(In reply to heathbo1 from comment #2)
> The error is an "Unable to parse service response" error.
> Nothing shows when I open the carrot.
> All I have is a very big "Stack trace" under it.

Can you please upload a screenshot?

Comment 4

[heathbo1]

Attachment: Screen shot of Stack trace error

Comment 5

[Brian Grinstead [:bgrins]]

OK, it looks like maybe console.error is being called with an Error object as a parameter instead of a string (which is what causes the stack to show up by default).  I believe if it the code was doing something like console.error("Unable to parse service response") instead of console.error(new Error("Unable to parse service response")), it might give you nicer looking output where the stack trace is only visible after expanding.  However, even with an Error as an argument the arrow should be opening up a more detailed view of the stack trace.

Comment 6

[Nicolas Chevobbe [:nchevobbe]]

Let's close it since there was significant work around error stacktrace lately