Closed
Bug 1962757
Opened 6 months ago
Closed 6 months ago
For SERP telemetry, allow fields within cookies to be in any part of the field
Categories
(Firefox :: Search, task, P2)
Firefox
Search
Tracking
()
VERIFIED
FIXED
140 Branch
People
(Reporter: standard8, Assigned: standard8)
References
(Blocks 1 open bug)
Details
(Whiteboard: [sng])
Attachments
(3 files, 1 obsolete file)
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-esr128+
|
Details | Review |
Currently when checking the SERP for follow-ons, we require that the parameter within the cookie is at the start of the cookie. This might not be correct and depends on the third party. We should make it more flexible, as Android has already done (bug 1932178).
Updated•6 months ago
|
| Assignee | ||
Comment 1•6 months ago
|
||
Updated•6 months ago
|
Assignee: nobody → standard8
Status: NEW → ASSIGNED
Pushed by mbanner@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/1b0705a51a59
For SERP telemetry, allow fields within cookies to be in any part of the field. r=search-reviewers,scunnane
Status: ASSIGNED → RESOLVED
Closed: 6 months ago
status-firefox140:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 140 Branch
| Assignee | ||
Comment 6•6 months ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D246956
Updated•6 months ago
|
Attachment #9485735 -
Flags: approval-mozilla-beta?
Comment 7•6 months ago
|
||
firefox-beta Uplift Approval Request
- User impact if declined: None, telemetry-only change, needed to fix some telemetry reporting for search engine result pages.
- Code covered by automated testing: yes
- Fix verified in Nightly: yes
- Needs manual QE test: yes
- Steps to reproduce for manual QE testing: Search QA already have STR
- Risk associated with taking this patch: Low
- Explanation of risk level: Small self-contained change to telemetry recording.
- String changes made/needed: None
- Is Android affected?: no
Flags: qe-verify+
| Assignee | ||
Comment 8•6 months ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D246956
Updated•6 months ago
|
Attachment #9485756 -
Flags: approval-mozilla-beta?
Updated•6 months ago
|
Attachment #9485756 -
Attachment is obsolete: true
Attachment #9485756 -
Flags: approval-mozilla-beta?
| Assignee | ||
Comment 9•6 months ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D246956
Updated•6 months ago
|
Attachment #9485773 -
Flags: approval-mozilla-esr128?
Comment 10•6 months ago
|
||
firefox-esr128 Uplift Approval Request
- User impact if declined: None, telemetry-only change, needed to fix some telemetry reporting for search engine result pages.
- Code covered by automated testing: yes
- Fix verified in Nightly: yes
- Needs manual QE test: yes
- Steps to reproduce for manual QE testing: Search QA already have STR
- Risk associated with taking this patch: Low
- Explanation of risk level: Small self-contained change to telemetry recording.
- String changes made/needed: None
- Is Android affected?: no
Updated•6 months ago
|
Flags: in-testsuite+
Updated•6 months ago
|
Attachment #9485735 -
Flags: approval-mozilla-beta? → approval-mozilla-beta+
Updated•6 months ago
|
Attachment #9485773 -
Flags: approval-mozilla-esr128? → approval-mozilla-esr128+
Updated•6 months ago
|
status-firefox139:
--- → fixed
Updated•6 months ago
|
status-firefox-esr128:
--- → fixed
Comment 11•6 months ago
|
||
| uplift | ||
Comment 12•6 months ago
|
||
| uplift | ||
Updated•6 months ago
|
QA Whiteboard: [QA-3962][uplift][qa-ver-needed-c140/b139]
QA Contact: cbaica
Comment 13•6 months ago
|
||
Issue is verified fixed part of the testing activities for bug 1962763, on nightly, beta and ESR builds. Please note that for ESR an intermediary treeherder build was used for verification.
Status: RESOLVED → VERIFIED
QA Whiteboard: [QA-3962][uplift][qa-ver-needed-c140/b139] → [QA-3962][uplift][qa-ver-done-c140/b139]
Flags: qe-verify+
You need to log in
before you can comment on or make changes to this bug.
Description
•