Comments on: Firefox 3.1 Proposal: Tabs in the Awesome Bar http://www.azarask.in/blog/post/tabs-in-the-awesome-bar/ -- aza | ɐzɐ -- Sat, 20 Mar 2010 23:20:05 +0000 http://wordpress.org/?v=2.6.5 By: stories http://www.azarask.in/blog/post/tabs-in-the-awesome-bar/#comment-6817 stories Wed, 20 Jan 2010 08:47:44 +0000 http://www.azarask.in/blog/?p=105#comment-6817 <a href="http://shilohstover.mysexylog.com/82508/gay+military+stories.html" rel="nofollow">gay military stories</a> gay military stories

]]> By: Paradiesstaub http://www.azarask.in/blog/post/tabs-in-the-awesome-bar/#comment-5946 Paradiesstaub Thu, 01 Oct 2009 19:22:27 +0000 http://www.azarask.in/blog/?p=105#comment-5946 To open an existing tab: text -> down -> enter To create a copy of an existing tab: text -> down -> right arrow -> enter (needs optical feedback) This solution is easy and would fit the goal. To open an existing tab: text -> down -> enter

To create a copy of an existing tab: text -> down -> right arrow -> enter (needs optical feedback)

This solution is easy and would fit the goal.

]]> By: gezjip http://www.azarask.in/blog/post/tabs-in-the-awesome-bar/#comment-5806 gezjip Sun, 23 Aug 2009 08:09:07 +0000 http://www.azarask.in/blog/?p=105#comment-5806 The toilet and this wasdifferent. Like this <a href="http://palaciosimaging.com/comments/index.php?op=ViewArticle&articleId=256&blogId=45" rel="nofollow">katty perry naked</a> worked. The toilet and this wasdifferent. Like this katty perry naked worked.

]]> By: Faraannuape http://www.azarask.in/blog/post/tabs-in-the-awesome-bar/#comment-3744 Faraannuape Fri, 30 Jan 2009 08:12:49 +0000 http://www.azarask.in/blog/?p=105#comment-3744 unprecedented [url=http://www.oneview.co.uk/url/details.jsf?urlId=114905]cialis[/url] forged unprecedented [url=http://www.oneview.co.uk/url/details.jsf?urlId=114905]cialis[/url] forged

]]> By: Mike Lazfsh http://www.azarask.in/blog/post/tabs-in-the-awesome-bar/#comment-2807 Mike Lazfsh Fri, 24 Oct 2008 16:02:12 +0000 http://www.azarask.in/blog/?p=105#comment-2807 Do the first mock-up but drop the instructions to "open in this tab" instruction from the second item. You are either switching to a current tab or opening a URL from your history/frecency. Why add another thing for people to read and understand? Also drop the tab preview because if people want tab previews in their awesomebar they will find an extension that does that to all or some of their awesomebar stuff anyways. Just use the "tab" icon from the users current options menu. Do the first mock-up but drop the instructions to “open in this tab” instruction from the second item.

You are either switching to a current tab or opening a URL from your history/frecency.
Why add another thing for people to read and understand?

Also drop the tab preview because if people want tab previews in their awesomebar they will find an extension that does that to all or some of their awesomebar stuff anyways.

Just use the “tab” icon from the users current options menu.

]]> By: Michael Jacobsen http://www.azarask.in/blog/post/tabs-in-the-awesome-bar/#comment-2711 Michael Jacobsen Fri, 10 Oct 2008 01:20:19 +0000 http://www.azarask.in/blog/?p=105#comment-2711 I want idea 1, w/ tabs searchable using a tab:yourkeyword. I think that way, people that don't want it don't get it. I want idea 1, w/ tabs searchable using a tab:yourkeyword. I think that way, people that don’t want it don’t get it.

]]> By: Philip http://www.azarask.in/blog/post/tabs-in-the-awesome-bar/#comment-2521 Philip Thu, 04 Sep 2008 20:10:26 +0000 http://www.azarask.in/blog/?p=105#comment-2521 It's a great idea. I would collapse designs 2 and 3 by placing "open in current tab (option+return)" in small font, directly under the "switch to this tab". (By the way, "open in current tab" is less ambiguous than "open in this tab".) The advantages of offering both the option to switch and to open in current tab are that the user will know what happened, know how to duplicate a tab, and will not duplicate unintentionally. The drawbacks are that it grows the result list, clutters the display, requires different treatment of blank pages, and (possible drawback) is a new way to duplicate a tab. That the Awersomebar takes so much vertical space, thereby shortening the list of matches, is its only reasonable critique, I think. For example, the "Oldbar [extension] only affects the presentation of the results." That's especially a problem for mobile displays, which are small. How about a 2-column result list or going back to one line per result? Obviously, tabs should be searched in all windows, otherwise the user would have to know which window to search in, which defeats the purpose of automatic searching. Also, there should be a way to show only results matching open tabs. A keyword like "tab:" or "tab" would be discoverable, but using a symbol like "^" would be shorter and be consistent with the default keywords "*", "+", "#" etc. There should also be a way to hide tab matches: "tab-", "-tab" or "-^". Less related: Like Ryan, I have for a while wanted right clicking on list items. That's direct manipulation. And, a direct way to change the order of tabs, by time opened, parent website, time viewed (frecency), domain, etc. would be easier to implement and would require less computer memory than Danielle's design. It’s a great idea. I would collapse designs 2 and 3 by placing “open in current tab (option+return)” in small font, directly under the “switch to this tab”. (By the way, “open in current tab” is less ambiguous than “open in this tab”.)

