no longer sending homepage search params for about:home searches

VERIFIED FIXED in Firefox 26



4 years ago
4 years ago


(Reporter: Gavin, Assigned: Gavin)



26 Branch
Firefox 27
Bug Flags:
in-testsuite +

Firefox Tracking Flags

(firefox25 unaffected, firefox26+ verified, firefox27+ verified)



(2 attachments, 1 obsolete attachment)

The patch in bug caused us to stop sending the "homepage" reason to getSubmission, for about:home-triggered searches. That's bad!
This has the effect of altering the search params sent for Google searches and prevents us from being able to count about:home searches separately.
status-firefox25: --- → unaffected
status-firefox26: --- → affected
status-firefox27: --- → affected
tracking-firefox26: --- → +
tracking-firefox27: --- → +
Created attachment 816047 [details] [diff] [review]

Restoring the logic from
Assignee: nobody →
Attachment #816047 - Flags: review?(mnoorenberghe+bmo)
I'll try to write a test.
Comment on attachment 816047 [details] [diff] [review]

Review of attachment 816047 [details] [diff] [review]:

Sounds like we need a test. I though there was one before.
Attachment #816047 - Flags: review?(mnoorenberghe+bmo) → review+
Created attachment 816106 [details] [diff] [review]
with test

Adds a Google-specific test that covers actual search touch points. In retrospect, a generic test that just tests that we pass the appropriate "purpose" arguments with a custom search plugin would probably be sufficient and a bit cleaner, but I guess it doesn't hurt that much to be specific (gets us coverage of the case we actually care about).

I copied some of this from the existing browser_google.js, and some bits and pieces from browser_aboutHome.js and browser_keywordSearch.js.

I'm not quite happy with the "context menu" test - it's cheating a bit by calling the relevant function directly - but actually testing the context menu was a pain in the ass so I bailed.
Attachment #816047 - Attachment is obsolete: true
Attachment #816106 - Flags: review?(mnoorenberghe+bmo)
Comment on attachment 816106 [details] [diff] [review]
with test

Review of attachment 816106 [details] [diff] [review]:

The about:home part of the test seems overly complicated but I trust you that it's necessary.
Attachment #816106 - Flags: review?(mnoorenberghe+bmo) → review+
Target Milestone: --- → Firefox 27
Last Resolved: 4 years ago
status-firefox27: affected → fixed
Resolution: --- → FIXED
Flags: in-testsuite+
Comment on attachment 816106 [details] [diff] [review]
with test

[Approval Request Comment]
Bug caused by (feature/regressing bug #): bug 900865
User impact if declined: none (but we still care)
Testing completed (on m-c, etc.): N/A
Risk to taking this patch (and alternatives if risky): no risk, well tested
String or IDL/UUID changes made by this patch: none
Attachment #816106 - Flags: approval-mozilla-aurora?
Attachment #816106 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Keywords: checkin-needed


4 years ago
Keywords: verifyme


4 years ago
Whiteboard: [checkin-needed-aurora]
gavin, what are the steps to verify this?  

this is what I see in url's:

urlbar search:

searchbar search:

about:home search:

Nightly is similar, except with client=firefox-nightly
My nightly loads:

when I search for "test" from about:home.

That "channel=np&source=hp" would be missing prior to this bug being fixed.

(The patch hasn't landed on Aurora yet.)
ok, I get the correct URL on Nightly:
status-firefox27: fixed → verified
status-firefox26: affected → fixed
Keywords: checkin-needed
Whiteboard: [checkin-needed-aurora]
(In reply to :Gavin Sharp (use for email) from comment #14)

Test failures:

Backed out:
status-firefox26: fixed → affected
Thanks Ed, my fault for not paying close enough attention. The newly-added test needed to be tweaked since bug 925892 wasn't uplifted.
Created attachment 822421 [details] [diff] [review]
aurora patch

I have to step away; if someone could land this revised patch for me that'd be great!
Keywords: checkin-needed
Whiteboard: [checkin-needed-aurora]
Keywords: checkin-needed
Whiteboard: [checkin-needed-aurora]
status-firefox26: affected → fixed

Comment 19

4 years ago
Verified as fixed on Firefox 26b1 - 20131028225529 - on Windows 7, Ubuntu 13.04 and Mac OS X 10.9.
status-firefox26: fixed → verified
Keywords: verifyme
You need to log in before you can comment on or make changes to this bug.