Closed Bug 1825768 Opened 2 years ago Closed 2 years ago

Only set the SERP telemetry timer for pages that we know are SERPs

Categories

(Firefox :: Search, task, P3)

task

Tracking

()

RESOLVED FIXED
114 Branch
Tracking Status
firefox114 --- fixed

People

(Reporter: standard8, Assigned: jteow)

Details

Attachments

(1 file)

Currently in SearchSERPTelemetryChild we set a timer whenever a page is loaded so that we can check to see if there is SERP telemetry to report.

We should be able to do the "is this a relevant doc" checks before we set the timer. If so, this would avoid the extra spike to do nothing.

I don't think it gains us anything significant, but it would seem better to avoid a timer wake-up if we can.

I also moved cancelCheck to didDestroy since it seems like a common pattern amongst
other children. Once destroyed and constructed again in a new page load, isSerp should be
null again.

Assignee: nobody → jteow
Status: NEW → ASSIGNED
Pushed by jteow@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/b217d35accf8 Prevent timer in SearchSERPTelemetryChild from firing on non-SERPs - r=Standard8
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 114 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: