berkun switches to firefox

| 180 Comments

Last week I switched to Firefox: and I�ve been happy.

Scott points out some of the shortcomings of IE that led him to move to Firefox and goes on to point out some usability issues with Firefox. I wanted to take a second to address some of Scott's concerns about Firefox.

His first criticism is of the Find toolbar's location, at the bottom of the app rather than the top. We tried both configurations and the bottom was the solution that didn't cause the content area to shift down a couple of lines. This seemed much less jarring. We haven't done any serious usability testing on this but we've been following the feedback quite closely and Scott's not alone in this concern.

Scott's second concern is about the download dialog. I think he's asking for the amazing Download Statusbar extensions. For people that do a lot of downloading, this is certainly a nice UI. I use it occasionally. Scott, extensions kick ass ;-)

His next criticism is the new tab not inheriting session history from the previous tab (how IE does for new windows.) Again, this is one of those decisions that we spent a lot of time thinking about and we think we've settled on a reasonable default behavior. Perhaps some formal usability studies would enlighten us but I think that tabs are fundamentally different from new windows and just copying the new window behavior seems wrong too. Fortunately, and once again, extensions come to the rescue. Either Clone Window or Duplicate Tab should give Scott the behavior he's looking for.

Scott's forth issue, that modal dialogs which should be tab modal are app modal, is a bug. It's probably 123913 and we should fix that. It's a pain in the butt.

Scott's final complaint is that Firefox has a Go menu. Indeed. Not only do we have a go menu, but rather than displaying session history like the back and forward button, our Go menu shows global history. He suggests we put it out to pasture. I wouldn't have a problem with that :)

I'm really pleased that other than those issues, Scott, who worked on IE versions 1-5, is finding Firefox to be a better fit than IE. It's even better that he's offering some good feedback. Without high quality feedback, we wouldn't have the Firefox we do today.

Scott, if you're reading this, I highly recommend you give Firefox 1.5 Beta 1 a test drive. It's my daily browser and I find it to be not only faster and more stable than Firefox 1.0.6, but also considerably more polished. Oh, and as for your question on the gatekeepers for UI, that was Blake, Ben, Dave, and me :-)

180 Comments

I couldn't agree more on the Go menu. I have used Firefox as my default browser since it was called Phoenix and I've never touched the Go menu.

I personally really like the location and behavior of the Find toolbar. I think your reasoning about the content moving down being jarring is spot on, and is why I have both Firefox and Safari set to always show the tab bar.

Hide the Go menu with userChrome.css in the profile directory.

menu[label="Go"]{display: none !important;}

:D

Correct, the Go-menu is the most usefull thing ever created.

Funny you mention Download Statusbar. I also think it's a great extension, but I'm not using it since upgrading to 1.5. It was disabled for incompatibility.
Now that you've mentioned it, I clicked "Find updates" in the extensions window, and got "no updates were found for download statusbar".
I thought "oh well, no update yet" - but then I clicked the link you supplied, which is to a newer, "Deer Park" version of the extension.

I don't know why the update mechanism doesn't work, but it doesn't..

Noam.

The only valuable thing in the Go menu is the "History" menu-item, but other than that, the Go menu should really go, because nobody cares.

After posting the comment, I tried installing this update, and it doesn't work. I guess this is why the update didn't want to get it (?).
Anyway:
1. Download Statusbar does not work on FF 1.5.
2. addons.mozilla.org says it does (it says, "Deer Park").

Noam.

There's some good comments over at the blog so I'll be brief.

Find toolbar - kinda good on bottom as when your browsing find results its going down, hence moving the mouse down rather than up, it just logical and easier. Improvements could be made, I suggested Scott try the All in One Search Bar extension which allows the search bar to be the find bar too, which I think would be good if Mofo can develop but simpler maybe.

Tabs not inheriting previous tab history - good point, its session history really is it not, I kinda agree here, but in a sense its simpler now. No major complaints so prob just leave it as is, nice and simple.

Go Menu - this was mentioned here before. It should definitely stay, it was decided to put it in and it was and still is justified. In proper full screen mode it also allows easier navigation, with back, forwards, short history, and a link to full history all still usable. In anycase, it doesnt waste any space anyhow, so there's little reason to just dump it, I'd hate it if Mofo did, it would cause more disruption than any benefit.

Thanks for the response - you folks are cool.

About tabs: I spent more time than I can remember thinking about within browser navigation (moving between bars, panes, whatever). Depending on which group of users you're worrying about, the design conclusions you reach are different. Most of the folks reading this post are at the high end of the expertise scale. The expected behavior for those at the middle of the expertise scale, the majority of people using browsers, is often different. Balancing the needs and expectations is an intense challenge - if you're an expert yourself you can no longer rely alone on your own needs/wants for how it should be, and changes you make to satsify the mainstream crowd often cause the previously friendly experts and early adopters to throw sharp things at you. (tip: you may want to invest in thicker clothing, or make sure your health insurance is up to date).

I'll bet you and a reasonable number of mozilla folks a dinner at the restaurant of your choice that if you do any formal testing with FF with more mainstream users, the current design for both tabs and find will be problematic for people that have never used FF before. One of the secret burdens you have with tabs is designing the feature so that it both teaches people new to tabs how to use it, while still staying smooth and streamlined for those that use it every day.

I'd offer to run a formal study for you myself, but given the bet I just offered I probably should recuse myself. Truthfully, I'd love to run a well designed comparative usability study (IE/FF/Opera) and publish the results. Sadly there doesn't seem to be an open usability community of people volunteering to run usability studies (maybe I just put my foot in my mouth to start one).

Note: this isn't to say that my off the cuff recommendations are right. I think the design challenges for both tabs and the find UI are subtle and I can imagine some % of people having problems no matter how you design them.

There's always going to be a learning curve with new software, and its been made seriously more easier on Firefox than on any other browser, of software. So things cant just be changed to work like IE. It all has been studied hard and tested, and there's been no real complaints even from basic users. Specifically on the find toolbar and tabs, I think the find toolbar is far easer and intuitive than IE's or any other browsers, my mum can understand it, but even more advanced users have never gotten used to IE's find feature.

On tabs, in some area's maybe, but again its been studied and tested well with not serious complaints. When there are theyre taken seriously. But its not been done half heatedly or in a naive sense, it works now, things will improve. To an extent the bets not specific enough as there's always problems to an extent with a minority. If you mean it would be problematic for a majority of users on the other hand - well no serious numbers have problems now or complain, and any novice users I know understand and learn it all very well ;)

Berkun wrote:

Sadly there doesn't seem to be an open usability community of people volunteering to run usability studies

Openusability.org; I believe it was inspired by ESR's essay "The Luxury of Ignorance" (which begat part two, which begat The Art of Unix Usability)

Maybe you'll also find talking to ESR to be rewarding. Maybe....

Scott, what are your thoughts on tab overflow UI? Right now we simply don't (tabs are lost when they exceed the available space). I initially liked IE 7's implementation -- the stubby tabs at each end which behave as a tab and as a scroll mechanism but after using it for about a month, I'm a lot less happy with it. The other options we've considered (and rejected) are scrolling from each end -- with actual scroll arrows, tab oveflow with chevrons and menus at each end, and tab wrapping so that you get another toolbar of tabs when the first fills up. All of these seem to have pretty serious shortcomings when you think about trying to locate a specific tab or what happens to the rest of the tabs when tab switching.

If you've got any suggestions, I'm definitely interested.

- A

