I am able to reproduce this on the latest branch and trunk build, another similar
bug:  issue 4953 

Checked on:
1.0.154.39 (Official Build 7051)
1.0.155.0  (Developer Build 7219)

Might be a GURL issue (haven't checked)

(No comment was entered for this change.)

(No comment was entered for this change.)

Moving from milestone 2 to milestone 2.1.

(No comment was entered for this change.)

(No comment was entered for this change.)

(No comment was entered for this change.)

If i'm not mistaken this is just the Unicode (not sure) character of the parenthesis 
(which is U+0028 or %28) It's the same as when you enter a space in an address you will 
get %20. Also when you're using the search function you can always add a question mark 
in front of your sentence, so Chrome wont try to look for a website.

At this point the repro steps have changed slightly.  Prepend a scheme.  Changing 
summary to match.

This looks like some sort of strangeness with escaping or unescaping.  Brett is the 
most appropriate person to look.

(No comment was entered for this change.)

(No comment was entered for this change.)

In Chrome build 2.X, when type a key word in Omnibox, Chrome suggests http://keyword as 
the second item under Omnibox auto-complete pop-up, and it has problem if the keyword 
contains punctuations.

But we removed this suggestion on Omnibox2, so this bug is not valid anymore (Please 
refer to my screenshot attached), and I am closing this bug now.
 

	Suggestion_Removed.jpg 240 KB   View   Download

Xlyuan, this bug is very valid in Omnibox2. Notice that the description of the bug 
speaks about "http://тест("; try entering it, it still shows the bug in 3.0.193.0. 
Please reopen the bug.

Ah, you are right, thanks for your update, I am reopening this bug now :-)

Sorry, I missed this because I just tried typing тест(

Brett must be too busy. 

Cira, can you take a look at it? I think it might not be that hard to get to the bottom of 
this. 

Cira identified the cause and began to work on a fix. 

We were escaping punicode string after it was created (url_canon_host.cc, DoIDNHost). 
Mailed patch to Brett couple minutes ago.

 Issue 4953  has been merged into this issue.

Cira, can you point to Anthony in what revision of googleurl has your fix? Or, you can 
update the entry for googleurl in our DEPS file once it's checked in googleurl. 

Then, that DEPS change need  be picked up by 3.0 branch. 

I haven't checked it in yet, will do so today.

Just ping me when you do.

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=23965 

------------------------------------------------------------------------
r23965 | cira@chromium.org | 2009-08-21 09:35:17 -0700 (Fri, 21 Aug 2009) | 6 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/DEPS?r1=23965&r2=23964
   M http://src.chromium.org/viewvc/chrome/trunk/src/build/temp_gyp/googleurl.gyp?r1=23965&r2=23964
   M http://src.chromium.org/viewvc/chrome/trunk/src/net/http/http_network_transaction_unittest.cc?r1=23965&r2=23964

Pulling new version of googleurl into the tree.
Fixing a net_unittest case that wasn't updated when googleurl code was changed (but not down integrated to chrome).

BUG=5490

Review URL: http://codereview.chromium.org/174093
------------------------------------------------------------------------

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=24464 

------------------------------------------------------------------------
r24464 | laforge@chromium.org | 2009-08-26 10:30:58 -0700 (Wed, 26 Aug 2009) | 10 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/branches/195/src/DEPS?r1=24464&r2=24463
   M http://src.chromium.org/viewvc/chrome/branches/195/src/build/temp_gyp/googleurl.gyp?r1=24464&r2=24463
   M http://src.chromium.org/viewvc/chrome/branches/195/src/net/http/http_network_transaction_unittest.cc?r1=24464&r2=24463

Merge 23965 - Pulling new version of googleurl into the tree.
Fixing a net_unittest case that wasn't updated when googleurl code was changed (but not down integrated to chrome).

BUG=5490

Review URL: http://codereview.chromium.org/174093

TBR=cira@chromium.org

Review URL: http://codereview.chromium.org/174535
------------------------------------------------------------------------

(No comment was entered for this change.)

Coverity found a bug (CID 5991) in that googleurl change:
if (source <= 0x80) {
 should be
if (source < 0x80) {

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=27110 

------------------------------------------------------------------------
r27110 | mattm@chromium.org | 2009-09-24 12:50:26 -0700 (Thu, 24 Sep 2009) | 5 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/DEPS?r1=27110&r2=27109

Update googleurl to 118.

BUG=5490

Review URL: http://codereview.chromium.org/219015
------------------------------------------------------------------------