Closed
Bug 1963372
Opened 1 year ago
Closed 1 year ago
Submit private ping in addition with newtab ping if enabled
Categories
(Firefox :: New Tab Page, defect)
Firefox
New Tab Page
Tracking
()
VERIFIED
FIXED
140 Branch
| Tracking | Status | |
|---|---|---|
| firefox140 | --- | verified |
People
(Reporter: nbarrett, Assigned: nbarrett)
References
Details
Attachments
(1 external file)
Currently, if the pref for the private ping is enabled it will record the newtab-content ping INSTEAD of the newtab ping. It should call the newtab-content ping in addition to newtab ping.
| Assignee | ||
Comment 1•1 year ago
|
||
Updated•1 year ago
|
Assignee: nobody → nbarrett
Status: NEW → ASSIGNED
Pushed by nbarrett@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ed4b96444dc5
Call newtab-content ping in addition to newtab ping if enabled r=home-newtab-reviewers,thecount
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox140:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 140 Branch
Updated•1 year ago
|
QA Whiteboard: [qa-triage-done-c141/b140]
Flags: qe-verify+
Comment 4•1 year ago
|
||
I have verified this issue by setting up the prefs from here and can confirm the following:
- The
pocket.impressionandpocket.clickevents are part of the "newtab" ping. - The
newtab_content.impressionandnewtab_content.clickevents are part of the "newtab-content" ping.
Verified using the latest Firefox Beta 140.0b2 (Build ID: 20250528090620) installed on Windows 11, macOS 15.4.1, and Ubuntu 24.04.
You need to log in
before you can comment on or make changes to this bug.
Description
•