Open Bug 1208476 Opened 9 years ago Updated 2 years ago

Websocket Frame Listener API should also provide timing info

Categories

(Core :: Networking: WebSockets, defect, P5)

Product:
Core
Component:
Networking: WebSockets
Type:
defect

Tracking

()

People

(Reporter: Honza, Unassigned)

References

Details

(Whiteboard: [necko-would-take]) 

Websocket Frame Listener API (introduced in bug 1203802) should also provide timing information.

Every frame should have the following timing info.
1) Start of frame data receiving
2) End of frame data receiving

This should allow developer tools to build waterfall diagrams (similarly to what the existing Network panel displays) and also append new labels into existing timeline.


Honza
Whiteboard: [necko-would-take]
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P5
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.