Patent Grant
8631341
This document generally relates to browsing software, and more particularly, to tabbed-browsing software.
Browsing the World Wide Web (the web), the graphical portion of the Internet, has become quite popular in recent years. A software program, commonly referred to as a web browser, or just browser, provides an easy-to-use point-and-click interface for accessing various content on the web. Upon entering a web address or URL of a particular website, the browser requests web pages from a web server hosting that website. The browser then interprets the web pages and displays the content on a display. The web pages include hypertext and hyperlinks that, when selected, cause the browser to request additional content associated with them. By selecting the hypertext and hyperlinks, a user may conveniently navigate through pages of information—commonly known as browsing or surfing the Internet.
Each time one of the hypertext or hyperlinks is selected, the new content is downloaded into the current window. Depending on the network bandwidth, this may cause a brief to extensive delay. For convenience, additional windows may be opened to view multiple web pages. However, after opening several web pages, each in its own window, the taskbar may become quite cluttered. This makes it difficult to re-locate a particular web page. Tabbed browsers have been introduced to help manage the viewing of multiple web pages.
Tabbed browsers load web pages in “tabs” within the same browser window. Therefore, only one item appears on the taskbar, even though multiple web pages are loaded. New tabs may be opened via a hotkey, a context menu item on a link or the like. The new web page downloads in the background into the new tab. This allows a user to continue viewing the current web page without automatically switching to the other web page. At any time, the user may click on the associated tab and view that web page. Tabbed browsing makes it easier and more convenient to view multiple web pages. However, when multiple tabs are open, users may experience difficulty switching between them.
The present mechanism further enhances the tabbed-browsing experience, especially with selecting one out of a large set of open tabs.
The techniques and mechanisms described herein are directed to a method for managing and selecting one out of several open tabs in a tabbed browser. Briefly stated, browsing software is configured to provide a quick pick user-interface that visually displays the several tabs. The quick pick user-interface displays a rich set of information for each tab, such as a thumbnail, meta-data describing each tab (e.g., title) and/or other adornments. The thumbnails allow a user to easily distinguish between each opened tab. The browsing software may also be configured to recognize a user selection from within the quick pick user-interface and in response, switch back to the tabbed window view and display the selected tab in that view. The browsing software may adjust the tab row so that the selected tab is positioned in a favorable position within the tab row. In addition, within the quick pick user-interface, the user may reposition the thumbnails and/or close the thumbnails, thus affecting the associated tab in the tab row.
Non-limiting and non-exhaustive embodiments are described with reference to the following figures, wherein like reference numerals refer to like parts through-out the various views unless otherwise specified.
Briefly, the techniques and mechanisms described herein are directed to managing and selecting one out of a large set of open tabs within a tabbed window displayed by a browser. A quick pick user-interface is provided that visually displays a rich set of information, such as thumbnails, meta-data describing each tab (e.g., title) and the like. The thumbnails may be selected and/or moved within the quick pick user-interface. Upon switching back to the tabbed window view, the tab row and the contents of the tabbed window are modified based on the interactions that occurred in the quick pick user interface. The following discussion describes the quick pick mechanism within a tabbed browser that supports tabbed-heterogeneous windows. However, after reading the following description, one skilled in the art could incorporate the quick pick mechanism into other types of tabbed browsers. As will be described in more detail below, the present quick pick mechanism provides a convenience that was unavailable until now.
Exemplary Computing Environment
The various embodiments of the quick pick mechanism may be implemented in different computer environments. The computer environment shown in
With reference to
Computing device 100 may have additional features or functionality. For example, computing device 100 may also include additional data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, or tape. Such additional storage is illustrated in
Computing device 100 may also contain communication connections 122 that allow the device to communicate with other computing devices 124, such as over a network. Communication connection(s) 122 is one example of communication media. Communication media may typically be embodied by computer-readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. The term computer readable media as used herein includes both storage media and communication media.
Various modules and techniques may be described herein in the general context of computer-executable instructions, such as program modules, executed by one or more computers or other devices. Generally, program modules include routines, programs, objects, components, data structures, etc. for performing particular tasks or implement particular abstract data types. These program modules and the like may be executed as native code or may be downloaded and executed, such as in a virtual machine or other just-in-time compilation execution environment. Typically, the functionality of the program modules may be combined or distributed as desired in various embodiments.
An implementation of these modules and techniques may be stored on or transmitted across some form of computer readable media. Computer readable media can be any available media that can be accessed by a computer. By way of example, and not limitation, computer readable media may comprise “computer storage media” and “communications media.”
Exemplary Architecture
Thread boundary 230 represents a boundary between a single thread (i.e., a frame thread) that handles the processing for the components shown to the left of thread boundary 230 and multiple threads that handle the processing for the components on the right of thread boundary 230. Each instance of content window 202 is associated with at least one of its own threads. That thread also handles the processing for the associated toolbars/menus 204, custom bars 206, status bars 208, and content 210.
By having multiple threads, at least one for each content window 202, the architecture prevents a potential bottleneck caused by having only one thread handle the messages for all HTML rendering across the multiple tabs. In addition, having multiple threads reduces the likelihood of unnecessary delays or timeouts when downloading web pages. Having multiple threads also makes the architecture more resilient because if a tab hangs, only one tab hangs instead of potentially hanging all of the tabs. This is in contrast with other tabbed browsers that host their tabs on a single UI thread. In these tabbed browsers, the entire application hangs when a single tab is blocked. Each individual thread may be prioritized.
Each of the components in architecture 200 is now described. As mentioned above, each content window 202 is associated with its own toolbars/menus 204, custom bars 206, status bars 208, and content 210, as needed. For example, if there are five tabs open, five instances of each add-on (e.g., custom bar, toolbar, etc) are created and hooked to their own content. Similarly, if menus or status bars are modified via internal logic, HTML, document hosting, add-ons, or the like, the menu or status bar associated with that content window 202 is changed. The add-ons and the content window 202 operate in a well know manner. Because the add-ons do not know about tabs, the architecture 200 does not modify the operation between the add-ons and the content window. Instead, the architecture wraps each set of content windows into one browser frame 214. While not shown, there may be multiple browser frames 214, each with a set of tabbed-heterogeneous windows.
Content window 202 maintains state for the content window, such as size, position, visibility of frame elements, and the like. The state may be persisted into a stream when the tabbed browser closes, and then may be read when a new content window is launched. Alternatively, the state may be saved in a registry and read from the registry when the new content window is launched.
The tab window 212 lives on the frame thread. Each tab window 212 is configured to manage communication between the outer frame components (e.g., navigation bar 216, browser frame 214, etc) and an individual tab. The tab window 212 holds pointers to its associated content window 202 and interfaces so that it can manage cross-thread communication between the outer frame components and the individual content window 202. The cross-thread communication may involve cross-thread calls. In one embodiment, calls from the browser frame 214 to the content window 202 may be asynchronous. The tab window 212 is then responsible for marshalling the parameters and posting a message to the main window of content window 202. In contrast, calls from the content window 202 to the frame browser 214 may be synchronous. The tab window 212 is then responsible for marshalling the interfaces of the corresponding tab window 212. The tab window 212 may also convert synchronous calls into asynchronous calls in order to reduce the likeliness that a tab will hang.
The tab window 212 may also cache a limited amount of state. This allows the tab window to provide a quick synchronous lookup of state to other components. When the tab window 212 receives an event from the content window 202 that modifies the state, the tab window propagates these events up to the tab window manager 220.
In addition, the tab window 212 exposes several operations that can be performed on a tab, such as destroy, set visibility, set size, set position, and order. The tab window 212 also exposes operations that the frame needs for asynchronously invoking a tab. These operations may be exposed via individual application programming interfaces (API) or through a generic API. For the present quick pick mechanism, each tab window 212 may have its own set of characteristics. For example, one of the tab windows may be a quick pick window which has a different navigation characteristic than other tabbed windows. As will be described and illustrated in
The tab window manager 220 hosts multiple content windows 202 via multiple tab windows 212. The tab window manager 220 manages the overall state of each of the tabs. The state may include: a top level URL; a page title; a back/forward button availability; a favorite icon for the current page, a progress state for the current page, security information reflected in the user-interface (e.g., HTTPs info); and the like. The tab window manager 220 may synchronously query the tab window 212 for per-tab data. In addition, the tab window manager 220 manages the operations performed on the tabs, such as open, close, select, move, set size, set position, set order, and the like. This is achieved by accessing the operations exposed via the tab window 212.
The browser frame 214 hosts the navigation bar 216, frame command bar 218, tab window manager 220, and the tab UI 222. The browser frame 214 may also directly or indirectly host a rebar control (not shown). The browser frame 214 brokers communication between these hosted components.
The tab UI 222 is configured to render the user-interface for the collection of tab windows 212. As will be described later in conjunction with
The frame command bar 218 provides a set of commands that have been determined to be the most useful. By having this set of commands readily available for any tab, a user can conveniently locate one of the commands for any tab.
Exemplary User-Interface
The tabbed window 312 includes, a tab band or tab row 320, one or more tabs (e.g., tabs 332-342), and content 360 associated with the tab currently in focus (e.g., tab 336 shown in
In accordance with the present quick pick mechanism, the tabbed browser provides a mechanism for accessing a quick pick user interface. The mechanism may be a quick pick button 350, a context menu selection (not shown), and/or the like on the user-interface 300. The mechanism may also be a hot key (not shown) entered through a keyboard. A user may select the quick pick button 350 to access the quick pick user interface.
The navigation bar 302 may include an address bar 304, a back button 306, a forward button 308, and a search box 310. The content of the address bar 304 may be maintained for each tab. Thus, when “clicking” through the tabs 332-341 the address bar 304 may display the address for the currently selected tab (i.e., the tab in focus). The search box 310 allows text to be entered and searched for in the currently selected tab.
In one embodiment, items in the user-interface 300 that are per frame include the navigation bar 302 and the tab band 320. Items in the user-interface 300 that are per tab include content 360. In one embodiment, content 360 may include different type of data sources. For example, content 360 may be a web page, a shell folder, a navigation based application, and the like. This heterogeneous content may be hosted in a single frame. In another embodiment, the content 360 associated with each tab may all be web pages.
Each thumbnail may include a close indicator (e.g., close indicator 420). If a user selects close indicator 420, the corresponding thumbnail (e.g., thumbnail 411) is removed from the quick pick window 460 and its associated tab (e.g., tab 341) is removed from the tab row 320. In addition, the rich set of information may include a page title or other adornment for each item in the quick pick window 460. When a user hovers a pointer (e.g., pointer 422) over one of the thumbnails (e.g., thumbnail 410), the thumbnail 410 may visually change appearance, such as changing its color. In addition, the tab (tab 440) associated with the hovered thumbnail 410 may change its appearance, such as changing color, bolding text, and the like. The user may select any one of the thumbnails to view its corresponding content in the tabbed window.
Exemplary Operation
State 1004 may occur from state 1002. At state 1004, the tabbed browser adds a new tab and changes the in focus tab to the new tab. In addition, the tabbed browser may visually remove some of the tabs displayed on the tab row if the addition of the new tab makes the number of tabs in the tab row more than a pre-determined number. After the new tab is added, the state transitions back to state 1002.
State 1006 may occur from state 1002. At state 1006, the tabbed browser responds to the user's selection of a tab or overflow indicator. The tabbed browser adjusts the in focus tab and adjusts the tabs that are displayed on the tab row accordingly. After the tabbed browser handles the user's selection, the state transitions back to state 1002.
State 1008 may occur from state 1002. State 1008 is responsible for handling the present quick pick mechanism. From state 1008, several transitions may occur.
State 1010 may occur from state 1008. State 1010 exits the quick pick mechanism, such as via a close button on the quick pick user interface. From state 1008, the tabbed browser transitions back to state 1002.
State 1012 may occur from state 1008. At state 1012, the tabbed browser closes a thumbnail in response to a user's action within the quick pick user interface. For example, the user may have selected a close button 420 within the quick pick user interface. Upon closing the thumbnail, the tabbed browser may also perform other operations associated with closing the thumbnail, such as removing the associated tab from the tab row, deleting the associated tab window, and informing the tab window manager that the associated tab window is no longer open. After the tabbed browser handles closing the thumbnail, the state transitions back to state 1008.
State 1014 may occur from state 1008. At state 1014, the tabbed browser may rearrange the thumbnails in response to a user's action within the quick pick user interface. For example, the user may have selected one of the thumbnails, dragged it to another location, and dropped it next to different thumbnails. The tab browser will change the order of the thumbnails displayed in the quick pick user interface. In addition, the tab browser will change the order of the tabs within the tab row to reflect the re-positioned thumbnail. After the tabbed browser handles the re-arranging of the thumbnails, the state transitions back to state 1008.
State 1016 may occur from state 1008. At state 1016, the tabbed browser may perform operations in response to the user's selection of one of the thumbnails displayed in the quick pick user interface. For example, the tabbed browser may set the in focus tab to be the tab associated with the selected thumbnail. In addition, the tabbed browser may intelligently slide the tabs within the tab row so that the selected thumbnail is displayed in a favorable position. For example, if the selected thumbnail corresponds to a tab in the overflow on the left side of the tab row, each tab in the tab row may move to the right until there are not any more items in the overflow on the left. Alternatively, each tab in the tab row may move to the right until the selected item moves to a favorable position on the tab row, such as in the center. Likewise, if the selected thumbnail corresponds to a tab in the overflow on the right side of the tab row, each tab in the tab row may move to the left until there are not any more items in the overflow on the right. Alternatively, each tab in the tab row may move to the left until the selected item moves to a favorable position on the tab row. The favorable position may be user definable. Once the tabbed browser handles the processing based on the selected thumbnail, the state transitions to back to state 1002.
As one can see, the present quick pick mechanism allows a user to conveniently select any one of several open tabs. They can easily view each open tab, rearrange the tabs, close a tab, and the like. Thus, the present quick pick mechanism provides an enhanced and convenient viewing experience to users.
Reference has been made throughout this specification to “one embodiment,” “an embodiment,” or “an example embodiment” meaning that a particular described feature, structure, or characteristic is included in at least one embodiment of the present invention. Thus, usage of such phrases may refer to more than just one embodiment. Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
One skilled in the relevant art may recognize, however, that the present mechanism may be practiced without one or more of the specific details, or with other methods, resources, materials, etc. In other instances, well known structures, resources, or operations have not been shown or described in detail merely to avoid obscuring aspects of the present consistent visual appearance technique.
While example embodiments and applications have been illustrated and described, it is to be understood that the present technique is not limited to the precise configuration and resources described above. Various modifications, changes, and variations apparent to those skilled in the art may be made in the arrangement, operation, and details of technique disclosed herein without departing from the scope of the claimed invention.
This application is a continuation of and claims the benefit of U.S. patent application Ser. No. 11/101,735, filed on Apr. 7, 2005, and entitled “SYSTEM AND METHOD FOR SELECTING A TAB WITHIN A TABBED BROWSER”, the disclosure of which is hereby incorporated by reference herein in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5781785 | Rowe et al. | Jul 1998 | A |
| 5949413 | Lerissa et al. | Sep 1999 | A |
| 6247020 | Minard | Jun 2001 | B1 |
| 6356908 | Brown et al. | Mar 2002 | B1 |
| 6359634 | Cragun et al. | Mar 2002 | B1 |
| 6433801 | Moon et al. | Aug 2002 | B1 |
| 6456303 | Walden et al. | Sep 2002 | B1 |
| 6489975 | Patil et al. | Dec 2002 | B1 |
| 6544295 | Bodnar | Apr 2003 | B1 |
| 6801227 | Bocionek et al. | Oct 2004 | B2 |
| 6981223 | Becker et al. | Dec 2005 | B2 |
| 7207003 | Berstis et al. | Apr 2007 | B1 |
| 7234114 | Kurtz et al. | Jun 2007 | B2 |
| 7251775 | Astala et al. | Jul 2007 | B1 |
| 7596760 | Sauve et al. | Sep 2009 | B2 |
| 7624348 | Shuping et al. | Nov 2009 | B2 |
| 20020093537 | Bocioned et al. | Jul 2002 | A1 |
| 20020163545 | Hii | Nov 2002 | A1 |
| 20020194611 | Hodgkinson | Dec 2002 | A1 |
| 20030071849 | Ferri | Apr 2003 | A1 |
| 20030097640 | Abrams et al. | May 2003 | A1 |
| 20030222916 | Kuwata et al. | Dec 2003 | A1 |
| 20040030719 | Wei | Feb 2004 | A1 |
| 20040041841 | LeMogne et al. | Mar 2004 | A1 |
| 20040093562 | Diorio et al. | May 2004 | A1 |
| 20040113948 | Shahrbabaki et al. | Jun 2004 | A1 |
| 20040215649 | Whalen et al. | Oct 2004 | A1 |
| 20050015726 | Tuominen | Jan 2005 | A1 |
| 20050172235 | Cragun et al. | Aug 2005 | A1 |
| 20060101330 | Godley | May 2006 | A1 |
| 20060161857 | Johnston et al. | Jul 2006 | A1 |
| 20070128899 | Mayer | Jun 2007 | A1 |
| Number | Date | Country |
|---|---|---|
| 1529262 | Sep 2004 | CN |
| 2360921 | Oct 2001 | GB |
| 2003223250 | Aug 2003 | JP |
| 2004145375 | May 2004 | JP |
| 2003112728 | Dec 2004 | RU |
| 2004119851 | Mar 2005 | RU |
| 448377 | Aug 2001 | TW |
| 518487 | Jan 2003 | TW |
| 2004107151 | Dec 2004 | WO |
| Entry |
|---|
| Jhaveri, “Intermediate and Post-Session Web Page Revisitation Techniques and Tools,” Sep. 2004, pp. 59. |
| Siracusa, “OmniWeb 5.0 Beta,” at <<http://arstechnica.com/reviews/appsfow5.ars/1 >>, Feb. 3, 2004, pp. 22. |
| PCT Search Report Patent Application No. PCT/US06/08415 Mailed on Oct. 1, 2007, pp. 7. |
| “Tabbrowser Preferences—Firefox Extension,” found on internet at https://addons.mozilla.org/extensions/moreinfo. php?id=158&application=firefox on Jan. 25, 2006, 8 pages. |
| “Maxthon Tabbed Browser,” found on internet at http://www.maxthon.com/ on Jan. 25, 2006, 3 pages. |
| “Netscape 7.1 Highlights,” found on internet http://channels.netscape.com/browsers/7/learnmore/NS71—reviewersguide.pdf, 46 pages, 2003. |
| “Opera for Windows,” found on internet at http://www.opera.com/products/desktop/ on Jan. 25. 2006, 4 pages. |
| Notice of Allowance issued Aug. 29, 2011, in Malaysia Patent Application No. PI 20060945, filed Mar. 7, 2006. |
| Office Action mailed Aug. 12, 2010 in co-pending Australia Application No. 2006234871, filed Mar. 9, 2006. |
| Office Action mailed Nov. 15, 2011 in co-pending Australia Application No. 2011201522, filed Apr. 5, 2011. |
| Notice of Allowance mailed Feb. 21, 2012 in co-pending Australia Application No. 2011201522, filed Apr. 5, 2011. |
| Notice of Allowance mailed Jun. 26, 2012 in co-pending Canada Application No. 2,602,600 filed Mar. 9, 2006. |
| Office Action mailed Jan. 22, 2010 in co-pending China Application No. 200680011149.3, filed Mar. 9, 2006 (with English-language translation). |
| Notice of Allowance mailed Dec. 28, 2011 in co-pending China Application No. 200680011149.3, filed Mar. 9, 2006 (with English-language translation). |
| Office Action mailed Sep. 22, 2011 in co-pending Japan Application No. 2008-505313, filed Mar. 9, 2006 (with English-language translation). |
| Notice of Allowance mailed Mar. 9, 2010 in co-pending Mexico Application No. MXa/2007/012422, filed Mar. 9, 2006. |
| Gagne, Marcel, “Moving to Linux: Kiss The Blue Screen of Death Goodbye!” 2004, Chapter 4, pp. 24, 169 and 172, found in Internet http://books.google.ru/books, 3 pages. |
| Notice of Allowance mailed Aug. 27, 2012 in co-pending Japan Application No. 2008-505313, filed Mar. 9, 2006. |
| Notice of Allowance mailed Dec. 15, 2010 in co-pending Australia Application No. 2006234871, filed Mar. 9, 2006. |
| Notice of Preliminary Rejection mailed Aug. 17, 2012 in co-pending Korean Application No. 10-2011-7005286, filed Mar. 4, 2011 (with English-language translation). |
| Notice of Allowance mailed Sep. 12, 2012 in co-pending Taiwan Application No. 95104450, filed Feb. 9, 2006. |
| Michel Beaudouin-Lafon, Novel Interaction Techniques for Overlapping Windows, Proceedings: Proceedings of the 14th annual ACM symposium on User interface software and technology.—Published Date: Nov. 11, 2011. http://wiki.lri.fr/fondihm/—files/windows-uist01-beaudouinlafon.pdf. |
| Cockburn, et al., “WebView: A Graphical Aid for Revisiting Web Pages,” In Proceedings of the Australian Conference on Human Computer Interaction, Nov. 28, 1999, 7 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20100011313 A1 | Jan 2010 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11101735 | Apr 2005 | US |
| Child | 12564705 | US |
