Closed
Bug 1504686
Opened 7 years ago
Closed 7 years ago
In content probe is double counting DuckDuckGo
Categories
(Firefox :: Search, defect, P1)
Firefox
Search
Tracking
()
VERIFIED
FIXED
Firefox 65
People
(Reporter: mkaply, Assigned: mkaply)
References
(Blocks 1 open bug)
Details
Attachments
(1 file, 1 obsolete file)
47 bytes,
text/x-phabricator-request
|
jcristau
:
approval-mozilla-beta+
|
Details | Review |
DuckDuck go does a redirect on the search so we are double counting.
Need to either get DuckDuckGo to fix or update our engine to include the param they are adding.
Assignee | ||
Comment 1•7 years ago
|
||
Assignee | ||
Comment 2•7 years ago
|
||
BrowserUsageTelemetry is counting all URLs including same document.
We don't want that, so we have to explicitly exclude it.
Assignee | ||
Updated•7 years ago
|
Priority: -- → P1
Updated•7 years ago
|
Attachment #9023114 -
Attachment is obsolete: true
Assignee | ||
Comment 3•7 years ago
|
||
Assignee | ||
Comment 4•7 years ago
|
||
adw:
Any ideas on how to write a test for this?
You did some pretty clever tests for the private browsing stuff.
Flags: needinfo?(adw)
Comment 5•7 years ago
|
||
I would probably start by trying to write a small web page that mimics whatever DDG does to trigger this bug, and then the test would just load it and make sure we didn't double count. Or if it's a server-level thing then you could write an sjs script and load that instead.
DDG is getting captured here due to the SEARCH_PROVIDER_INFO stuff that I recently modified, right? So you could use the same observe() technique to add your test URL so that it's captured during the test.
I'd also run the test without the fix to make sure it does trigger the double count of course.
Flags: needinfo?(adw)
Assignee | ||
Comment 6•7 years ago
|
||
I'm going to take this as is and file a followup for the test. We can't risk not having this with the other changes.
Pushed by mozilla@kaply.com:
https://hg.mozilla.org/integration/autoland/rev/b39b4f4ba16b
Don't count search for same document changes. r=Standard8
Comment 8•7 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 65
Assignee | ||
Comment 9•7 years ago
|
||
To test this, do a duckduckgo search via one off searches.
Go to about:Telemetry, search on SEARCH_COUNTS
notice that there were two recorded searches before this patch.
Flags: qe-verify+
Comment 10•7 years ago
|
||
Reproduced the issue on the affected Nightly 65.0a1 (2018-11-05) on Windows 7/10, Mac OS 10.13 and Ubuntu 16.04.
The issue can no longer be reproduced on the latest Nightly 65.0a1 (2018-11-15) as per Comment 9 now there is only 1 recorded search in about:telemetry, thus closing it as Verified - Fixed on all the above mentioned OS.
Assignee | ||
Comment 11•7 years ago
|
||
[Tracking Requested - why for this release]: We need this change in 64, but I think there was an issue with a checkin from Drew that needs to be resolved first.
tracking-firefox64:
--- → ?
Comment 12•7 years ago
|
||
OK, please request uplift when you get a chance. AFAICT this grafts cleanly on beta. (I guess you're talking about 1499193?)
Assignee | ||
Comment 13•7 years ago
|
||
Comment on attachment 9023791 [details]
Bug 1504686 - Don't count search for same document changes.
[Beta/Release Uplift Approval Request]
Feature/Bug causing the regression: Bug 1482158
User impact if declined: Incorrect telemetry on DDG
Is this code covered by automated tests?: No
Has the fix been verified in Nightly?: Yes
Needs manual test from QE?: Yes
If yes, steps to reproduce: Steps in bug.
List of other uplifts needed: None
Risk to taking this patch: Low
Why is the change risky/not risky? (and alternatives if risky): Just adds an extra check to the search record.
String changes made/needed:
Attachment #9023791 -
Flags: approval-mozilla-beta?
Comment 14•7 years ago
|
||
Comment on attachment 9023791 [details]
Bug 1504686 - Don't count search for same document changes.
search telemetry fix, approved for 64.0b11
Attachment #9023791 -
Flags: approval-mozilla-beta? → approval-mozilla-beta+
Comment 15•7 years ago
|
||
bugherder uplift |
Updated•7 years ago
|
Flags: qe-verify+
Comment 16•7 years ago
|
||
Verified - fixed on latest Firefox 64.0b11 (Build ID: 20181119162153) on Windows 7/10, Mac OS 10.14 and Ubuntu 16.04.
Marking it as verified for fx 64 and removing qe+ flag.
Flags: qe-verify+
You need to log in
before you can comment on or make changes to this bug.
Description
•