Virtual tabs supporting web content suspension

• US 9,658,747 B2
• Filed: 10/01/2013
• Issued: 05/23/2017
• Est. Priority Date: 10/01/2013
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Rossi, Jacob S., Patten, Michael J., Ens, Michael J.
• Primary Examiner(s): Leggett, Andrea
• Application Number:
  US14/043,711
• Publication Number:
  US 20150095838A1
• Time in Patent Office: 1,330 Days
• Field of Search: 715777
• CPC Class Codes: G06F 3/0483 Interaction with page-structured environments, e.g. book metaphor

Abstract

A Web application displays Web content in a user interface (UI) tab having multiple associated virtual tabs. The multiple associated virtual tabs can include a visible tab hosting Web content that is currently visible, one or more hidden tabs each hosting Web content that is not currently visible, and optionally one or more empty tabs each hosting no Web content or only primitive Web content. For each hidden tab, the Web content hosted in the hidden tab is suspended, which refers to ceasing execution of instructions in and/or other operations performed by the Web content. For example, audio/video playback is paused, execution of script instructions ceases, and so forth.

Claims

1. A method comprising:

displaying first Web content in a user interface tab of a Web application;

receiving a request to change from displaying the first Web content to displaying second Web content in the user interface tab;

displaying, in response to the request, the second Web content in the user interface tab;

keeping the first Web content in a first hidden tab that is a virtual tab associated with the user interface tab while displaying the second Web content in the user interface tab; and

suspending the first Web content based on determining that the first Web content is compatible with being suspended by accessing a record that identifies Web content that is compatible with being suspended and other Web content that is not compatible with being suspended.

2. The method as recited in claim 1, further comprising:

receiving, after suspending the first Web content, an additional request to change to displaying the first Web content in the user interface tab;

reactivating, in response to the additional request, the first Web content;

displaying the first Web content;

keeping the second Web content in a second hidden tab corresponding to the user interface tab; and

suspending the second Web content.

3. The method as recited in claim 1, the Web application comprising a Web browser, the first Web content comprising a first Web page, and the second Web content comprising a second Web page.

4. The method as recited in claim 1, the suspending the first Web content including pausing playback of audio and/or video content included in the first Web content.

5. The method as recited in claim 1, the suspending the first Web content including:

receiving one or more replies to one or more asynchronous requests sent by the first Web content to another device;

holding the one or more replies;

providing the one or more replies to the first Web content in response to the first Web content being subsequently reactivated.

6. The method as recited in claim 1, the suspending the first Web content including stopping providing to the first Web content messages of when events occur.

7. The method as recited in claim 6, the stopping comprising stopping sending messages that would trigger execution of JavaScript in the first Web content.

8. The method as recited in claim 1, the suspending the first Web content including stopping a timer that controls each animation element and each transition element in the first Web content.

9. The method as recited in claim 1, the suspending the first Web content including stopping providing to Web worker threads of the first Web content messages of when events occur.

10. The method as recited in claim 1, the suspending the first Web content including:

sending a request to a plug-in that adds a feature to the Web application for the plug-in to suspend itself; and

unloading, rather than suspending, the first Web content in response to the plug-in not being able to suspend itself.

11. The method as recited in claim 1, further comprising deleting one or more hidden tabs associated with the user interface tab in response to more than a threshold number of hidden tabs being associated with the user interface tab.

12. The method as recited in claim 1, the second Web content having been in a second hidden tab corresponding to the user interface tab, and the displaying the second Web content comprises switching the second hidden tab to being the visible tab corresponding to the user interface tab.

13. The method as recited in claim 1, the first hidden tab being available for use with at least one user interface tab different than the user interface tab.

14. A computing device comprising:

one or more processors;

one or more computer-readable media having stored thereon multiple instructions that, when executed by the one or more processors, cause the one or more processors to perform acts comprising;

displaying a plurality of user interface tabs of a Web browser each having simultaneously its own virtual tabs comprising an associated visible tab and an associated hidden tab;

displaying in a first user interface tab of the plurality of user interface tabs a first Web page hosted in the visible tab associated with the first user interface tab;

generating an empty tab;

receiving a request to change from displaying the first Web page to displaying a second Web page in the first user interface tab;

loading, in response to the request, the second Web page in the previously generated empty tab;

switching the previously generated empty tab to being the visible tab associated with the first user interface tab; and

displaying the second Web page hosted in the visible tab associated with the first user interface tab in the first user interface tab while keeping the first Web page hosted in the hidden tab associated with the first user interface tab.

15. The computing device as recited in claim 14, the empty tab hosting a blank Web page.

16. The computing device as recited in claim 14, the acts further comprising:

suspending the first Web page; and

switching the previously visible tab to being a hidden tab.

17. The computing device as recited in claim 16, the acts further comprising:

receiving, after suspending the first Web page, an additional request to change to displaying the first Web page in the first user interface tab;

reactivating, in response to the additional request, the first Web page;

switching the hidden tab hosting the first Web page to being a visible tab;

displaying the first Web page;

switching the tab hosting the second Web page to being a hidden tab; and

suspending the second Web page.

18. The computing device as recited in claim 16, the suspending the first Web page comprising:

pausing playback of audio and/or video content included in the first Web page;

pausing each animation element and each transition element in the first Web page; and

stopping providing to Web worker threads of the first Web page messages of when events occur.

19. The computing device as recited in claim 14, the acts further comprising generating, after loading the second Web content in the previously generated empty tab, a new empty tab.

20. A method comprising:

displaying a first Web page in a user interface tab of a Web browser;

receiving a request to change from displaying the first Web page to displaying a second Web page in the user interface tab;

displaying, in response to the request, the second Web page in the user interface tab;

keeping the first Web page in a first hidden tab corresponding to the user interface tab; and

suspending the first Web page, the suspending including;

pausing playback of audio and/or video content included in the first Web page,

stopping providing to the first Web page messages of when events occur that would trigger execution of JavaScript in the first Web page,

sending a request to a plug-in that adds a feature to the Web browser for the plug-in to suspend itself, and

unloading, rather than suspending, the first Web page in response to the plug-in not being able to suspend itself.