Closed
Bug 359880
Opened 19 years ago
Closed 19 years ago
Add param "aq=t" to the Google search engine spec
Categories
(Firefox :: Search, enhancement)
Tracking
()
RESOLVED
FIXED
People
(Reporter: mozilla, Assigned: mozilla)
Details
(Keywords: verified1.8.1.2)
Attachments
(2 files)
|
2.65 KB,
patch
|
Gavin
:
review+
dveditz
:
approval1.8.1.2+
|
Details | Diff | Splinter Review |
|
6.57 KB,
patch
|
Pike
:
review+
mconnor
:
superreview+
dveditz
:
approval1.8.1.2+
|
Details | Diff | Splinter Review |
The Google search folks would like us to add an "aq=t" parameter to Google search queries that originate from the searchbar. (This parameter identifies the query as coming from a suggest-enabled searchbox.)
| Assignee | ||
Comment 1•19 years ago
|
||
Updated•19 years ago
|
Attachment #244942 -
Flags: review?(mconnor)
Attachment #244942 -
Flags: review?(gavin.sharp)
Attachment #244942 -
Flags: review+
| Assignee | ||
Comment 2•19 years ago
|
||
We also need to update any other localized versions of the Google plugin (only Japan at this point?).
Comment 3•19 years ago
|
||
affected versions would be ja, ja-JP-mac, and ar.
Comment 4•19 years ago
|
||
Wrong mic, sorry.
Mic, could you see which pages we need to update to protocol this change in search?
rhelmer probably needs to add this to his checks, too.
Comment 5•19 years ago
|
||
axel,
you mean which search page requirements we need to change? in that case i believe it would be...http://wiki.mozilla.org/Firefox2/L10n_Requirements
please advise
mic
Comment 6•19 years ago
|
||
At least, yes. I'm not exactly sure what we have on the intranet.
Do we have the arabic and japanese plugin deviations documented somewhere?
Comment 7•19 years ago
|
||
here's what we have (that i know about) on the intranet and I don't believe that it makes sense to document it there, lmk if you disagree
https://intranet.mozilla.org/Trademark_L10n_Review-Firefox2#Search_Plug-ins
if this is a new requirements to create this documentation, lmk
| Assignee | ||
Comment 8•19 years ago
|
||
I don't believe that the ar localization's plugin needs to be updated because it doesn't have Suggest activated.
Attachment #249792 -
Flags: superreview?(mconnor)
Attachment #249792 -
Flags: approval-l10n?
Updated•19 years ago
|
Attachment #249792 -
Flags: superreview?(mconnor) → superreview+
Comment 9•19 years ago
|
||
I don't know if this is the complete list of Google search suggest locales, this was not a requirement I had documented. Axel, do you know for sure if this it the complete list? if yes, great, if not, I'll follow up with our contact at Google to be sure.
Comment 10•19 years ago
|
||
Joe's been our liason to the Suggest team. Currently en and jp are the only locales with active suggest results. Not sure why AR has suggest, that'll get english results afaict.
We should definitely track this in the searchplugin reqs.
Comment 11•19 years ago
|
||
As an added note: we should track this for all searchplugins, since any searchplugin can implement it (Yahoo/Answers/one of the Japanese engines (goo?) already do so).
Comment 12•19 years ago
|
||
ok, will track going forward.
Comment 13•19 years ago
|
||
We need to get this resolved by 2.0.0.2
Mic/Axel, can you do whatever you need to do here?
Flags: blocking1.8.1.2+
Comment 14•19 years ago
|
||
will do
| Assignee | ||
Comment 15•19 years ago
|
||
Ping: still waiting on L10N approval on these patches (also, I think technically mconnor needs to SR+ the English patch).
Comment 16•19 years ago
|
||
Comment on attachment 249792 [details] [diff] [review]
Makes the required change to ja and ja-JP-mac localizations
We should really kill that flag, I don't look at it anymore. Doing an r+ instead.
Attachment #249792 -
Flags: approval-l10n? → review+
| Assignee | ||
Comment 17•19 years ago
|
||
Assuming that we now have all the relevant approvals, could someone with l10n checkin approval land these patches?
Updated•19 years ago
|
Attachment #244942 -
Flags: review?(mconnor)
Comment 18•19 years ago
|
||
Both patches need 1.8.1 branch driver approval (approval1.8.1.2) for landing on the 1.8 branch. The en-US patch can land on the trunk now; the l10n patch doesn't apply to the trunk.
| Assignee | ||
Updated•19 years ago
|
Attachment #244942 -
Flags: approval1.8.1.2?
| Assignee | ||
Updated•19 years ago
|
Attachment #249792 -
Flags: approval1.8.1.2?
Comment 19•19 years ago
|
||
Comment on attachment 244942 [details] [diff] [review]
Adds the parameter
approved for 1.8 branch, a=dveditz for drivers
Attachment #244942 -
Flags: approval1.8.1.2? → approval1.8.1.2+
Comment 20•19 years ago
|
||
Comment on attachment 249792 [details] [diff] [review]
Makes the required change to ja and ja-JP-mac localizations
approved for the 1.8-l10n branch, a=dveditz for drivers
Attachment #249792 -
Flags: approval1.8.1.2? → approval1.8.1.2+
Comment 21•19 years ago
|
||
Comment on attachment 249792 [details] [diff] [review]
Makes the required change to ja and ja-JP-mac localizations
I landed the l10n patch on the branch,
Checking in ja/browser/searchplugins/google-jp.xml;
/l10n/l10n/ja/browser/searchplugins/Attic/google-jp.xml,v <-- google-jp.xml
new revision: 1.1.2.7; previous revision: 1.1.2.6
done
Checking in ja-JP-mac/browser/searchplugins/google-jp.xml;
/l10n/l10n/ja-JP-mac/browser/searchplugins/Attic/google-jp.xml,v <-- google-jp.xml
new revision: 1.1.2.6; previous revision: 1.1.2.5
done
| Assignee | ||
Comment 22•19 years ago
|
||
Thanks, Axel!
| Assignee | ||
Comment 23•19 years ago
|
||
I just landed the en-US patch on branch & trunk.
You need to log in
before you can comment on or make changes to this bug.
Description
•