Open Bug 1570602 Opened 5 years ago Updated 2 years ago

Create a DAMP test to track the performance of highlighters

Categories

(DevTools :: Inspector, task, P3)

Product:
DevTools
Component:
Inspector
Type:
task

Tracking

(Fission Milestone:Future)

Project Flags:
Fission Milestone Future

People

(Reporter: pbro, Unassigned)

References

(Blocks 2 open bugs)

Details

(Whiteboard: dt-fission-future)

We currently do not track the performance of our highlighters. This means we do not know if/when highlighters take longer to get displayed after the user has hovered on a node in the markup-view for example.
This is very common use case that happens a lot, and we would want that to be instant, so that users have immediate feedback for the node they are currently inspecting.

Especially with Fission coming soon and changing the way we deal with highlighters, we might want to know if performance in this area regresses.

So this bug is to track the creation of this test.

Blocks: dt-fission-inspector
Whiteboard: dt-fission
Priority: P3 → P2
Assignee: nobody → rcaliman
Status: NEW → ASSIGNED
Priority: P2 → P1
Whiteboard: dt-fission → dt-fission-reserve

Tracking Fission DevTools bugs for Fission Nightly (M6)

Fission Milestone: --- → M6
Assignee: rcaliman → nobody
Status: ASSIGNED → NEW
Priority: P1 → P3

dt-fission-reserve bugs do not need to block Fission Nightly (M6).

Fission Milestone: M6 → ---

Tracking dt-fission-reserve bugs for Fission MVP until we know whether they really need to block Fission or not.

Fission Milestone: --- → MVP

Moving old "dt-fission-reserve" bugs to "dt-fission-future" because they don't block Fission MVP.

Fission Milestone: MVP → Future
Whiteboard: dt-fission-reserve → dt-fission-future
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.