123748 - Typing "? keyword' into location bar does not work

Status: RESOLVED DUPLICATE of bug 95199

(SeaMonkey :: Search, defect)

Description

[Javier Morales]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:0.9.8) Gecko/20020204
BuildID:    2002020411

When I want to do a single-word search on Mozilla, I type "? keyword" (wihtout
the quotes) into the location bar and hit enter. When I do this, nothing
happens. Afterwards, if I click on the location bar, and hit enter nothing will
happen. I can workaround by selecting down arrow and highllighting seach google
for "keyword."

Reproducible: Always
Steps to Reproduce:
1. type question mark followed by single word on location bar 
2. hit enter
3.

Actual Results:  nothing happens

Expected Results:  google search should be initiated using single keyword I
typed into location bar

Comment 1

[Peter Trudelle]

->hewitt

Comment 2

[Chibi15]

2002031005 / Mac OS X confirmed.

Comment 3

[Greg K.]

Javier, what is the significance of the question mark preceding your search
word? I find no mention of it in Mozilla's documentation.

Comment 4

[Javier Morales]

The question mark is to let the browser know that I want to search the internet
for the word(s) that follow the question mark. Usuallly this is more of a
problem with single keyword searches and with multiple keyword searches. 

If I type a single word into the URL bar, I expect the browser to wrap that
around http://www. and .com and take me to that URL. e.g. Typing "cats" into the
URL bar would take me to http://www.cats.com. However, if I preceed that word
with a question mark and a space ("? cats") I would expect the browser to search
my selected search engine with the keyword cats.

I though this was normal browser behavior.

Comment 5

[Greg K.]

-->Search to confirm whether or not "? foo" is some sort of official search
trigger mechanism.

Comment 6

[Asa Dotzler [:asa]]

"?" has never performed a search. This is not a bug.

Comment 7

[Daniel Wang]

reopen to mark as dupe of bug 95199

Comment 8

[Daniel Wang]

*** This bug has been marked as a duplicate of 95199 ***