The advantages of offering both the option to switch and to open in current tab are that the user will know what happened, know how to duplicate a tab, and will not duplicate unintentionally. The drawbacks are that it grows the result list, clutters the display, requires different treatment of blank pages, and (possible drawback) is a new way to duplicate a tab.

That the Awersomebar takes so much vertical space, thereby shortening the list of matches, is its only reasonable critique, I think. For example, the “Oldbar [extension] only affects the presentation of the results.” That’s especially a problem for mobile displays, which are small. How about a 2-column result list or going back to one line per result?

Obviously, tabs should be searched in all windows, otherwise the user would have to know which window to search in, which defeats the purpose of automatic searching.

Also, there should be a way to show only results matching open tabs. A keyword like “tab:” or “tab” would be discoverable, but using a symbol like “^” would be shorter and be consistent with the default keywords “*”, “+”, “#” etc. There should also be a way to hide tab matches: “tab-”, “-tab” or “-^”.

Less related: Like Ryan, I have for a while wanted right clicking on list items. That’s direct manipulation.

And, a direct way to change the order of tabs, by time opened, parent website, time viewed (frecency), domain, etc. would be easier to implement and would require less computer memory than Danielle’s design.

]]> By: Julien Couvreur http://www.azarask.in/blog/post/tabs-in-the-awesome-bar/#comment-2467 Julien Couvreur Fri, 29 Aug 2008 15:57:08 +0000 http://www.azarask.in/blog/?p=105#comment-2467 I love the basic idea and the variants. I'd vode for option 3 as well. One question is how many tab entries would get included in the AwesomeBar results? Also would there be a code to filter only on tabs (similar to the asterisk '*" to keep only bookmarks)? PS: Overall, I see a lot of excitement for the interface design of Firefox, simplifying user tasks and saving time and cognitive energy. That's really great. Thanks Aza, I think you're being a terrific influence on Firefox and Mozilla Labs. I love the basic idea and the variants. I’d vode for option 3 as well.
One question is how many tab entries would get included in the AwesomeBar results?
Also would there be a code to filter only on tabs (similar to the asterisk ‘*” to keep only bookmarks)?

PS: Overall, I see a lot of excitement for the interface design of Firefox, simplifying user tasks and saving time and cognitive energy. That’s really great. Thanks Aza, I think you’re being a terrific influence on Firefox and Mozilla Labs.

]]> By: webmage http://www.azarask.in/blog/post/tabs-in-the-awesome-bar/#comment-2444 webmage Thu, 28 Aug 2008 09:31:45 +0000 http://www.azarask.in/blog/?p=105#comment-2444 I like Alex's proposed solution -- and an option blended into the "awesome bar" to open in new tab. Remember, while we may be firefox geeks, there are quite a lot of users out there who are scared and frightened by keyboard shortcuts. Part of usability is being able to capture these scared cats and make them comfortable with firefox. If no one else, they will be wowed by the magic. I like Alex’s proposed solution — and an option blended into the “awesome bar” to open in new tab.

Remember, while we may be firefox geeks, there are quite a lot of users out there who are scared and frightened by keyboard shortcuts. Part of usability is being able to capture these scared cats and make them comfortable with firefox. If no one else, they will be wowed by the magic.

]]> By: Mike Beltzner http://www.azarask.in/blog/post/tabs-in-the-awesome-bar/#comment-2364 Mike Beltzner Tue, 26 Aug 2008 03:06:21 +0000 http://www.azarask.in/blog/?p=105#comment-2364 Before I forget to tell you anywhere else, whatever UI we choose, it's imperative that we do a switch & refresh operation, not just a switch. Don't worry about form data; that should stay the same. If we have to repost to get content, we can be smart and not do the refresh. Before I forget to tell you anywhere else, whatever UI we choose, it’s imperative that we do a switch & refresh operation, not just a switch. Don’t worry about form data; that should stay the same. If we have to repost to get content, we can be smart and not do the refresh.

]]>