Thanks for giving my pixels back, browser makers
I'd personally like to offer browser makers my gratitude for realizing that my screen isn't big enough.
I'm one of those people who wants every bit of display real estate I can get. The more I can see of the document I'm writing, the in-box I'm scanning, and the photo I'm editing, the happier and more productive I am.
The maximize button is my friend. Toolbars are my enemies.
So I'm happy to report that browser makers are paying new attention to the issue. It's important to me for reading Web sites, but it's really important to me for the new generation of Web applications. A row of pixels saved once in the browser is returned again with each Web-based application.
Mozilla's ultimate goal is to make the user interface step into the background as much as possible--indeed, the mobile-phone version of Firefox now under development has no visible user interface until it's needed. "Every time a user has to think about how to do something, instead of what we want to do, we as software creators have failed," said Aza Raskin, Mozilla's leader of user interface work.
But it's not simple to redesign the browsers. Users can be confused when interfaces change, some controls are essential, and hiding them can cause problems.
"The challenge to reducing UI (user interface) is in recognition versus recall. People generally use what they see," Raskin said. "How can we provide one-click access to everything possible on the Web without also cluttering the screen? That's a question we are still answering."
Microsoft's case is illuminating. Its Internet Explorer 7 hid the menu bar, though it could be revealed by pressing the Alt key, but IE 8 shows menus by default. (It can be hidden again by default if people choose, and I do.)
Reclaiming real estate
There's been some work in this area for years. For example, hitting the F11 key in Windows puts Firefox into a full-screen mode, hiding title, menu, address, and tab bars. And Microsoft's Internet Explorer 7 hid the menu bar, though it could be revealed by pressing the Alt key; IE 8 shows menus by default again, though it can be hidden again by default if people choose, and I do.
But now the pixel reclamation effort is taking off in earnest. The big statement came in September 2008, when Google revealed its Chrome browser--ironically named because it aims to move the user interface elements, called chrome, as much into the background as possible.
Chrome wiped out the title bar altogether and arrayed its browser tabs in the newly freed space. It also wiped out the menu strip and tucked the options into two drop-down menu buttons to the right of the address bar. Information that would show in a status bar, such as the actual URL of a Web address you're hovering your mouse over, appear in a temporary box that appears on the lower left. When you search a Web page, another small window appears in the upper right. (Chrome looks somewhat different on Mac OS X, which always uses a menu bar at the top of the screen that's detached from the browser Window itself.)
An example of Chrome's latest interface on Windows.
(Credit: Screenshot by Stephen Shankland/CNET)
Chrome on the Mac can't free up the menu bar real estate, so it looks different than on Windows.
(Credit: Screenshot by Josh Lowensohn/CNET)Missing at launch was a full-screen mode, but Google rapidly filled in that gap. This max-screen ethos is one reason that Chrome, at present at least, is my default browser.
Another change came with Safari 4 from Apple. Like Chrome, it added the two-button menu icons toward the upper right. Unlike Chrome, it sports a traditional menu bar as well, though with the Windows version it can be hidden to free up some real estate.
Safari 4 lets you hide the menu bar--but between the beta and final versions, Apple moved the tabs to the more conservative position immediately above the browser Web page.
(Credit: Screenshot by Stephen Shankland/CNET)Unfortunately, in my opinion, Apple backed off from another change between the Safari 4 beta and final version. Initially, the browser sported tabs in the title bar, like Chrome, but Apple later moved them into the more conservative position immediately above the Web page.
The next move comes from Mozilla, which leads development of the Firefox browser.
With the dash to release Firefox 3.5 now over, developer attention again focuses on the future. Last week, mock-ups of Firefox 3.7 arrived to trigger discussions of what the final interface should look like. On display were two Chrome-like characteristics: the two menu icons and the missing menu bar.
Shortly afterward came the Firefox 4.0 mock-ups, moving the tabs to the title bar in one option that's even more Chrome-esque.
This Firefox 4.0 mock-up shows a very Chrome-like interface.
(Credit: Mozilla)One of the big assets Firefox has is its extensions system, which can be used to customize the browser. One I like is autoHideStatusbar, which reclaims the status bar real estate except when I need it in order to see where a link on a Web site leads. I also use Tree Style Tab to move tabs off to the left; I typically need vertical space more than horizontal.
In the same vein, those who were enamored of the Firefox 3.7 mock-up look can try it themselves in the real world with a three-step change LifeHacker put together.
The Web app era
How all these changes will shake out isn't clear yet. But what is clear is that influential developers believe thin frames are better than thickets of icons, menus, bars, and boxes.
The Web application trend is one reason this trend is important.
Consider for a moment Microsoft Word. Especially when the newer version's ribbon of icons is active, it requires a fair amount of area to house its controls.
Now consider Google Docs, which must add its word-processing user interface elements with those already present for the browser itself. Those using the application must bear a double burden. It's like going back to the era of 800x600-pixel displays.
Now factor in the Web application future--Picnik for photo editing, Zoho for office productivity, Bespin for programming, even Microsoft Office soon. These applications are increasing in number, sophistication, and importance, even if they aren't replacing desktop applications as soon as Google Chrome OS developers might hope.
A little bit of screen real estate saved in the browser is multiplied many times over across this range of applications. And of course, conventional Web browsing can benefit, too, offering the possibility of more information and less scrolling to get to it.
It takes real work to pare back a user interface without impairing software's utility. But until the day arrives when my screen is displayed on an entire office wall or directly on my retina, I'll hoard every pixel that browser developers can give me.
Stephen Shankland writes about a wide range of technology and products, but has a particular focus on browsers and digital photography. He joined CNET News in 1998 and since then also has covered Google, Yahoo, servers, supercomputing, Linux and open-source software, and science. E-mail Stephen, or follow him on Twitter at http://www.twitter.com/stshank. 





