Mozilla Labs: The Location Bar Has To Go
conceivablytech.com
conceivablytech.com
Because where did the intermediate users come from? They were novice users who somewhere along the way figured out what URLs were. And part of that learning process is having them staring you in the face every day.
Yes they're geeky. But they're also fucking powerful. And the world is better because we have intermediate users who use them. Not developers, but computer savvy, regular people who seriously make good use of URLs.
Hiding them is a terrible idea. Not until we have a replacement that fixes the usability/confusion issues without throwing away the immense power.
Why have two search boxes when a regular expression can easily and accurately decipher what you are searching for?
Why does having two types of bar add anything but noise to lives of even the most advanced users (of which I include myself)?
The URL bar is a relic akin to the human appendix or tail-bone.
Begone.
this seems like a conniving way to drive more traffic to google.com so people like my parents will then type in the urls they already know into google's search box
Safari could also use the Chrome-style status bar overlay.
I can think of two reasons:
For beginners having 'address is the square box on the left and search is the rounded box on the right' is the sort of simplification Apple likes to bake into their products.
The other is 'The bit of the internet you are looking at is in the square box, and the 3rd party app for search called Google is over there in that rounded box (where it should stay)'.
Both make sense to me if I put on my Apple mindreader hat... although I may be being a bit too cynical with my second reason.
Type a search string into a 'universal' field and hit enter = perform a search.
Type a URL into a 'universal' field and hit enter = go to that URL.
Use some refined heuristics to determine the intention (ala the AwesomeBar in Firefox) and you've got the best of both worlds.
I don't use Firefox/Chrome daily, so I may be missing something, but I don't see why a dual address/search field needs to communicate with Google to be combined.
1. What is the panic with space on monitors? Stop making everything at 1080 widescreen TV.
2. If you cannot read an URL then I guess sending links to others in email, IM, or Facebook is too hard as well. Heck, how are you even going to share the URL? Some kind of drag and drop that people will have to learn even exists?
3. It has more than one mode? Like old TV sets that had a dial to tell you what channel you were on, yet could be set to another channel by turning it? The bar already as been turned into a search, and URL bar. So we already dropped from two entry points to one.
First part: Non sequitur.
Second part: A "copy link" function either as a button or a context menu action lets people do exactly what you described. Still no need to see the url all the time.
However, when I'm on my netbook I do appreciate measures to reduce vertical clutter.
Seriously, we've been doing ourselves a disservice by optimizing monitors for displaying films when 90% of the time we use them to read text.
It turns out if you slide the screen material in the way they do they can slide more screens from the same material.
You can still get other monitors but they are more expensive.
Atleast that is what I heared.
The death of 4:3 is a natural consequence of these facts.
(Now, you could turn it on its side and optimise for reading portrait text, but given the harsh viewing angles of your typical TN panel this needs either an IPS screen or retooling your factory to build portrait panels - which butts against the 'wants cheap monitors' criteria. Technology progresses but not always in the direction you'd like...)
But we're doing the disservice to ourselves when we buy it, so your point still stands.
I registered a lot of complaints over the removal of the status bar text at the bottom of FF4, and the fact that I now have to run an add-on to get that functionality back. It could have EASILY been made an optional element, off by default, but dragged back into place via toolbar customization. As long as you maintain the option to restore classic GUI options then altering the defaults for the 'typical user' doesn't bother me much. But don't remove something entirely and go 'So sorry, too bad.' when it would have been easy to maintain the option.
Hell yeah, that was stupid. I really hate the new one for many reasons, one of which is that I have to search for it whenever I hover over a link. And whey the hell can't I turn it back on???
As usual, Seamonkey keeps what Firefox changed to stupid.
I see "why can't it just be an option?" a lot. Maintaining an option has a cost. Every option introduced in software creates an additional code path that must be maintained, and must be made to play nice with other features and their options. This can add up rather quickly, especially when options have many subtle interactions with other options. It's not about how easy one option is to maintain, it's about how easy all options are to maintain when we decide to add this one.
In the case of the addon, however, the cost of the option is removed from the main code base and the developers who work in it, and shifted to the addon which is (presumably) maintained by developers who care about the feature. In this way, the cost of the feature is distributed over code and development effort that best serves both the users who care about feature in the addon, and the project's user/developer community as a whole. With the only caveat that the addon api must be sufficient, the addon solution is optimal.
There's a mentality that moving a feature to an addon/plugin/whatever makes it a second-class citizen, but I think in most situations, if executed correctly, it's better than trying to maintain it as an integrated feature.
It's as if the UI designers saw a sketch on a cocktail napkin once that really impressed them and now they expect us to use a cocktail napkin for a browser. As if it's all just about inconsequential web surfing and party drinks.
No, no need to care about security or strong site authentication. UI designers have completely failed us in that respect, too, with click-through certificate warnings. This just formalizes it I guess.
Removing the status bar (now requires an add-on) and the menu bar (now requires tweaking about:config) should have been a warning that the people at ML were operating without a clue, but the removal of the address bar goes far beyond just plain ignorance.
Bravo to Microsoft Office, Chrome, Firefox, etc. for abandoning the menu bar entirely in their new versions.
Until there's an option to turn on the menu bar, Office and Chrome (and everything which mimicks their mistakes) have no place on my machines.
But for browsers? I'm genuinly curious what menu bar commands you're hitting in a browser on a daily basis. There can't be that many. Grouping them all under one menu button to simplify things and free up screen real-estate isn't that big of a deal.
Also, eliminating the address bar seems to be a trend among the major browsers, if anything I would expect Firefox to be easier to revert the behavior (see how easy it is to switch back from tabs-on-top, for example).
Basically, here's my beef: I own both an iPhone and a computer with a 30" Dell monitor. They are not even remotely alike. Design decisions aimed at making the browser on my PC look and work more like the one on my iPhone are wrongheaded, misguided, and arguably batshit insane, from the perspective of someone who has actually seen, and in fact regularly uses, both platforms.
Vertical space, for one thing, is not at a premium on my PC. It should not be treated as a resource to be conserved at all costs.
To do otherwise would be similar to proclaiming that all movies must be made for children, because children will want to watch them.
As long as there's an easy way to invoke the url bar, I'll be happy.
Although one thing I'd like, which I've seen no one implement yet is to have links urls as tooltips on mouseover. Perhaps below another tooltip if it existed. Shorter distance to move my eyes.
I honestly can't think of all the implications of how this might change how people interact with the web, but what value is a short memorable domain name (ie: "color.com") if browsers are redesigned to eliminate direct type ins?
Perhaps not as big a deal if the location bar is set to auto-hide, and expand on mouse-over ... but it would really be a tragedy for the industry to disappear.
There are a few domainers on here (Ohashi, Michael Cyger, others?) I'd love to hear some of their comments on how they think the domain industry would change.
However, suitable alternatives would have to be found for common usage patterns associated with the location bar, in particular I can think of the following:
1. Properly displaying your location relative to the structure of a website.
2. Verifying the security and validity of an address you are visiting.
3. Typing new addresses and search queries.
4. Copying and sharing the location you are in.
I can think of a few UI alternatives for each of those use cases and the article presents some others, many would require a pretty big change on the way we do things on the Web.
I have a feeling most of the folk pushing for this have a vested interest in search. Maybe they are just overly eager UX people trying desperately to put a fingerprint on something.
I think it fundamentally arises from the perception they are developing the interface for some kind of idealized idiot/user that doesnt exist. As is usual, software written for "other people" misses the point and just generally sucks.
[touches tip of index finger to his nose]
SSL verifies the hostname of the site you're connecting to, so for SSL to be any use at all, the hostname has to be meaningful and visible.
(I do think you could get away with hiding everything but the domain name and/or hostname by default - the signal-to-noise ratio in the rest of the URL is pretty low anyway).
Also remember this idea first appeared on Chrome. Chrome is developed by Google. Google is a business, that realistically, has a vested interest in users not understanding urls - it means less direct site hits and hopefully more traffic via Google.
It is visible when first loaded and when you change tabs, etc.
I think it is pretty easy to find.
Not a problem on my old 4:3 laptop screen but I dread the time when my current laptop dies and I have to deal with one of those 16:9 models.
Right now I have 1400x1050 but in the future I would have to deal with 1440x900 or 1600x900. The height difference is more than the height of the location bar.
Actually I'd like to own a laptop with a 1400*1200 screen, because I spend a lot of time reading articles and don't care for width.
I would be just fine with moving the url UI elements into a panel, so long as I Never have to give up the the side-toggle widget...
So they leave out the the request parameters and the protocol to dumb it down.
I know this will be inflammatory, but I'm really reaching the opinion that it's time to take a few of the worst of these "image ueber alles" designers out back and, well, play them that provebial violin.
Nothing to worry about
* Back and forward buttons
* Reload / stop button
* Address-bar
* Search/google box
* Three buttons provided by various extensions
* A feedback button, since I'm on a beta.
Let's say they remove the address-bar (and the search/google box). I'll still need a space for the rest of my UI elements. Lets say I dont have those extensions and wasn't running a beta.In that case, I'd still need a place for those back/forward and stop/reload buttons. Or are they going to take those away as well?
I'm not saying it can't be done, but in my (humble) opinion it would mean access to (other) crucial functionality would be severely displaced. I'm definitely not sure I like the direction which all this extreme UI minimalism is heading.
What is does is autohide the whole bar.
All it leaves is the tab bar with the Firefox-button and some kind of Panorama/Tab Candy pull down thingie.
There, I fixed that for you. If you're so upset about breaking conventions, please stop using contractions in your sentences and revert to conventional English. Thank you.
Language changes. Technology changes. This change will bring problems and challenges - as did the contraction ('they're' 'their' and 'there' got a lot worse) but we will solve those problems.
The problem here is that the technology has not changed. We are just trying to hide more of the machine from the operator. This will keep happening until the operator is dealing with such a high level abstraction that they no longer can or will understand the machine. I use the term operator rather than user as that implies less of an understanding barrier.