Open
Bug 1544788
Opened 6 years ago
Updated 3 years ago
[network markers] Add a timing for requestEnd
Categories
(Core :: Gecko Profiler, enhancement, P3)
Core
Gecko Profiler
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox68 | --- | affected |
People
(Reporter: julienw, Unassigned)
References
(Blocks 1 open bug)
Details
Currently we have the following timings:
- requestStart
- responseStart
- responseEnd
I think we miss a requestEnd timing, so that we can display how much time we're waiting for the response without doing anything.
Type: defect → enhancement
Priority: -- → P3
|
Reporter | |
Updated•6 years ago
|
Blocks: network-markers
|
|
Reporter | |
Comment 1•5 years ago
|
||
Hey Valentin,
do you think this can/should be added to the existing Timing Structure?
Flags: needinfo?(valentin.gosu)
|
||
Comment 2•5 years ago
|
||
Probably yes. The structure is supposed to mirror the resource-timing-api, which doesn't include this.
The only problem is recording this timestamp accurately. I assume it should happen somewhere in nsHttpTransaction::ReadSegments
Flags: needinfo?(valentin.gosu)
|
||
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•