Status: Assigned Owner: pkast...@chromium.org Labels: Type-Bug Pri-3 OS-All Area-BrowserUI
New issue 6795 by pkast...@chromium.org: Messed-up port handling in autocomplete parser http://code.google.com/p/chromium/issues/detail?id=6795 When ParseServerInfo() is given the string "http://a:b";, it marks "b" as a port. Per brettw this is intentional; the parser validates nothing. This comes up via the fixer upper which can hand GURL strings like this to try and decode. The effect on users is that some things that they type in to the omnibox that aren't URLs get marked as URLs even though they can't be opened. Maybe SegmentURL() needs to be able to mark this sort of thing as a failure? Can I call CanonicalizeUrl() or do I want to allow some invalid stuff through? Not sure... -- 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 --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
