Closed Bug 178149 Opened 22 years ago Closed 15 years ago

Search from URL Bar or sidebar not recognising "+" characters

Categories

(SeaMonkey :: Search, defect)

Product:
SeaMonkey
Component:
Search
Platform:
x86
All
Type:
defect
Priority:
Not set
Severity:
minor

Tracking

(Not tracked)

Status:
VERIFIED WORKSFORME

People

(Reporter: paul, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20020929
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20020929

Mostly when I search in Google, I'll enter a string such as "+foobar +bob". The
form get submitted back, and the "+" characters are translated correctly into
the code %2B. Eg:
  
http://www.google.com/search?hl=en&ie=UTF-8&oe=UTF-8&q=%2Bfoobar+%2Bbob&btnG=Google+Search

However, searching from the URL bar doesn't transpose the "+" for the hexcode.
Instead, it leaves the "+" in the url which Google translates as a space
character. The resulting URL is something like:

http://www.google.com/search?q=+foobar%20+bob&sourceid=mozilla-search&start=0&start=0&ie=utf-8&oe=utf-8

This is mostly ok, but occasionally does produce a lot of extra results that
aren't necessarily required. Not sure how many other people insist on using
control characters in their search string, but it would be nice if they can be
translated properly.

Other search engines seem to translate this properly from the URL bar, eg Dmoz.org

Reproducible: Always

Steps to Reproduce:
Select Google as your default search engine
1. Enter "+foobar +bob" (without quotes, using proper search terms)
2. Select Search Google for ... or click the search icon.
Just for your information, the query 

+foobar +bob

in Google is the same as the query

foobar bob

though in other seach engines it would make a difference.

-M
Sorry for the SPAM. Additionally:

This actually WorksForMe in Win2K 20021104.

It WFM with Netscape Search as the URLBar Search, and it WFM with Google as the
URLBar Search.

-M
*** Bug 185948 has been marked as a duplicate of this bug. ***
adding to summary
Summary: Search from URL Bar not recognising "+" characters → Search from URL Bar or sidebar not recognising "+" characters
*** Bug 188882 has been marked as a duplicate of this bug. ***
*** Bug 197522 has been marked as a duplicate of this bug. ***
Status: UNCONFIRMED → NEW
Ever confirmed: true
It actually makes a difference with Google. See
<http://www.google.de/intl/de/help/basics.html#stopwords>.
How a particular search engine interprets a '+' doesn't change the fact that
Internet Keywords doesn't submit what you entered into the URL bar if it
contains a '+'. Try submitting anything to do with C++ using IK.

(N.B. the Limitations section at the foot of
http://www.mozilla.org/docs/end-user/internet-keywords.html does say this
feature doesn't work with all input)
Oh, and I think this should be OS=all, I see it in Win98 and Linux
*** Bug 207462 has been marked as a duplicate of this bug. ***
*** Bug 208631 has been marked as a duplicate of this bug. ***
Changed OS to All based on comment 9.

-M
OS: Windows 2000 → All
*** Bug 212737 has been marked as a duplicate of this bug. ***
-> Search
Assignee: hewitt → shliang
Component: Location Bar → Search
QA Contact: claudius → petersen
*** Bug 216826 has been marked as a duplicate of this bug. ***
I've done a patch for this and other search-in-URL-bar oddness; see #245597
Product: Core → SeaMonkey
Assignee: shliang → nobody
QA Contact: chrispetersen → search
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.