Open Bug 1663753 Opened 5 years ago Updated 4 years ago

Add telemetry to measure the time platform printing code takes to create/update/scroll print/preview documents

Categories

(Core :: Printing: Setup, task, P2)

Product:
Core
Component:
Printing: Setup
Type:
task

Tracking

()

People

(Reporter: jwatt, Unassigned)

References

Details

(Whiteboard: [print2020][old-ui-])

We know we have some bad performance issues when it comes to creating, updating and displaying print [preview] documents. For example, we don't support incremental reflow, which means we need to redo a lot more work than we otherwise should. We should have some telemetry to measure the impact of any future efforts to improve things. Some things that come to mind include the time taken from:

  • FrameLoader.printPreview() being called to completion of the creation of a print preview document
  • FrameLoader.printPreview() being called to completion of each indivitual settings change exposed in the UI
  • FrameLoader.print() being called to completion
  • The time taken between scrolling part of a print preview document into view and rendering completing
Priority: P1 → P2
Whiteboard: [print2020_v82][old-ui-] → [print2020_v83][old-ui-]
Whiteboard: [print2020_v83][old-ui-] → [print2020_v84][old-ui-]
Whiteboard: [print2020_v84][old-ui-] → [print2020_v85][old-ui-]
Whiteboard: [print2020_v85][old-ui-] → [print2020_v87][old-ui-]
Whiteboard: [print2020_v87][old-ui-] → [print2020][old-ui-]
You need to log in before you can comment on or make changes to this bug.