I think the rationale for the Go menu is for accessibility: all toolbar icons should have a menu equivalent. IE5 and later makes the Go menu a submenu of the View menu. Opera 8 (I don't have earlier versions to test) seems to have ditched the Go menu completely.

One way to help tab discoverability is to put the new-tab button on the toolbar by default, to the right of the search bar (all the way on the right side of the toolbar). This puts it directly above the close-tab button, making the tab controls "all in one place" and adjacent to the maximized screen (Fitts' Law). The close tab button also needs a tooltip: "Close the current tab." It would also be nice aesthetically, IMHO, if the close-tab button were equal in width to the new-tab button and looked like a red X over a tab (instead of a "hey, what's this X thingie do?").

On tab overflow: I'd start by trying to come up with a profile for who's using 15+ tabs and what they're doing. Is it mostly from people doing "open in tabs" off of a bookmarks folder? Is it from people who do Cntrl-T for most new link clicks? I'd want some idea of the common usage patterns that get people into an overflow state. If I had data for this great, if not I'd hypothesize: "The 5 common usage patterns related to tab overflow".

Then I'd be able to make a list of the different UI widgets for overflow management. In the universe of UI there's only 7 or 8 ways to handle this: scroll, dropdown, submenus (magically collapse tabs into tab groups), orient them vertically (might fit more that way), and on and on. I'd riff for awhile on alterantives (preferably in a room with beer, a whiteboard and other designers), and dig into twists on the basic 7 or 8 ways.

But I wouldn't decide which way to go (or prototype) until I applied that hypothesis of usage to the different possible widgets. I should be able to take that hypothesis and imagine which designs would serve which kind of usage best, and in doing that comparison (usage model to widgets) I'll probably find new twists and tweaks I hadn't thought of before. But using the usage model I'd be able to easily see the strengths and weaknesses of each alternative.

I realize I'm telling you how I'd do it, and not doing it, but the former takes less time (although the later wouldn't really take all that long) and at the moment less time is all I have :)


"I personally really like the location and behavior of the Find toolbar. I think your reasoning about the content moving down being jarring is spot on, and is why I have both Firefox and Safari set to always show the tab bar."

My feelings exactly.

Granted that the Go menu is a little peculiar (and therefore maybe not optimum), it does serve an almost essential role at present. Did you ever close a tab by mistake? Yes, I can find the last site from the History, but many users will have a hard time thinking of that and setting the view correctly. On the Go menu it's right there (i.e. discoverable).

When you figure out how to undo closing of the last tab, then maybe the Go menu could go. You could put the history in the View menu.

Even before reading the above comments I was going to say I would agree with Scott on the Tabs behavior in particular. Things like the Go menu's existence I've not thought of consciously - it's not bugged me. But a new tab (created by middle/ctrl/right clicking a link) inheriting the initial tab's history has always seemed intuitively useful to me (this also counts for new windows). I've found myself scratching my head at times over the years wondering why that behavior still has not arrived.
I believe such behavior would only affect usability positively.

@Greg, I agree on the tooltip, I never realised the tab close button didnt have one and see no reason why it shouldnt tomorrow, the tooltip of close current tab is perfect too . Asa, comments?

I also think it needs to be easier to close an un-current tab. Right clicking any tab, the close tab button should be at the top of the list rather than the bottom, or at least just more obvious. Its not obvious now, meaning people click on a tab, then click the close current tab button, then return to they're previous tab they were on - very long winded and un-necessary.

A add tab close button to all tabs is a sensible option to consider too rather than just in an extension. This does make tabs even more intuitive, easier to understand and use, as the user can see the close for that page, so know if they click its close button, it will close that page/tab - as with Opera.

Open a new tab button by the search bar though, no way. That would be really ugly and confusing looking. Right clicking a current tab has add a new tab button, and of course in file menu which is fine. User can also very quickly and easily add the new tab button to the navigation bar, so it doesnt look seperate, isolated, and yet another thing to learn. I have open a new tab button next to the home button, aswell as print!

As for tab overflow:
How about grouping tabs from the same domain into one tab like Windows XP does with multiple instances of a program in the taskbar. It's not an infalable solution but it can lessen the occurance of the problem. But then there are two things that need to be decided:
1) How do you know a tab is a group holder? I'd say the least you can do is show the domian and the number of pages in the group. e.g. mozilla.org - [5] And mabye show a down arrow on the favicon like was done in the search bar.
2) How do you access the pages in that group? I'd say you left click on the tab and get a drop down menu of the pages in the group. Focusing the current tab is what happens if you left click on the current tab in 1.5. That behavior can be done instead on double click. Or you only get the drop down menu by clicking on the favicon.

Regarding the Go menu, instead of removing that piece of code altogether it could be used elsewhere (I mean, _somebody_ must use it after all this time, right?).

The Go menu could instead be popped up when you right-click on the Go button next to the location box. The location box doesn't seem to sort by last-visited so the Go menu would be handy to have lying around. This would be consistent with the lists that pop up when you right-click the Back and Forward buttons. Just an idea. Hope this is an appropriate place to air it.

The Go menu still does show a handy recent history, but the Go menu in Thunderbird is completely pointless. It has three items: Mail Start Page, Next, Previous. I think people can navigate their messages with arrow keys, and why would anyone want to go back to the Thunderbird start page?

I had never realized that the Go menu could be used as an "unclose tab" feature (thanks, AnotherGuest!); here is yet another reason to keep Firefox's Go menu.

Overall, there are very few changes I would make to the Firefox UI (and the little pet peeves I have can mostly be resolved with extensions). It's the Thunderbird UI that needs work.

It's also nice to see a good What I Like And Dislike review of Firefox that isn't from an Opera fan, or a Maxthon fan. It's from someone with some sense. He makes good points...if only Mozilla would listen more to my bugs and requests (I know, I know, you get a ton), I'd be happy ;-)

