Hyperlink destination visibility

- Microsoft

Various embodiments utilize page scripting and parsing to identify the target destination of a hyperlink and provide a visual indication of the destination to the user without causing redirection to the target destination. In some embodiments, hyperlink color, highlighting, or icons are used to indicate the destination. Particular colors and/or icons selected to indicate the destination can, in some embodiments, be selected based on the domain hosting the target destination. In at least some embodiments, the destination of a link is determined by the page script run by a web browser on a user's device, while in other embodiments, information is transmitted to a web request handler on the server hosting the web site to determine the destination.

Skip to: Description  ·  Claims  ·  References Cited  · Patent History  ·  Patent History
Description
BACKGROUND

Many web sites present aggregated content from various content sources to users. For example, a web page can include hyperlinks that can take the user to a different page on the web site or to a different web site altogether. In some instances, what appears to be a hyperlink leading to additional information on a topic instead takes a user to a search engine page listing search results for the topic. Often, users are given little to no indication about where a given link will take them, which can lead to frustration or wasted time.

SUMMARY

This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

Various embodiments utilize page scripting and parsing to identify the destination of a hyperlink and provide a visual indication of the destination to the user. In some embodiments, hyperlink color, highlighting, or icons are used to indicate the destination. In at least some embodiments, the destination of a link is determined by the page script run by a web browser on a user's device, while in other embodiments, information is transmitted to a web request handler on the server hosting the web site to determine the destination.

BRIEF DESCRIPTION OF THE DRAWINGS

While the specification concludes with claims particularly pointing out and distinctly claiming the subject matter, it is believed that the embodiments will be better understood from the following description in conjunction with the accompanying figures, in which:

FIG. 1 is an illustration of an example environment in accordance with one or more embodiments;

FIG. 2 illustrates an example web browser in accordance with one or more embodiments;

FIG. 3 is a is a flow diagram that describes steps in a method in accordance with one or more embodiments;

FIG. 4 is a flow diagram that describes steps in a method in accordance with one or more embodiments;

FIG. 5 is a flow diagram that describes steps in a method in accordance with one or more embodiments; and

FIG. 6 illustrates an example system that can be utilized to implement one or more embodiments.

 DETAILED DESCRIPTION

Overview

Various embodiments utilize page scripting and parsing to identify the target destination of a hyperlink and provide a visual indication of the destination to the user without causing redirection to the target destination. In some embodiments, hyperlink color, highlighting, or icons are used to indicate the destination. Particular colors and/or icons selected to indicate the destination can, in some embodiments, be selected based on the domain hosting the target destination. In at least some embodiments, the destination of a link is determined by the page script run by a web browser on a user's device, while in other embodiments, information is transmitted to a web request handler on the server hosting the web site to determine the destination.

In the discussion that follows, a section entitled “Example Operating Environment” describes an operating environment in accordance with one or more embodiments. Next, a section entitled “Example Embodiment” describes various embodiments of hyperlink destination visibility. In particular, the section describes processes for determining the destination of a hyperlink and indicating to a user the destination. Finally, a section entitled “Example System” is provided and describes an example system that can be used to implement one or more embodiments.

Consider, now, an example operating environment in accordance with one or more embodiments.

Example Operating Environment

FIG. 1 is an illustration of an example environment 100 in accordance with one or more embodiments. Environment 100 includes a user device 102 including one or more processors 104 and computer-readable storage media 106. User device 102 can be embodied as any suitable computing device such as, by way of example and not limitation, a desktop computer, a portable computer, a netbook, a handheld computer such as a personal digital assistant (PDA), cell phone, and the like.

Computer-readable storage media 106 includes one or more applications, which can include at least a software executable module in the form of a web browser 108. Web browser 108 can receive content from and send content to other servers, such as web site host server 110, via network 112, such as the Internet. Such content can include any suitable type of content that can be received from and sent to web sites hosted by the servers. In various embodiments, web browser 108 is configured to cause a webpage to be displayed to a user according to styles defined by information associated with the webpage. Styles can be specified using the Cascading Style Sheets (CSS) language or in other suitable ways. The information associated with the webpage can be included in page script, which includes instructions to the browser about how to cause the webpage to be displayed. For example, information associated with a certain webpage can define a style such that a hyperlink anchor (e.g., the location within a page from which the hyperlink can be followed) is underlined and displayed in blue while other text on the page is displayed in black. In various embodiments, the style can depend on information associated with the target of a hyperlink (e.g., the location to which the hyperlink leads).

