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.

Abstract: Techniques for web resource compatibility with web applications are described. According to one or more implementations, an indication of a request to navigate a web application to a web resource is received. Based on the request, a compatibility service is queried regarding compatibility status of the web resource with the web application. According to one or more embodiments, if a compatibility issue between the web resource and the web application is identified, a compatibility element is provided to mitigate the compatibility issue. At least some embodiments enable a user to provide feedback regarding presentation of the web resource by the web application with the compatibility element applied. At least some embodiments notify a developer of the web resource about a compatibility issue of the web resource with the web application.

Abstract: In at least some embodiments, input provided by a single source generates events representing multiple source types through a mapping process, e.g. a touch input generates both touch and mouse events. By configuring the system to not recognize certain gestures, messages associated with the events of the different source types are then interleaved and provided to an associated application for processing. Efficiencies are gained by configuring the system to interleave the messages associated with the source types because messages of one source type can be processed sooner than if the messages of the one source type were queued up and sent in a non-interleaved fashion.

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.

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.

Abstract: Instantiable gesture object techniques are described in which native gesture functionality is abstracted to applications using a script-based recognition interface. Gesture objects may be instantiated for different interaction contexts at the direction of applications programmed using dynamic scripting languages. Gesture objects can be configured to designate particular touch contacts and/or other inputs to consider for gesture recognition and a target element of content to which corresponding recognized gestures are applicable. After creation, gesture objects manage gesture processing operations on behalf of the applications including creating recognizers with the native gesture system, feeding input data for processing, and transforming raw gesture data into formats appropriate for the application and/or a target element. Accordingly, script-based applications may use the gesture objects to offload processing tasks associated with gesture recognition and take advantage of native gesture functionality.

Abstract: In at least some embodiments, input provided by a single source generates events representing multiple source types through a mapping process, e.g. a touch input generates both touch and mouse events. By configuring the system to not recognize certain gestures, messages associated with the events of the different source types are then interleaved and provided to an associated application for processing. Efficiencies are gained by configuring the system to interleave the messages associated with the source types because messages of one source type can be processed sooner than if the messages of the one source type were queued up and sent in a non-interleaved fashion.

Abstract: In at least some embodiments, input provided by a single source generates events representing multiple source types through a mapping process, e.g. a touch input generates both touch and mouse events. By configuring the system to not recognize certain gestures, messages associated with the events of the different source types are then interleaved and provided to an associated application for processing. Efficiencies are gained by configuring the system to interleave the messages associated with the source types because messages of one source type can be processed sooner than if the messages of the one source type were queued up and sent in a non-interleaved fashion.

Abstract: Techniques for web resource compatibility with web applications are described. According to one or more implementations, an indication of a request to navigate a web application to a web resource is received. Based on the request, a compatibility service is queried regarding compatibility status of the web resource with the web application. According to one or more embodiments, if a compatibility issue between the web resource and the web application is identified, a compatibility element is provided to mitigate the compatibility issue. At least some embodiments enable a user to provide feedback regarding presentation of the web resource by the web application with the compatibility element applied. At least some embodiments notify a developer of the web resource about a compatibility issue of the web resource with the web application.

Abstract: A Web application displays Web content in a user interface (UI) tab. Different Web content can be displayed at different times, and Web content that is not displayed can be suspended, which refers to ceasing performance of operations and/or actions by the Web content. The Web content has various different characteristics, and a determination is made based on these characteristics as to whether suspension of particular Web content would yield undesirable results (and thus the Web content is not compatible with being suspended) or whether suspension of the particular Web content would not yield undesirable results (and thus the Web content is compatible with being suspended). Once suspended, the suspended Web content has an associated lifetime. Various different lifetime criteria are used to determine when to suspended Web content is to no longer be maintained, and Web content that is to no longer be maintained is disposed of.

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.

Abstract: High performance touch drag and drop are described. In embodiments, a multi-threaded architecture is implemented to include at least a manipulation thread and an independent hit test thread. The manipulation thread is configured to receive one or more messages associated with an input and send data associated with the messages to the independent hit test thread. The independent hit test thread is configured to perform an independent hit test to determine whether the input hit an element that is eligible for a particular action, and identify an interaction model associated with the input. The independent hit test thread also sends an indication of the interaction model to the manipulation thread to enable the manipulation thread to detect whether the particular action is triggered.

Abstract: Various embodiments enable repetitive gestures, such as multiple serial gestures, to be implemented efficiently so as to enhance the user experience. Other embodiments provide various approaches to zoom operations that consider a particular element's contextual surroundings in making a zoom decision that is designed to enhance the user experience and provide efficiently-zoomed content given a device's or rendering container's form factor.

Abstract: Instantiable gesture object techniques are described in which native gesture functionality is abstracted to applications using a script-based recognition interface. Gesture objects may be instantiated for different interaction contexts at the direction of applications programmed using dynamic scripting languages. Gesture objects can be configured to designate particular touch contacts and/or other inputs to consider for gesture recognition and a target element of content to which corresponding recognized gestures are applicable. After creation, gesture objects manage gesture processing operations on behalf of the applications including creating recognizers with the native gesture system, feeding input data for processing, and transforming raw gesture data into formats appropriate for the application and/or a target element. Accordingly, script-based applications may use the gesture objects to offload processing tasks associated with gesture recognition and take advantage of native gesture functionality.

Abstract: A timer is utilized in an input simulation process that simulates an input of one type when an input of a different type is received. In at least some embodiments, when a first type of input is received, a corresponding timer is started. If, before passage of an associated time period, a first input scenario is present, then one or more actions associated with the first input type are performed. If, on the other hand, after passage of the associated time period, a second input scenario is present, then one or more actions associated with a second input type are performed by using the first input type to simulate the second input type.

Abstract: Various embodiments enable performant cascading operations to be performed by selectively applying a subset of cascading operations to designated elements in a hierarchical tree, responsive to receiving an input associated with one of the elements. A full set of cascading operations can be performed, subsequent to performing the subset of cascading operations, in accordance with various parameters. Such parameters can include, by way of example and not limitation, user interaction timing, the complexities of the cascading operations for a given element, and/or the number of elements to which the cascading operations can be applied, to name just a few.

Abstract: In at least some embodiments, input provided by a single source generates events representing multiple source types through a mapping process, e.g. a touch input generates both touch and mouse events. By configuring the system to not recognize certain gestures, messages associated with the events of the different source types are then interleaved and provided to an associated application for processing. Efficiencies are gained by configuring the system to interleave the messages associated with the source types because messages of one source type can be processed sooner than if the messages of the one source type were queued up and sent in a non-interleaved fashion.

Abstract: Various embodiments enable repetitive gestures, such as multiple serial gestures, to be implemented efficiently so as to enhance the user experience. Other embodiments provide various approaches to zoom operations that consider a particular element's contextual surroundings in making a zoom decision that is designed to enhance the user experience and provide efficiently-zoomed content given a device's or rendering container's form factor.