regarding tab history, it's be interesting to test out implementing the 'back' operation when there's no history in the current tab, to swithc tabs back tot he tab that was used to open the current tab (if one exists).

For example, I just tabs a ton when I open up a news site with 10 stories I want to read, I just middle-click each story link. If 'back' in those new tabs took me back to my original tab (if it was still open) that might be interesting.

On the other hand, I can see this causing me to have a ton of useless tabs open if I go back to the main tab instead of closing my current tab.

I like the Find Toolbar on bottom. I think it's slightly disorienting for new users as it's kind of in your peripheral vision, but that also makes it unobstrusive once you get used to it. If it were at the top it would either shift content (definately jarring!) or obscure the top portion of the page where I'm likely to be looking at something. I'm almost certainly *not* looking at the bottom 20 pixels of the window. The most important thing, though, is that the toolbar is not a floating dialog that obscures part of the thing I'm searching!

I agree that it would be very nice if opening a link in a new tab copied the history.

@Noam: The download statusbar extension works in 1.5 beta: I know because it is active in my list. You can check for updates by opening up the extensions window and click on "find updates".

I kind of agree that the Go menu is kind of pointless, though it is needed for accessibility purposes. It wouldn't be a bad idea to move it all under the View menu, since you are, in fact, viewing pages or recent history.

Regarding tab overflow:

I regularly work with many tabs open simultaneously (10+, often 20 or more). I'd call the usage pattern "working set" -- they're the pages (web email, news sites, etc.) I find handy to have readily available, either because they change frequently or because I'm not able to digest their contents in one browser session. (The SessionSaver extension is a great tool for this usage scenario, since I don't have to worry about losing state on all my tabs if I have to close the browser or if a new FF update comes along and requires a restart.)

One possible approach to the tab overflow problem is to mimic the behavior of the Mac OS X Dashboard widget: the input device (mouse or keyboard) identifies a coordinate along the axis that the tabs are aligned upon, and in this region the tabs are given enough separation/magnification to be able to distinguish their titles. Outside that range, the tabs could crowd together as much as is necessary. Sliding the "uncrowd range" along the line of tabs would enable the user to locate the desired tab quite quickly, I think.

"Sadly there doesn't seem to be an open usability community of people volunteering to run usability studies (maybe I just put my foot in my mouth to start one)."

I haven't really looked at it but what about http://www.openusability.org ? Seems to be just what you are describing.

I disagree on your comment about tabs, Scott. Every "mainstream" person I have switched to Firefox raves about the tabs. They are very discoverable and well-implemented.

And these are not geeks in any sense of the word. They are people who think the internet and that blue "e" are synonymous. They sometimes have a bit of a learning curve with various of FF's features, but tabs isn't one of them.

Gah, points number 2 and 3 I've talked about twice on this blog, once on Blake's and on the wiki too. I'm not typing it up once more for an idea I've had for a year.

http://wiki.mozilla.org/Talk:Firefox:3.0_Tabbed_Browsing#Why_not_use_the_back_button.3F

http://wiki.mozilla.org/Firefox:1.5_Download_Manager

Please Read x_x

Tab overflow:

Just from my own experience. Do not do anything different. I usually avoid getting tab overflow problem by "grouping" related tabsets into separate windows. So I have for example a set of tabs woth mozilla-related blogs and stuff in one and Eclipse related things in a different window and news entirely in a separate window. This means I do not arbitarily just create tabs but instead I try to minimize the clutter and organize my tabs by topic.
I agree that this is not the ideal solution for everybody - more like a workaround but if that forces me to better organize my browsing, I am not complaining.
One thing though that I've missed - sometimes I open a tab and wish to "detach" it into a new browser window - session and all... In 1.5 I can drag tabs to reorder them - wouldn't it be nice if I could also drag them out of the browser window to form a new one.

On the other hand - I am using Eclipse in my everyday work and they have a nice feature - they have a chevron menu for tabs that overflow and a keyboard shortcut (Ctrl+E on Windows) that opens up the menu for the chevron showing a list of all tabs (titles). You can then either navigate to the desired tab with arrow keys or you can start typing the title of the tab and it will automagically filter the list according to the text you've typed.

