Closed
Bug 1421904
Opened 7 years ago
Closed 6 years ago
Collect a more precise timestamp for each event
Categories
(Firefox :: New Tab Page, enhancement, P3)
Firefox
New Tab Page
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: Mardak, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [AS61MVP])
This is so we can compute time to first interaction.
Each event should have a precise timestamp like we have for our other performance metrics so that we can subtract it from load_trigger_ts to compute this.
Right now we only have a "receive_at" field populated by the server, rounded to the nearest minute, which is not useful for this computation.
Reporter | ||
Updated•7 years ago
|
status-firefox58:
--- → wontfix
Reporter | ||
Updated•7 years ago
|
Iteration: 1.26 → 1.27
Reporter | ||
Updated•7 years ago
|
Iteration: 1.27 → 60.1 - Jan 29
Reporter | ||
Updated•7 years ago
|
Reporter | ||
Updated•7 years ago
|
Iteration: 60.1 - Jan 29 → 60.2 - Feb 12
Reporter | ||
Updated•7 years ago
|
Severity: normal → enhancement
Reporter | ||
Updated•7 years ago
|
status-firefox60:
--- → affected
Updated•7 years ago
|
Whiteboard: [AS60MVP]
Updated•7 years ago
|
Iteration: 60.2 - Feb 12 → 60.3 - Feb 26
Updated•7 years ago
|
Iteration: 60.3 - Feb 26 → 60.4 - Mar 12
Updated•7 years ago
|
Reporter | ||
Updated•7 years ago
|
Iteration: --- → 61.1 - Mar 26
Updated•7 years ago
|
Whiteboard: [AS60MVP] → [AS61MVP]
Updated•7 years ago
|
Iteration: 61.1 - Mar 26 → ---
Reporter | ||
Updated•7 years ago
|
Iteration: --- → 61.2 - Apr 9
Priority: P3 → P2
Updated•7 years ago
|
Iteration: 61.2 - Apr 9 → 61.4 - May 7
Updated•7 years ago
|
Iteration: 61.4 - May 7 → ---
Reporter | ||
Updated•7 years ago
|
Iteration: --- → 62.1 - May 21
Priority: P2 → P3
Updated•7 years ago
|
Iteration: 62.1 - May 21 → 63.1 - July 9
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Updated•6 years ago
|
Iteration: 63.1 - July 9 → ---
Assignee | ||
Updated•5 years ago
|
Component: Activity Streams: Newtab → New Tab Page
You need to log in
before you can comment on or make changes to this bug.
Description
•