In various embodiments, web site host server 110 hosts a plurality of webpages 114. Web site host server 110 also includes one or more processors 116 and computer-readable storage media 118 on which the webpages 114 reside. In some embodiments, a web request handler 120 also resides on computer-readable storage media 118. Web request handler 120 can be configured to determine the target of dynamic hyperlinks included in one or more webpages 114 and transmit information associated with the target to the browser 108 via network 112. The web request handler is described in further detail below.

The computer-readable storage media included in each device or server can include, by way of example and not limitation, all forms of volatile and non-volatile memory and/or storage media that are typically associated with a computing device. Such media can include ROM, RAM, flash memory, hard disk, removable media and the like. One specific example of a computing device is shown and described below in FIG. 6.

Generally, any of the functions described herein can be implemented using software, firmware, hardware (e.g., fixed logic circuitry), or a combination of these implementations. The terms “module,” “functionality,” and “logic” as used herein generally represent software, firmware, hardware, or a combination thereof. In the case of a software implementation, the module, functionality, or logic represents program code that performs specified tasks when executed on a processor (e.g., CPU or CPUs). The program code can be stored in one or more computer-readable memory devices. The features of the user interface techniques described below are platform-independent, meaning that the techniques may be implemented on a variety of commercial computing platforms having a variety of processors.

Having described an example operating environment, consider now a discussion of various embodiments employing techniques to visually indicate the destination of a hyperlink to a user.

Example Embodiment

The discussion that follows starts first with a description of an example web browser and its associated user interface. Following this, a discussion of various embodiments of visually indicating the destination of a hyperlink is provided.

FIG. 2 illustrates an example web browser 200 in accordance with one or more embodiments. In this particular example, web browser 200 includes a web browser user interface 202 which includes a content rendering area 204 above a status indication bar 206. The web browser user interface 202 also includes an address bar 208, one or more tabs 210, and a new tab button 212 for opening additional tabs. Other controls can be provided depending on the specific embodiment.

Status indication bar 206 is configured to display messages and icons to provide information to the user regarding what the browser is doing. For example, a message can indicate that the browser is looking for a web site, contacting a web site it found, waiting for the web site to send data, receiving data from the web site, or downloading parts of a webpage, to name just a few. In some embodiments, the status indication bar 206 can display icons regarding a security or privacy level. Additionally, the status indication bar can provide information regarding the destination of a hyperlink. Specifically, when an input is received relative to a hyperlink that is of the type that is typically used to attempt to navigate to or initiate a navigation to an associated destination, the target destination can be displayed in the status indication bar. For example, when a mouse indicator 214 hovers over a hyperlink 216 in the content rendering area 204, the status indication bar 206 can display the target address for the hyperlink 216.

In various embodiments, the destination of the hyperlink 216 can be indicated by one or more changes or additions to the mouse indicator 214. In some embodiments, a rendering is provided adjacent to the mouse indicator to visually convey an affordance that is associated with the target destination. For example, in FIG. 2, when mouse indicator 214 hovers over the words “web site” which anchor hyperlink 216, a small butterfly logo is rendered adjacent to the mouse indicator to indicate that the target of the hyperlink 216 is a webpage hosted by MSN® (MSN and the MSN logo are registered trademarks of Microsoft Corporation). Other logos or icons can be employed, and can be added to mouse indicator 214 or can replace the mouse indicator 214. For example, a magnifying glass can be added to or can replace mouse indicator 214 when the target of a hyperlink is a search results page, or the mouse indicator 214 can be replaced with the MSN logo when the target of a hyperlink is a webpage hosted by MSN®.

