Ad clicks are not recorded for Bing search engine
Categories
(Firefox :: Search, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox87 | --- | unaffected |
firefox88 | --- | fixed |
firefox89 | --- | fixed |
People
(Reporter: cbaica, Assigned: standard8)
References
Details
(Keywords: regression)
Affected versions
- Fx88.0a
Affected platforms
- Windows 10
- Ubuntu 18.04
- macOS 10.15
Preconditions
Have NordVPN addon installed in Firefox and connected to US.
Have Bing set as your default engine.
Set 'browser.search.region' to US.
Steps to reproduce
- Launch Firefox.
- Using the URL bar search for 'iphone 12'.
- In the search results page, click on an ad link.
- Return to the search results page and click on another ad link.
- Return to the search results page and click on another ad link.
Expected result
- The ad clicks are correctly recorded and displayed in the telemtry page.
Actual result
- No ad click telemetry pings are recorded.
Regression range
- This looks like a recent regression, as in Fx87 RC i cannot reproduce the issue (ad clicks are recorded in telemetry)
Additional notes
- Even after multiple restarts, no telemetry pings are recorded.
- The 'browser.search.withads' is recorded and displayed in the telemetry page.
Reporter | ||
Comment 1•3 years ago
|
||
Last good build: 2021-03-10
First bad build: 2021-03-11
The regression range pointed me to this range: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=569826c0fd47a0e196057500c0873fab31253b70&tochange=96508d0c910050edc14dd95cd9af86036dac0b90
Reporter | ||
Updated•3 years ago
|
Reporter | ||
Updated•3 years ago
|
Comment 2•3 years ago
|
||
:dharvey, this seems like it might be high severity? If so, could you prioritize and/or assign?
Updated•3 years ago
|
Assignee | ||
Comment 3•3 years ago
|
||
I'm starting to look at this, I'm trying to gather more information first to find out what's affected.
Assignee | ||
Comment 4•3 years ago
|
||
The issue here is the same as bug 1699467.
Assignee | ||
Comment 5•3 years ago
|
||
Note: I think the regressing point here may have been different from bug 1699467, but the same thing fixes it.
Updated•3 years ago
|
Description
•