Issue 4010: Inline autocomplete wrongly autocompletes raw punycode input to
Unicode
http://code.google.com/p/chromium/issues/detail?id=4010
New issue report by [EMAIL PROTECTED]:
See <b\880810>
If you have some Unicode hosts in your history, and you type in e.g. "xn"
into the address bar, you get inline autocompleted with Unicode, which is
totally wrong.
The bug here is that HistoryAutocomplete sets a match's input_location even
when StringForURLDisplay() has fixed up the fill_into_edit into something
that no longer looks like the original user input. A hackish fix would be
to detect and prevent this case. A better fix is perhaps to wait for the
history system to deal with Unicode/punycode issues better internally,
which will hopefully avoid this kind of a case at all.
Issue attributes:
Status: Untriaged
Owner: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Labels: Type-Bug Pri-2 OS-All Area-Misc Area-BrowserUI I18N
--
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
-~----------~----~----~----~------~----~------~--~---