Additionally or alternatively, the destination of the hyperlink 216 can be indicated by a change in the color of the hyperlink anchor. For example, the words “web site” which anchor hyperlink 216 can be displayed in light blue to indicate that the target of hyperlink 216 is a webpage hosted by MSN® while the word “address” which anchors hyperlink 216a can be displayed in orange to indicate that the target of hyperlink 216a is a webpage hosted by Bing® Maps (Bing is a registered trademark of Microsoft Corporation). The use of colors can be used to indicate the destination of the hyperlink in embodiments that do not include mouse indicators, such as in browsers on a mobile phone. The colors chosen to indicate destinations can vary, as will be appreciated by the skilled artisan. For example, a particular destination may have a prominent color with which it is associated or which is used to brand the destination. In this case, the prominent color may be used as a way to visually convey an association between the domain hosting the target destination of the hyperlink and the anchor displayed to a user.

In various embodiments, multiple hyperlinks associated with different target webpages (e.g., hyperlinks 216 and 216a in FIG. 2) can be identified. When multiple hyperlinks are identified, the system can utilize information associated with different respective target webpages to determine multiple respective styles to be applied to the webpage and visually apply different respective styles to indicate each target webpage.

In some embodiments, a visually applied style is selected based on information regarding a domain hosting the target webpage. For example, in FIG. 2, anchors leading to target webpages hosted on a domain such as MSN® can be displayed in light blue, while anchors leading to target webpages hosted on a domain such as Bing® can be displayed in orange. In such embodiments, the same style can be visually applied to multiple hyperlinks leading to different webpages hosted on the same domain.

Having described an example web browser employing hyperlink destination visibility, consider now various processes indicating a target destination of a hyperlink to a user without causing navigation of a browser to the target destination.

FIG. 3 is a flow diagram illustrating steps in a process 300 for indicating the destination of a hyperlink to a user. The process 300 can be implemented in connection with any suitable hardware, software, firmware, or combination thereof. In at least some embodiments, the method can be implemented by a client device, such as a personal computer or mobile phone, examples of which are provided above and below.

Block 302 ascertains occurrence of a user action. Any suitable type of user action can be ascertained. In the illustrated and described embodiments, user actions can include those that typically precede or initiate a navigation to a destination associated with a hyperlink. By way of example and not limitation, such actions can include a user hovering a mouse indicator over a hyperlink included on a webpage displayed by a browser. Block 304 executes at least a portion of a page script associated with a webpage. This can be performed in any suitable way. For example, in various embodiments, the hovering of a mouse over the hyperlink triggers the execution of one or more portions of JavaScript® code that encodes the webpage (JavaScript is a registered trademark of Oracle Corporation). The page script provides the browser with instructions regarding how to process the hyperlink.

Block 306 determines the target destination by processing the hyperlink. This can be performed in any suitable way. For example, various parsing techniques can be employed to extract the target destination from information associated with the hyperlink included in the page script. In various embodiments, additional processing by a web request handler can be employed to determine the target destination, such as when the hyperlink is a dynamic link with a variable target destination. Additional processing by the web request handler is described in more detail below.

Block 308 visually applies one or more styles based on the target destination. This can be performed in any suitable way. For example, in at least some embodiments, the page script can include a look up table (LUT) that defines one or more styles according to the target destination of a hyperlink. Alternately or additionally, the style can be inline coded within the page script. Styles defined according to target destination can include, by way of example and not limitation, text color, background color, mouse icon, mouse color, text styles (including bold, underline, or italics), and the like. Examples of how styles can be applied are provided above.

FIG. 4 is a flow diagram that describes steps in a process 400 of processing a hyperlink to determine a target destination in accordance with one or more embodiments. The method can be performed in connection with any suitable hardware, software, firmware, or combination thereof. In at least some embodiments, the method can be performed by a suitably-configured web browser, such as the one described above.

Block 402 identifies one or more hyperlinks to be processed. This can be performed in any suitable way. For example, in various embodiments, the hovering of a mouse over the hyperlink triggers the execution of one or more portions of page script that encodes the webpage and indicates that a hyperlink is present.