Peace.
And I'll also say relying on F11 is a deficient solution. It's a extra step that shouldn't be needed. Also makes it harder to switch browser window to the other monitor. For those of us who cherish our screen RE, moving windows across monitors is a big deal.
1) most site/page layouts aren't going to have anything other than pad at left and right, especally if you have a decent sized widescreen monitor
2) what is the point of covering up all your other applications "windows" in a "windows" envirnment. It has a plural noun name for a reason -- More than ONE window. Hiding windows under a full-screen one I find annoying, especially as the shell commands for focus from various applications are implemented differently, causing my alt-tab t not work as it has in the past.
I'm looking forward to more experimental/smaller firefox themes being available, not that Mozilla will make a decent Mac theme themselves but GrApple will soon make up for that
See this post and the associated thread for more details: http://mydellmini.com/forum/mac-os-x/7287-i-miss-fullscreen-firefox-osx-3.html#post84519
The close-box location issue is complicated for Apple. On Mac OS X, the minimize/maximize buttons are on the upper left, so it makes sense to put the close box on the left side of the tab. But of course on Windows the close box is on the upper right, so what should Apple do on Windows? Upper left won out, so it works differently from one OS to another. I don't like the way Safari hides the close box unless you hover over the tab, though.
IE 8 has the same behavior.
FF3.5 has the close button always present, but not highlighted until you hover over it (but is still there).
Let alone when viewing on a crappy screen resolution.
Personally I like having the menu bar at the top of the screen. The amount of realistate it takes is miniscule compared to the overall size of the screen, Complaining about 1/4" on such a large display makes no sense to me whatsoever, especially if you can modify it how you want anyway.
If you don't like it, change it to suit you. Leave us people who like the menu bar alone. If you're using a crappy browser that can't be modified or customized, who's fault is that?
Things for the page are in File, Edit, and View. Things for the app are in File, Edit, View, Tools and Help. There's a button for "Search Web", which just links you to the search bar. There's an "Open Location" button linking you to the address bar. There are print options, which should be in the printer dialog, but are in the file menu. Updates are in "Help". The "Clear Recent History" button is in the "Tools" menu, not the "History" menu.
Still fond of the menu bar?
With Chrome available for people that don't like IE, it seems that Firefox is really just around to serve the people that like the look / feel of IE but hate Microsoft for some reason.
1. Extensions
2. It supported some standards (I'm a web developer)
3. It was faster than IE
I now use chrome because of the simplicity and the speed. Once I got a taste of fast browsing, I can't go back. I also love that chrome updates in the background without asking. It is so annoying when Firefox asks me to accept updates every time I open it.
I use chrome and simply cannot stand to use IE or FF3.5.
Microsoft told me that people started exercising a lot more of what Office can do once it was exposed through the ribbon. Personally, I don't do too much with Office and generally want it hidden. (I also got annoyed that keyboard shortcuts take longer--e.g. to paste special in Word or Excel I now have to type Alt-H-V-S instead of Alt-E-S, and it takes longer to wade through all the ribbon rendering to actually execute the command. (Happily, in Word 2007, I can also set it to paste unformatted text by default now, so that ameliorated the problem.)
Yeah people moaned about it like hell but then people moan about any change in there lives, even if it does makes life easier, quicker and simpler, once you put the ten minutes or so it takes to learn where the new stuff is.
But the real benefits of the ribbon become obvious when you use it on a touch screen device.
It was also the bravest thing Microsoft done in a long time, forcing people to change instead of giving them the choice.
You can find a list on wikipedia: http://en.wikipedia.org/wiki/Category:Tiling_window_managers
It takes time getting used to it, but after that it's har to go back (in my own experience).
> interface elements, called chrome, as much into the background as possible.
Why is that ironic? Why not appropriate or clever or cheekily? Is it ironic because its name calls attention to that which the program attempts not to?
- by PhaseDMA July 28, 2009 9:07 AM PDT
- Good article
- Like this Reply to this comment
-
Showing 1 of 2 pages (70 Comments)