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)

enhancement

Tracking

()

RESOLVED WONTFIX
Tracking Status
firefox58 --- wontfix
firefox59 --- wontfix
firefox60 --- 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.
Iteration: 1.26 → 1.27
Iteration: 1.27 → 60.1 - Jan 29
Iteration: 60.1 - Jan 29 → 60.2 - Feb 12
Severity: normal → enhancement
Whiteboard: [AS60MVP]
Iteration: 60.2 - Feb 12 → 60.3 - Feb 26
Iteration: 60.3 - Feb 26 → 60.4 - Mar 12
Iteration: 60.4 - Mar 12 → ---
Priority: P2 → P3
Blocks: 1437659
Iteration: --- → 61.1 - Mar 26
Whiteboard: [AS60MVP] → [AS61MVP]
Iteration: 61.1 - Mar 26 → ---
Iteration: --- → 61.2 - Apr 9
Priority: P3 → P2
Iteration: 61.2 - Apr 9 → 61.4 - May 7
Iteration: 61.4 - May 7 → ---
Iteration: --- → 62.1 - May 21
Priority: P2 → P3
Iteration: 62.1 - May 21 → 63.1 - July 9
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Iteration: 63.1 - July 9 → ---
Component: Activity Streams: Newtab → New Tab Page
You need to log in before you can comment on or make changes to this bug.