Next, block 404 generates tokens. This can be performed in any suitable way. For example, in one or more embodiments, a parser processes the page script and splits characters in the code into meaningful symbols according to known expressions. Each group of characters can include one or more characters, and is referred to as a token. For example, in the text “[Tour rookie] [Keegan Bradley], playing in his first [major championship], proved all of those statements wrong here [Sunday] when he won the [PGA Championship],” the brackets illustrate tokens, or words and phrases that have contextual meaning even when considered on their own.

Block 406 confirms that the tokens form an allowable expression. For example, the parser ensures that the tokens define components that make up an expression and that each word/phrase exists in a lookup table. For example, the parser can confirm that each token (e.g., Tour rookie, Keegan Bradley, major championship, Sunday, and PGA Championship from the example above) exists in a Wikipedia® entry lookup table (Wikipedia® is a registered trademark of Wikimedia Foundation, Inc.) or other database. If the parser has parsed the characters incorrectly, one or more of these tokens may not appear in the lookup table, and the parser can generate a new set of tokens.

Next, block 408 ascertains a target destination of the hyperlink. This can be done in any suitable way. For example, the parser selects the token including a URL destination of the hyperlink and ascertains the target destination of the hyperlink from the token. Usually, the target domain of the URL can be sufficient to indicate the target destination (e.g., the target network “msn.com” within the URL http://editorial.autos.msn.com/blogs/autosblog.aspx?feat=d363e301-a203-4080-a52d-39eb03946032).

Block 410 visually applies one or more styles based on the target destination without causing navigation of the browser to the target destination. This can be performed in any suitable way. For example, a look-up table (LUT) can define one or more styles according to the target destination of a hyperlink, or the style can be defined by the code in the page script. Styles defined according to target destination can include, by way of example and not limitation, text color, background color, mouse icon, mouse color, text styles (including bold, underline, or italics), and the like. For example, the LUT can define a style corresponding to the target network “msn.com”, and the defined style can be applied to the hyperlinks with URLs including that target network (e.g., http://editorial.autos.msn.com/blogs/autosblog.aspx?feat=d363e301-a203-4080-a52d-39eb03946032). The browser then causes the webpage to be displayed accordingly.

Process 400 can employed in embodiments in which the target destination of the hyperlink can be determined by processing information associated with the webpage, and more particularly, by parsing the information associated with the hyperlinks included in the webpage. However, in some embodiments, such as embodiments where one or more hyperlinks are dynamic hyperlinks, additional processing can be used to determine the target destination.

FIG. 5 is a flow diagram that describes steps in a method 500 of processing a hyperlink to determine the target destination in accordance with one or more embodiments. The method can be performed in connection with any suitable hardware, software, firmware, or combination thereof. In the illustrated example, some steps of the method are illustrated as being performed by a “Browser,” while other steps of the method are illustrated as being performed by a “Server.” In at least some embodiments, the method can be performed by a suitably-configured web browser, such as the one described above.

Block 502 identifies a hyperlink to be processed. This can be performed in any suitable way. For example, in various embodiments, the hovering of a mouse over the hyperlink triggers the execution of one or more portions of a page script that encodes the webpage and indicates that a hyperlink is present.

Next, block 504 generates tokens. This can be done in any suitable way. For example, a parser processes the page script and splits the characters in the code into meaningful symbols according to known expressions. Each group of characters can include one or more characters, and is referred to as a token. Example tokens are “Seattle,” “Forrest Gump,” “Bill Clinton” or “Committee to Investigate the Condition of the Potomac River Front at Washington.”

Block 506 confirms that the tokens generated at block 504 form an allowable expression. This can be performed in any suitable way. For example, the parser can ensure that the tokens define components that make up an expression and that each word/phrase in the expression exists in a Wikipedia® entry lookup table.

Next, block 508 attempts to ascertain a target destination of the hyperlink. This can be performed in any suitable way, examples of which are provided above. Block 510 determines whether a target destination of the hyperlink was ascertained at block 508. If the target destination of the hyperlink was ascertained, block 524 visually applies one or more styles according to the target destination. However, if block 510 determines that no target destination was ascertained, the process proceeds to block 512. Attempts to ascertain a target destination of the hyperlink can fail (e.g., a “no” at block 510), for example, when the parser is unable to determine the target destination of the hyperlink based on the tokens. For example, the parser determines that the token including the URL destination of the hyperlink is missing or is indicative of a variable destination.

Block 512 transmits information associated with the hyperlink to the server. The server can be, for example, the web site host server on which the webpage resides. Information transmitted to the server can include information determined by the parser as well as additional information about the user or environment for use in determining the destination of the hyperlink. For example, the target destination of the hyperlink can vary depending on the date, time, user location, or other factors. In addition to transmitting information associated with the hyperlink and user information, the browser can transmit a cookie corresponding to the webpage to the server.

Block 514 receives the information associated with the hyperlink. Block 516 ascertains a target destination of the hyperlink. This can be performed in any suitable way. For example, a web request handler can determine the target destination of the hyperlink based on the information received from the browser.

In some embodiments, the process continues to optional block 518. Block 518 determines styles to be applied. This can be performed in any suitable way. For example, the web request handler can determine styles to be applied based on the target destination of the hyperlink utilizing a LUT to determine one or more styles to be altered according to the target destination. Styles defined according to target destination can include, by way of example and not limitation, text color, background color, mouse icon, mouse color, text styles (including bold, underline, or italics), and the like. Then, block 520 transmits information to the browser. In embodiments including block 518, the server can transmit the style information, the target destination, and other information to the browser. Block 522 receives the information from the server, and block 524 visually applies one or more styles according to the target destination of the hyperlink without causing navigation to the target destination.

In alternate embodiments, computational demands on the server can be reduced by shifting the style determination to the browser. In such embodiments, after block 516 ascertains the target destination of the hyperlink, the process continues to block 520. Block 520 transmits information to the browser. This can be performed in any suitable way. For example, the server can transmit the target destination of the hyperlink along with other information to the browser to enable the browser to determine one or more styles according to the target destination. For example, other information transmitted can include information regarding a domain hosting the target webpage. Block 522 receives the information from the server, and block 524 visually applies one or more styles according to the target destination. This can be performed in any suitable way. For example, the browser can utilize a LUT or one or more style sheets embedded in the page script to determine one or more styles to be altered depending on the target destination. Styles defined according to target destination can include, by way of example and not limitation, text color, background color, mouse icon, mouse color, text styles (including bold, underline, or italics), and the like.

Having described an example method of processing to determine the destination of a hyperlink and indicate the destination to a user, consider now a discussion of an example system that can be used to implement one or more embodiments.

Example System

FIG. 6 illustrates an example computing device 600 that can be used to implement the various embodiments described above. Computing device 600 can be, for example, client computing device 102 of FIG. 1, or any other suitable computing device.

Computing device 600 includes one or more processors or processing units 602, one or more memory and/or storage components 604, one or more input/output (I/O) devices 606, and a bus 608 that allows the various components and devices to communicate with one another. Bus 608 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. Bus 608 can include wired and/or wireless buses.

Memory/storage component 604 represents one or more computer storage media. Memory/storage component 604 can include volatile media (such as random access memory (RAM)) and/or nonvolatile media (such as read only memory (ROM), flash memory, optical disks, magnetic disks, and so forth). Component 604 can include fixed media (e.g., RAM, ROM, a fixed hard drive, etc.) as well as removable media (e.g., a flash memory drive, a removable hard drive, an optical disk, and so forth).

One or more input/output devices 606 allow a user to enter commands and information to computing device 600, and also allow information to be presented to the user and/or other components or devices. Examples of input devices include a keyboard, a cursor control device (e.g., a mouse), a microphone, a scanner, and so forth. Examples of output devices include a display device (e.g., a monitor or projector), speakers, a printer, a network card, and so forth.

Various techniques may be described herein in the general context of software or program modules. Generally, software includes routines, programs, objects, components, data structures, and so forth that perform particular tasks or implement particular abstract data types. 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 medium or media that can be accessed by a computing device. By way of example, and not limitation, computer readable media may comprise “computer-readable storage media”.

“Computer-readable storage media” include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or other data. Computer-readable storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer.

While various embodiments have been described above, it should be understood that they have been presented by way of example, and not limitation. It will be apparent to persons skilled in the relevant art(s) that various changes in form and detail can be made therein without departing from the scope of the present disclosure. Thus, embodiments should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.

Claims

1. A computer-implemented method comprising:

identifying, using a computing device, at least one hyperlink displayed in a webpage, the at least one hyperlink being associated with a target webpage;
determining, using the computing device, at least one style to be applied to the webpage based at least in part upon information associated with the target webpage, the at least one style comprising a mouse indicator; and visually applying, using the computing device, said at least one style to the webpage, without causing navigation of an associated browser to the target webpage, wherein the information associated with the target webpage of the at least one hyperlink comprises information regarding a domain hosting the target webpage, wherein said identifying comprises identifying multiple hyperlinks at least some of which being associated with different target webpages; wherein said determining comprises determining multiple respective styles to be applied to the webpage based at least upon information associated with said different respective target webpages; and wherein said visually applying comprises applying said multiple respective styles to the webpage, the multiple respective styles comprising different respective styles.

2. The computer-implemented method of claim 1, the at least one style further comprising a color of an anchor within a webpage from which the at least one hyperlink can be followed or a background color.

3. The computer-implemented method of claim 1, said determining comprising determining at least one style to be applied utilizing a look up table.

4. The computer-implemented method of claim 1, said determining comprising extracting style information from a page script corresponding to the webpage.

5. The computer-implemented method of claim 1, further comprising ascertaining the target webpage by extracting information regarding the target webpage from a page script corresponding to the webpage.

6. The computer-implemented method of claim 1, the at least one hyperlink comprising a dynamic hyperlink.

7. The computer-implemented method of claim 6, further comprising receiving information regarding the target webpage of the at least one hyperlink from a server.

8. One or more computer-readable storage memories storing a web browser, said web browser being executable by a processor to perform operations comprising:

identifying at least one hyperlink displayed in a webpage, the at least one hyperlink being associated with a target webpage;
determining at least one style to be applied to the webpage based at least in part upon information associated with the target webpage, the at least one style comprising a mouse indicator; and
visually applying said at least one style to the webpage, without causing navigation of an associated browser to the target webpage,
wherein the information associated with the target webpage of the at least one hyperlink comprising information regarding a domain hosting the target webpage,
wherein said identifying comprises identifying multiple hyperlinks at least some of which being associated with different target webpages;
wherein said determining comprises determining multiple respective styles to be applied to the webpage based at least upon information associated with said different respective target webpages; and
wherein said visually applying comprises applying said multiple respective styles to the webpage, the multiple respective styles comprising different respective styles.

9. The one or more computer-readable storage memories of claim 8, the at least one style further comprising a color of an anchor within a webpage from which the at least one hyperlink can be followed or a background color.

10. The one or more computer-readable storage memories of claim 8, said determining comprising determining at least one style to be applied utilizing a look up table.

11. The one or more computer-readable storage memories of claim 8, said determining comprising extracting style information from a page script corresponding to the webpage.

12. The one or more computer-readable storage memories of claim 8, wherein the operations further comprise ascertaining the target webpage by extracting information regarding the target webpage from a page script corresponding to the webpage.

13. The one or more computer-readable storage memories of claim 8, the at least one hyperlink comprising a dynamic hyperlink.

14. The one or more computer-readable storage memories of claim 13, wherein the operations further comprise receiving information regarding the target webpage of the at least one hyperlink from a server.

15. A system comprising:

one or more processors;
one or more computer-readable storage memories embodying computer-readable instructions which, when executed by the one or more processors, implement a method comprising: identifying at least one hyperlink displayed in a webpage, the at least one hyperlink being associated with a target webpage; determining at least one style to be applied to the webpage based at least in part upon information associated with the target webpage, the at least one style comprising a mouse indicator; and visually applying said at least one style to the webpage, without causing navigation of an associated browser to the target webpage, wherein the information associated with the target webpage of the at least one hyperlink comprising information regarding a domain hosting the target webpage, wherein said identifying comprises identifying multiple hyperlinks at least some of which being associated with different target webpages; wherein said determining comprises determining multiple respective styles to be applied to the webpage based at least upon information associated with said different respective target webpages; and wherein said visually applying comprises applying said multiple respective styles to the webpage, the multiple respective styles comprising different respective styles.

16. The system of claim 15, the at least one style further comprising a color of an anchor within a webpage from which the at least one hyperlink can be followed or a background color.

17. The system of claim 15, said determining comprising determining at least one style to be applied utilizing a look up table.

18. The system of claim 15, said determining comprising extracting style information from a page script corresponding to the webpage.

19. The system of claim 15, further comprising ascertaining the target webpage by extracting information regarding the target webpage from a page script corresponding to the webpage.

20. The system of claim 15, the at least one hyperlink comprising a dynamic hyperlink.

21. The system of claim 20, wherein the operations further comprise receiving information regarding the target webpage of the at least one hyperlink from a server.

Referenced Cited
U.S. Patent Documents
5978818 November 2, 1999 Lin
6848075 January 25, 2005 Becker et al.
7464326 December 9, 2008 Kawai et al.
20020032745 March 14, 2002 Honda
20020107882 August 8, 2002 Gorelick et al.
20050076097 April 7, 2005 Sullivan et al.
20070067333 March 22, 2007 Cho et al.
20080114737 May 15, 2008 Neely et al.
20080172738 July 17, 2008 Bates et al.
20080256608 October 16, 2008 Gottlieb et al.
20090094327 April 9, 2009 Shuster et al.
20090193349 July 30, 2009 Arav
20090199135 August 6, 2009 Arav
20090234730 September 17, 2009 Lee
20110167328 July 7, 2011 Iverson
20110209040 August 25, 2011 Zeine et al.
20120030551 February 2, 2012 Bank et al.
Foreign Patent Documents
102890709 January 2013 CN
Other references
  • Weinreich, Harald, et al., “Concepts for Improved Visualization of Web Link Attributes” 9th international World Wide Web conference on Computer Networks,published May 15, 2000, pp. 403-416, http://vsis-www.informatik.uni-hamburg.de/getDoc.php/publications/82/hyperscout-www9.pdf.
  • Weinreich, Harald, et al., “The Look of the Link—Concepts for the User Interface of Extended Hyperlinks” Hypertext '01 The 12th ACM Conference on Hypertext and Hypermedia, published Aug. 14, 2001, pp. 19-28, http://citeseer.ist.psu.edu/viewdoc/download;jsessionid=060AD8DC9B3ECC60FBBACBB56B0A0CAE?doi=10.1.1.10.9171&rep=rep1&type=pdf.
  • Genest, Aaron, et al., “Looking Ahead: A Comparison of Page Preview Techniques for Goal-Directed Web Navigation” IFIP International Federation for Information Processing 2009, published Aug. 24, 2009, pp. 378-391, http://hci.usask.ca/uploads/162-3-57260378.pdf.
  • Witt, Rebecca, et al., “Reducing Cognitive Overhead on the World Wide Web” Twenty-Fifth Australasian Computer Science Conference (ACSC2002), published Nov. 1, 2006, pp. 311-320, http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.19.502&rep=rep1&type=pdf.
  • Kopetzky, Theodorich, et al. “Visual Preview for Link Traversal on the World Wide Web” WWW '99, Proceedings of the Eighth International World Wide Web Conference, published May 17, 1999, pp. 1525-1532, http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.106.4888&rep=rep1&type=pdf.
  • “International Search Report”, Mailed Date: Feb. 19, 2013, Application No. PCT/US2012/050219, Filed Date: Aug. 9, 2012, pp. 1. (MS# 333361.02).
Patent History
Patent number: 8627194
Type: Grant
Filed: Sep 6, 2011
Date of Patent: Jan 7, 2014
Patent Publication Number: 20130061120
Assignee: Microsoft Corporation (Redmond, WA)
Inventors: Hatem Zeine (Redmond, WA), Meir Shmouely (Kirkland, WA)
Primary Examiner: Maikhanh Nguyen
Application Number: 13/226,078