This is by far the best tab overflow solution I've seen so far, as it presents all available tabs in a single list, so if you just want to go to that tab having "Python" in the title - you can just type "Python"[]
and you are there... also - if the titles of the tabs are squeezed together to the site icon size - through that chevron You will still be able to navigate the list of tabs with full (or at least recognizable portion) of the tab title.

just my few cents

Asa, I wonder if the question we should be asking wrt tab overflow is not "What's a way to make an obscene number of tabs a joy to use?" -- which may well have no really good answer -- but rather, "Is not the current non-solution of the ui looking broken on tab overflow worse than any of the suggested minimal overflow solutions?" (minimal as in not changing the behavior of the non-overflowing case).

Also, tab grouping by e.g. domain, while useful to reduce tab crowding, is actually not at all a tab overflow solution.

I think the search bar is ok where it is. I would like to point out though that it currently doesn't cause the page to jar upwards when opened, so I don't see why it can't go at the top of the page and not jar the page downwards, which is the main worry put forward to justify why it should stay at the bottom. What would be nice to see is a button for find. Clicking it once should open the find bar, clicking it again should close it (not all buttons act this way, like the download button for instance). As it is the only way to access it is through the edit menu or by pressing CTRL-F (which pressing again does not close the bar).

You know what ? You're right ! Firefox _has_ a Go menu ! I never noticed it before !

About the Find menu:
I don't really care position. But there is one thing that I feel really annoying: when you press "Find Next" or "Find Previous", the text found is always at the top or bottom line. It's not very convenient, as often I have to know the 2-3 lines up or down to know if it's what I'm looking for...
I strongly suggest that you left a gap of 2-3 lines between the matched text and the top/bottom.

With regards.

I'd love to see that some of the more popular extensions eventually get integrated into the firefox build. Extensions are great, but your general user isn't going to go looking for them.

Some of the first I'd recommend for inclusion in Firefox proper: tabbrowser preferences, download statusbar, and go up.

Like Roland, I tend to group my tabs into separate windows when it looks like I'll have too many open at a time. More useful than a tabs overflow UI for me would be an addition to the context menu on the tab to be able to move it to a different window.

Close buttons on each tab make sense from a UI perspective as they identify exactly which tab is being closed. However when I've used extensions to get this functionality in the past I've found myself closing tabs I didn't mean to due to sloppy mouse positioning when I click. This becomes even more of an issue with lots of tabs, as the target area to bring a tab to the front shrinks, but the target area for the close button doesn't - increasing the likelihood of hitting a close button by mistake.

