Status: Unconfirmed Owner: [email protected] Labels: Type-Bug Pri-2 OS-All Area-Misc
New issue 5434 by joseph.odoherty: //url.tld resolves to file://url.tld rather than http://url.tld http://code.google.com/p/chromium/issues/detail?id=5434 Chrome Version : 1.0.154.36 URLs (if applicable) : //google.com Other browsers tested: firefox 3.0.4, safari 3.2.1, ie 7.0 Add OK or FAIL after other browsers where you have tested this issue: Safari 3: FAIL Firefox 3: OK IE 7: OK What steps will reproduce the problem? 1. Type "//url.tld" in omnibar. What is the expected result? My expectation from using Firefox is that this would resolve to an http:// rather than a file:// What happens instead? Instead it attempts to load a local path. Please provide any additional information below. Attach a screenshot if possible. I frequently paste URLs in the browser and sometimes the portion before the colon does not get captured because the colon is treated as a separator (putty is notorious for this, for example). This has not been a problem thus far with IE and Firefox assuming that such malformed URLs were for http://, but Chrome makes a different assumption. I can understand the merits of the way that chrome handling things, however, this may break the user's expectations. -- 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 -~----------~----~----~----~------~----~------~--~---
