If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Remove affiliate codes from default Google plugin in en-US

RESOLVED FIXED in Firefox 34



3 years ago
3 years ago


(Reporter: kev, Assigned: kev)


34 Branch
Firefox 37
Dependency tree / graph

Firefox Tracking Flags

(firefox34+ fixed, firefox35+ fixed, firefox36+ fixed, firefox37 fixed, firefox-esr3135+ fixed)



(3 attachments)



3 years ago
Created attachment 8527051 [details] [diff] [review]

Per expiration of the search agreement, the Google affiliate codes must be removed from any and all official builds. Note that Google plugins also exist in the JP and KU locales, and also need to be modified.
Attachment #8527051 - Flags: review?(gavin.sharp)
(In reply to Kev Needham [:kev] from comment #0)
> Note that Google plugins also
> exist in the JP and KU locales, and also need to be modified.

Flod, can we do that for 34? (Separate bug perhaps)
Flags: needinfo?(francesco.lodolo)
We will also need to adjust browser/components/search/test/browser_google_behavior.js and browser/components/search/test/browser_google.js accordingly.
Ah, bug 1103229 is already on file for ku.

Comment 4

3 years ago
For Japan, preferred approach would be to remove all the google plugins and reference the default, which Google has requested multiple times over the year.
Comment on attachment 8527051 [details] [diff] [review]

f?mfinkle for the mobile/ change.

It feels like there might be some value in leaving in a "from Firefox" generic parameter here, but I guess I don't feel strongly.

We will also need the test changes from comment 2.

I assume you are taking care of looping in whoever needs to be looped in to ensure it is consistent with partner expectations and communicate it to them as needed.
Attachment #8527051 - Flags: review?(gavin.sharp)
Attachment #8527051 - Flags: review+
Attachment #8527051 - Flags: feedback?(mark.finkle)

Comment 6

3 years ago
mconnor and I talked briefly about it, but cc'ing him and Joanne to make sure they close the loop with Google. mconnor - could you verify here when we've got an Ack from Google that the change meets obligations, please and thanks?
Flags: needinfo?(mconnor)

Comment 7

3 years ago
wrt value around leaving client="firefox" in, I'll defer to BD there. They can get the same info from UA analysis, and we don't see any benefit from it that I'm aware of, but users may if it triggers anything on page rendering. Good item to also follow up with them on.
(In reply to :Gavin Sharp [email: gavin@gavinsharp.com] from comment #1)
> Flod, can we do that for 34? (Separate bug perhaps)

I don't think so, Firefox 35 is more likely. I think we're going to have a RC on Monday, but pushing this change doesn't feel safe (CCing also Pike).

* Japanese is up to date with sign-offs, so I don't see any issue with shipping in Fx35, even happier if we drop the Japanese's variant all together.
* Kurdish is quite behind with sign-offs, not sure if we're in shape to take a sign-off on beta next cycle with the updated searchplugin. Let's continue the discussion about Kurdish in bug 1103229.
Flags: needinfo?(francesco.lodolo)
status-firefox34: --- → affected
status-firefox35: --- → affected
status-firefox36: --- → affected
status-firefox-esr31: --- → affected
tracking-firefox34: --- → +
tracking-firefox35: --- → +
tracking-firefox36: --- → +
tracking-firefox-esr31: --- → 35+
Francesco, if there's any way we can fix ja we should do so, even if we need extra QA from MozJP people. This is a requirement.

For everything else, this is 100% good to go.  No notification needed.
Flags: needinfo?(mconnor)


3 years ago
Blocks: 1103970
Attachment #8527051 - Flags: feedback?(mark.finkle) → feedback+
Created attachment 8527742 [details] [diff] [review]
test fixes
Attachment #8527742 - Flags: review?(felipc)
Attachment #8527742 - Flags: review?(dolske)
Attachment #8527742 - Flags: review?(felipc) → review+
Attachment #8527742 - Flags: review?(dolske)
status-firefox34: affected → fixed
Assignee: nobody → kev
https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=7d31faa161d8 (central)
https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=602e6e251617 (Aurora)
Try: https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=b232181e8006

Last Resolved: 3 years ago
status-firefox37: --- → fixed
Resolution: --- → FIXED
Target Milestone: Firefox 34 → Firefox 37
status-firefox35: affected → fixed
status-firefox36: affected → fixed
We need to remove the Google affiliate codes from Firefox ESR builds as well. Does this patch apply cleanly to the ESR31 branch?

Gavin/Ryan - Can you handle landing this today/tomorrow?

Ben - We should hold off on the ESR build until we can remove the codes.
Flags: needinfo?(ryanvm)
Flags: needinfo?(gavin.sharp)
Flags: needinfo?(bkerensa)
Needs rebasing for esr31 AFAICT.
Flags: needinfo?(ryanvm)
Created attachment 8544245 [details] [diff] [review]
esr31 patch
Flags: needinfo?(gavin.sharp)
Attachment #8544245 - Flags: approval-mozilla-esr31?
Attachment #8544245 - Flags: approval-mozilla-esr31? → approval-mozilla-esr31+
status-firefox-esr31: affected → fixed
Test failures :(
Flags: needinfo?(bkerensa) → needinfo?(gavin.sharp)
Bustage fix:
Flags: needinfo?(gavin.sharp)
You need to log in before you can comment on or make changes to this bug.