Status

defect
P2
normal
RESOLVED WONTFIX
5 years ago
Last year

People

(Reporter: akratel, Unassigned)

Tracking

(Blocks 1 bug)

35 Branch
x86
macOS
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [console-papercuts][polish-backlog])

User Story

1) Collapsible groups ( bug 1088793 )

2) line numbers other than where console.log was called ( bug 814497 )
More specifically, in chrome, can use 
var getStackTrace = function() {
  var obj = {};
  Error.captureStackTrace(obj, getStackTrace);
  return obj.stack;
};
console.log(getStackTrace());
but this doesn't work in Firefox. Can use Error().stack but Firefox looses Object and function names.

3) inline-images or screenshots of what the page looked like when the log was created

4) buttons or controls like sliders that can have events attached

5) updatable graphs of performance or other data

6) log AJAX/XMLHttpRequests ( bug 972655 )

7) more text space to be able to write longer snippets of code in the console ( bug 972655 ) Some people use it to write small functions. 

8) Revisit how the console and network panel interact ( bug 861335 )

9) clickable/linkable URLs in console ( many, many bugs )

10) concise object representations in the console - we really need a holistic approach here across all tools for a unified object view. See react library. See https://ffdevtools.uservoice.com/admin/forums/246087-firefox-developer-tools-ideas/suggestions/6263603-concise-object-representations-in-the-console

11) Queuing of objects to be displayed in console causes asynchronous results ( bug 754861 )
i.e. if object attribute is changed in between log request and when it's displayed in console, display shows new object attribute, not the old one. 

11) Support tagging in Console logging: It's possible to use the original control object to create log messages and group them. However, an asynchronous event and its callbacks might log into the middle of another log group. This could be solved by tagging log messages and filter them in the console window. 

12) Display the correct __proto__ object in a prototype chain in the console

13) Show complete error messages - console currently does not provide a strack trace that is deep enough to link back to the error. For example when using JQuery, Chrome will provide the actual line of user code that caused the problem, whereas Firefox only provides the Jquery line where the error first occurred. For example: Example: TypeError: ev is undefined jquery-1.11.1.min.js line 2 > eval:217, in chrome, one would get the line where ev was not defined outside of the JQuery library. ( bug 814497 )

14) Remember the state of the "toggle split console" button. (popular Firebug feature.)


Will add more later.
Reporter

Description

5 years ago
This is a catch all digest for various minor console feature requests in User voice.
Reporter

Updated

5 years ago
User Story: (updated)
Updated this list with some related bug numbers.
User Story: (updated)
Reporter

Comment 2

5 years ago
Thanks!
Whiteboard: [console-papercuts][devedition-40]
Setting devedition-40 bugs to p3, filter on FB20EAC4-3FC3-48D9-B15F-0587C3987C25
Priority: -- → P3
Priority: P3 → P2
User Story: (updated)
> 3) inline-images or screenshots of what the page looked like when the log was created

If I understand this correctly it would be horrible for performances.
But a on demand API could be helpful.

> 4) buttons or controls like sliders that can have events attached

I don't get this one?

> 9) clickable/linkable URLs in console ( many, many bugs )

Any STR ? Simple stuff like `console.log("foo http://mozilla.org bar");` works

> 12) Display the correct __proto__ object in a prototype chain in the console

I thought we had a bug opened for this? It's not crystal clear what we should be displaying here.

> 14) Remember the state of the "toggle split console" button. (popular Firebug feature.)

Isn't it already the case? I can see the split console automatically being displayed if I close/reopen the toolbox and if I reboot firefox.
User Story: (updated)
Whiteboard: [console-papercuts][devedition-40] → [console-papercuts][polish-backlog]
Closing this one out so we only have to track these various features in a single meta bug. I've moved all bug #s from this bug to block bug 1111089.  Please file new bugs if any of the individual requests slipped through the cracks.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX

Updated

Last year
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.