It’s an under-the-hood thing that has zero tangible quality to end users. I’m amazed it has stuck around so long. As I am not a Google Chrome / Chromium advanced user (I still prefer Opera) advanced user, it even doesn’t matter to me, so let the developers have their change. Or tell me: When have you seen someone entering an URI manually, including the schema?Įven if most advanced users won’t like this chance, they will be able to live with it.
![firefox 3.6 download linux firefox 3.6 download linux](https://user-media-prod-cdn.itsre-sumo.mozilla.net/uploads/images/2019-04-17-22-36-36-f278ca.png)
In most cases, the address bar is not for entering information, it’s mostly to show “where you are”, and given the fact you’re using a web browser, you’re on a web site, so is the most common schema for this. If you use the browser to browse something else, for example a FTP directory, the default should be to display the ftp:// schema anyway, regardless of the setting, just to make sure there’s no confusion. In cases where the default is taken, more shortening is possible, up to “– no schema, no slash.Īs you said, boulabiar: Most sites are HTTP anyway. Why hasn’t this been removed, too? (Of course I know what it indicates, but does the average user know – or need to know?) That’s a bit confusing. (The importance to keep the schema with the URI is that the schema is an essential part of the URI, and often programs decide on what specific mechanism to use in combination with a certain schema – remember, there’s more than just HTTP and FTP.)īy the way, have you noticed that the example in the “bug discussion” is shortened to “– you see the closing slash.
Firefox 3.6 download linux how to#
Advanced users know how to switch schema display to ON, so if they intendedly require it, they know where to do it.Īs it has additionally been explained in the linked “bug discussion”, copying the URI from the input field will include the schema, so it’s easy to transfer the URI from the browser to somewhere else maintaining full standard compliance – and standard is to keep the schema. I would rather prefer a static setting through the browser setup – the advantage is obvious: Because the default is OFF, average users aren’t bothered. What are they to be always displayed ? Most of sites are http/https, so removing this and adding a key icon to precise https sites is better. Since 99.999% of the people only ever encounter ftp://, and (did I forget any?), why not create a standard set of easy-to-understand icons to replace them, in cooperation with other browser makers? I mean, if Mozilla and Microsoft can agree on the RSS icon (2005, people, that’s how far back my OSNews memory goes!), surely we can all get along and do something similar here? Most browsers show a lock icon anyway when browsing to an https site, so this shouldn’t be too big of a deal, right? You can cover up that pile of mangled corpses in your bedroom with a flower-patterned table cloth, but that doesn’t actually address the problem of there being a pile of mangled corpses in your bedroom.
Firefox 3.6 download linux mac os x#
It’s like Mac OS X hiding away the UNIX file system layout madness with a layer of kid-friendly directories it only makes things look pretty – it doesn’t actually solve the underlying problem. Hiding complexity is not a solution – it’s just hiding something. That being said, I’m not at all in agreement with the “solution” Google is presenting here. Since computing has been about abstracting away complexity for a while now, it was only a matter of time before browser makers started removing this piece of web history. The reason behind this change is obvious: the URL scheme bears little meaning to most people using a browser – they know it’s there and how to type it, but it doesn’t indicate anything to them. The solution here is decidedly simple: those will still be shown.
![firefox 3.6 download linux firefox 3.6 download linux](https://jarwadi.files.wordpress.com/2010/01/firefox3_6.png)
Another thing that you should be wondering about now is what they do with other schemes like ftp, https, and gopher. Google claims to have solved this issue by adding the scheme to your clipboard when you copy and paste URLs from the URL field, however, this behaviour is currently broken in many clipboard implementations. The first thing that jumped into my mind was this: some applications, whether they be web or real ones, actually require you to add the scheme (for instance, to autoparse URLs). Bug reports were filed, and in true internet fashion, discussion ensued.Ī few things need to be made clear about Chrome’s implementation of this feature. The developer version of Google Chrome takes this a step further, and omits the scheme completely. On Mobile Safari, the scheme is hidden until you tap the URL field to edit. We all know and love Google Chrome/Chromium (and if you don’t, you’re demonstrably wrong), but Google recently made a change in the developer version that ruffled some feathers: the URL field will no longer show the “ This made a lot of people very upset.įor a while now, Mobile Safari has been doing something similar, although I do think in that case, it’s about saving space. Now this is something that I find really interesting.