Closed Bug 361100 Opened 18 years ago Closed 18 years ago

Using the "google" keyword to search for a string, firefox sends "google" as part of the string

Categories

(Firefox :: Search, defect)

x86
Windows XP
defect
Not set
minor

Tracking

()

RESOLVED INVALID

People

(Reporter: daniel, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1) Gecko/20061010 Firefox/2.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1) Gecko/20061010 Firefox/2.0 Using the "google" keyword to search for a string, firefox sends "google" as part of the string eg (i enter "google foo bar" then when i get to the results from google i get results for "google foo bar" insted of just "foo bar". Reproducible: Always Steps to Reproduce: 1.Type in to the address bar "google anything" 2.Press return 3.Read the query sent to google Actual Results: The query sent to google was with "google" appended to the beginning of the string Expected Results: For the query sent to google to not include "google" at the beginning of the string Windows XP Home Edition SP2, 512MB Ram, 1.8 Ghrz AMD Mobile Sempron, Acer Aspire 3003wmli
WFM with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0 Went to www.google.com, right clicked in the input field, chose "Add a keyword for this search" and gave it the keyword google. Then I typed in the location bar google internet and I got a page with results for the word internet. So I think the bookmark with the keyword google is simply not yet present amongst your bookmarks.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → INVALID
Reporter, I think you're not using a "google" keyword at all. By default, Firefox will send everything in the location bar that doesn't look like an URL, and that isn't a keyword either, to Google, for a "I'm feeling lucky" search. That's why you end up at the google search-page. If you want to install such a keyword, you can use the instructions from Ria.
You need to log in before you can comment on or make changes to this bug.