Closed
Bug 778766
(console-output)
Opened 12 years ago
Closed 6 years ago
[meta] Web Console output work
Categories
(DevTools :: Console, defect, P3)
DevTools
Console
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: msucan, Unassigned)
References
(Depends on 9 open bugs, )
Details
(Keywords: meta, Whiteboard: [status:inflight])
We want to be able to fix bug 706755 and bug 775607. We want to make it easier to add new message types and to customize the existing messages in the Web Console output. Since the last output rewrite in bug 605621, the output implementation has become harder to manage and easy to break (prone to regressions).
A rewrite is in order with the aforementioned goals. We also need to make sure that we improve message filtering performance and that we make it less confusing how filtering, categories and severities work.
This bug will only change the implementation while keeping user experience changes to a minimum. We need to be able to easily track potential regressions. The rest of the work will happen in separate bugs.
Other related bugs: bug 628019, bug 637604 and 617698.
Comment 1•12 years ago
|
||
I think this bug relates to bug 673891.
Reporter | ||
Comment 2•12 years ago
|
||
Ohzeki: you are correct. Thanks for your find! I missed that bug.
What I am working on will allow easy lookup of nodes within a message, but instead of using XBL, messages will be represented by JS objects.
Updated•12 years ago
|
Alias: console-output
Reporter | ||
Comment 3•12 years ago
|
||
We have started work on fixing this bug. Actual patches will be submitted in specific bugs.
The plan is here: https://gist.github.com/mihaisucan/5399023
Feedback is welcome. Thank you!
Summary: Web Console output rewrite → [meta] Web Console output rewrite
Reporter | ||
Updated•11 years ago
|
Reporter | ||
Updated•11 years ago
|
Reporter | ||
Updated•11 years ago
|
Reporter | ||
Updated•11 years ago
|
Reporter | ||
Updated•11 years ago
|
Comment 5•10 years ago
|
||
aiui, most of the important stuff has been taken care of. Do we still want to complete the remaining dependent bugs or can we close this meta bug and consider it "completed"?
Whiteboard: [status:inflight]
Reporter | ||
Comment 6•10 years ago
|
||
(In reply to Rob Campbell [:rc] (:robcee) from comment #5)
> aiui, most of the important stuff has been taken care of. Do we still want
> to complete the remaining dependent bugs or can we close this meta bug and
> consider it "completed"?
Indeed, the most important bugs are fixed. However this meta bug continues to be useful for me, to keep track of console output work. Maybe rename the bug?
Updated•10 years ago
|
Summary: [meta] Web Console output rewrite → [meta] Web Console output work
Updated•10 years ago
|
Assignee: mihai.sucan → nobody
Status: ASSIGNED → NEW
Updated•8 years ago
|
Priority: P1 → P3
Updated•6 years ago
|
Product: Firefox → DevTools
Comment 7•6 years ago
|
||
This was about old console, we can close this
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•