269360 - Google fails to recognise when <enter> is used to search

Status: RESOLVED INVALID

(Firefox :: General, defect)

Description

[Zac Evans]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

At www.google.com, you can perform a search by either typing something and
pressing enter, or by clicking the `search' button with the mouse. Normally if
you click the `search' button then google give you the tip: `Tip: Save time by
hitting the return key instead of clicking on "search"'
But in Firefox 1.0 it gives that hint everytime (unless you use the search in
the toolbar).
I suspect that this bug might affect other websites as well.

Reproducible: Always
Steps to Reproduce:
1. Go to www.google.com
2. Type something in the search box
3. Press <enter>

Actual Results:  
Google thinks that I have pressed the `search' with the mouse instead of <enter>
on my keyboard. It gives the message: `Tip: Save time by hitting the return key
instead of clicking on "search"'

Expected Results:  
Google should recognise that <enter> was used. ie. it should not give the `Tip'
every time.

Comment 1

[OstGote!]

WFM with FF 1.0 en-US on WinNT4

Comment 2

[Ross Shannon]

Google has no way of telling whether you clicked the button or pressed enter. It
gets the same data either way. As far as I can tell the hint is randomly
inserted into some searches.
->INVALID

Comment 3

[Zac Evans]

That's not true.
Try it with Internet Explorer. Notice that the tip comes up everytime if you
click `search', but never comes up if you use enter.
In Firefox the tip comes up everytime. (unless it has a different tip to give
you, possibly).

If you still don't believe me that the Google site isn't working correctly, then
I'll let it go. But the behavour of Firefox is different to that of IE and in
this case IE's behavour is the better one.

Comment 4

[:Gavin Sharp [email: [e-mail]]]

This is invalid, Google's failings are not Firefox's, and I don't even see that
behavior anymore.