Issue 2820: Chrome should copy 8-bit escaped URL as well as 16-bit  
characters when copying from the address bar
http://code.google.com/p/chromium/issues/detail?id=2820

Comment #1 by [EMAIL PROTECTED]:
Comments from internal bug:

<brettw>This fails in IE7. It also fails when I copy it to any non-Unicode  
aware app
such as vim or the console. I would really expect to be able to copy and  
paste a URL
to anywhere and have it work.

Firefox does this correctly. It copies the percent-escaped URL as well as  
the text
displayed. If I copy and paste this URL from Firefox 3 (where it works) to  
IE or the
console, it works.

We should probably do the same thing as Firefox. When you select all of the  
URL, it
will add both encodings. When you select part, it doesn't bother.  
Otherwise, we will
have a hard time figuring out what to copy and paste since things will be  
moving around.

It doesn't seem like we need this for beta.

<jshin>I agree with Brett on what to do (copying both IRI and URI to the  
clipboard
and allowing the recipient to pick what they can accept), but I can't copy  
IRI
(http://www.google.com/search?ie=UTF-8&q=上地) from FF3's address bar.  
Wherever I
paste it (FF3's addressbar, FF3's textarea - richedit or not, Chrome), I  
always get
URI ( http://www.google.com/search?ie=UTF-8&q=%E4%B8%8A%E5%9C%B0 )

Hmm... even if we put IRI in CF_UNICODETEXT and URI in CF_TEXT, it appears  
that a
recipient (like console. gvim is fine :-) ) asking for CF_TEXT will always  
get
CF_UNICODETEXT "automagically down-converted" to the default codepage  
("ANSI")
leading to the loss of data (when there's a character not covered) because  
of the
automatic conversion done by Windows. So, it seems that putting URI in  
CF_TEXT will
not help ...

In case of IE7, it seems that it's broken in terms of what it does with  
non-ASCII
characters put in its url bar (whether it's copied&pasted or directly typed  
there),
it converts it to the OS default codepage (rather than UTF-8)  before  
sending it out.
The same was true of IE6.  On the other hand, Firefox (even 1.x let alone 2  
or 3)
always treated what's typed in the address bar as IRI (so that I don't  
understand
what's reported by Xiaolu. I can't reproduce it, either).

<pkasting>Yes, you always get CF_UNICODETEXT if the origin object has it.

I assumed Brettw was saying that we should copy a "link" object (dunno what  
Windows
calls it, exactly) whose title was the IRI and whose URL was the URI.

<jshin>Yeah, that's  what I thought on reading his comment at first, but  
somehow I
couldn't find CF_foo for that in the MSDN (although I'm pretty sure I've  
seen it
before) and copy'n'paste from FF3 behaved differntly from my  
expectation.    If
everybody is sure that there's something for that, there must be :-).   I'm  
still
confused about copy'n'paste from FF3 url-bar, though. aha... drag'n'drop   
works  as
expected.



-- 
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Chromium-bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/chromium-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to