Hi all,
in fact, I *do* use the 'Go' menu, for a very simple reason. I occasionnaly close a tab by mystake, and sometimes, the 'Go' menu allows me to re-open it without going through the Session history, which is sorted by alphabetic order and not chronologic order (and sometimes I don't remember the exact title).
What about an 'Undo close' feature ?

Um..... Middle-click is your friend. Middle click to open tabs. Middle click to close tabs. Middle-click-click-click...

For an interesting approach to tab management -- and actually, an interesting approach to a lot of browser UI issues -- it might be worth looking at the OS X browser OmniWeb. It maintains "tabs" as thumbnails of pages in a vertical column on one side of the browser window; you can re-order the thumbnails, drag bookmarks into it to open pages in the background, double-click on a thumbnail to open it in a new window. (And, in that paradigm, a scrollbar down the thumbnail window when you have overflow makes perfect sense.) I'm not sure what lessons might be drawn from it for a more conventional tabbed browsing UI, but it addresses nearly every issue people have with tabs in the most elegant fashion I've seen yet.

http://www.omnigroup.com/applications/omniweb/

Regarding tab contexts, how about having a new tab show up with a button that you can click on to retrieve the context of wherever you came from? I rarely want a copy of the previous context, but such a button would be useful for those times when I do.

true about the go menu.
Haven't really noticed it, though I may have used it for the history navigation which thinking of it.

Furthermore, I think in the past it was possible to shrink the file - edit - etc.. menu so it only displayed file and an arrow to see the rest. For those of us who have removed the navigation and bookmarks toolbar and moved all toolbar content to a single toolbar, we could do with the extra space up there again.

and Asa, thanks for always taking the time to participate in discussions on slashdot etc and reading up.. You truely deserve your paycheck.

About tab overflow:

K Desktop Environment has a nice feature that allows you to switch between mutable desktops. My suggestion is to use a similar approach to solve the tab overflow problem. To have a tab that switches between mutable tab groups. You could, of course, move tabs between these groups simply by dragging the over the group tabs. Of course these group tabs would have to be in different colour than the tabs

The downside to this is that this might be a little complicated and confusing to the average user.

Regarding tabs:

every person I've introduced FF to has been confused at first by tabs. It seems the more computer illiterate the person, the less likely they are to understand the behavior. In fact, many people I've introduced FF to shy away from tabs entirely.

I, for one, don't understand some things with tabs either.

For one: The default behavior when multiple tabs are open and you shutdown windows is that you have to deal with the "are you sure you want to close multiple tabs" dialogue box. I can understand this feature when not shutting down a system, but it's really a nuisance at shutdown time. Either make the warning non-default or make shutdown time an exception.

Second: The blank tab opening is lacking. I don't personally care about the history, but it should open a user's home page at the very least. Is there any person out there who would want a new window to open a blank screen rather than their home page? I don't want opening my homepage in a new tab to be a 2 step process. IMHO that's one of the biggest failings of FF.

Um..... Middle-click is your friend. Middle click to open tabs. Middle click to close tabs. Middle-click-click-click...

Agree wholeheartedly. That's the first option I turn on in a new Firefox install - Middle-click opens and closes new Tabs. It's great, and I wouldn't change a thing other than making that the default option (when you click on a link and not in open space - the Autoscroll is great, too).

About the Overflow concept, having a little double-arrow that you click which gives a single-line for each Tab that you have open might be decent. I tend to operate with about 10 Tabs open before it gets confusing. After 10, it's a game of Click, Click, Click before finding the right page again.


Overall, great job on Firefox & Mozilla. I use both all of the time.

Really like the location of find. Please keep it. It is less jarring, and somehow so handy and unobtrusive.

The go menu could die. I didn't realize it was even there entil this came up.

Download statusbar is a good point.

Tab model another good point.

Second: The blank tab opening is lacking. I don't personally care about the history, but it should open a user's home page at the very least. Is there any person out there who would want a new window to open a blank screen rather than their home page?

NO!!! Leave it be. I'm that 'person out there' that wants a blank page. I typically set my Home Page (at least when I have to use IE) to "about:blank". I could see it being another option in the Preferences, though. I'll typically have my home page open in the first tab, so why would I want it open again?

Here's my stab at the tabs issue: Overlap tabs, but show all of the tab the mouse is curently over - a horizontal rolodex metaphor seems quite simple to understand. This could also be seen as a cleaner version of the 'floating tooltip' that currently shows the full title of a tab, but appears too slowly to be effective when searching through multiple tabs.

An option to show/hide the 'Go' menu would fit nicely in preferences->privacy. I think it should default to 'hide' too.

Why not put the 'find' dialogue where URL bar is? If I want to find something on this page, I don't want to go somewhere else, so I don't need to type a URL right now.

My personal beef with the Find dialogue is one not mentioned so far, It's not toggleable with the keyboard (or if it is, it's not obvious how I do it!). Everywhere else that there is a 'close window' button, I can ctrl-w to close it, the find dialogue breaks this, you lose the current page if (like me) you expect ctrl-w to close the last thing you opened.

My one complaint with the find window is that it doesn't remember that you've clicked "highlight".

I often want to view multiple pages with a certain term highlighted, but I have to re-click "highlight" every single time in spite of the fact that it remembers my search choice.

Good reply to a good article.

I frequently run into the tab-overflow situation. In my case it's no bother at all since I am simply popping 30-100 tabs off links in my current page and then viewing then closing them in that sequence. Roland Tepps mention of a menu that appears next to the close tab button containing a menu of all tabs (but only under an over-flow situation) might come in handy on occasion and is quiet enough to not disturb.

Quick n dirty of what I do: Open 100 links in tabs off current page, ctrl-tab to first new tab, ctrl-w all the way through 99 tabs after digesting page content.

In my case the page titles mean nothing to me and would provide zero information. The page content is the only thing of merit.

For those of you interested in the specific useage, it's stock research.

I like the fact that open new tab brings up a blank page. I use it all the time when I'm entering or pasting a URL. If you want your home page by default when opening a new tab, perhaps there should be a setting for that. You can always middle click the Home icon for that behaviour, FWIW.

Monthly Archives