Closed Bug 1363682 Opened 7 years ago Closed 2 years ago

Connect each Message component

Categories

(DevTools :: Console, task, P3)

Product:
DevTools
Component:
Console
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: nchevobbe, Unassigned)

References

Details

(Whiteboard: [newconsole-reserve]) 

At the moment we only connect the ConsoleOutput component, which is then responsible of creating all the messages and handling the updates.
The ConsoleOutput component could only iterate through an array of visible message ids and create the Message component with only the messageId as a prop.
Then, each Message component could be connected and responsible for getting all the message properties.

This could mean that we kill the MessageContainer component and do things differently.
Depends on: 1363678
Priority: -- → P2
Whiteboard: [console-html]
Flags: qe-verify?
Flags: qe-verify? → qe-verify-
Assignee: nobody → odvarko
Status: NEW → ASSIGNED
Iteration: --- → 55.6 - May 29
Priority: P2 → P1
Iteration: 55.6 - May 29 → 55.7 - Jun 12
Iteration: 55.7 - Jun 12 → 56.1 - Jun 26
Iteration: 56.1 - Jun 26 → 56.2 - Jul 10
Iteration: 56.2 - Jul 10 → 56.3 - Jul 24
Assignee: odvarko → nobody
Status: ASSIGNED → NEW
Iteration: 56.3 - Jul 24 → ---
Priority: P1 → P2
Priority: P2 → P3
Whiteboard: [console-html] → [reserve-console-html]
Priority: P3 → P4
Flags: qe-verify-
Priority: P4 → P2
Whiteboard: [reserve-console-html] → [newconsole-mvp]
Priority: P2 → P3
Whiteboard: [newconsole-mvp] → [newconsole-reserve]
Product: Firefox → DevTools
Type: enhancement → task

With the work on console performance, I don't think we'll do this
Furthermore, having multiple connected components could lead to performance issue (we have such experience in the debugger)

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.