Microsoft Technology Licensing, LLC

Facebook Technologies, LLC

Jacob Rossi

Justin Rogers

Michael J Ens

Michael J Patten

Stephen Harry Wright

Nathan J E Furtwangler

Matthew Allen Rakow

Joshua Jacob Inch

Jordan Dale Andersen

Raju Ramanathan

Reed L Townsend

Jane T Kim

Mirko Mandic

Lawrence William Osterman

Hirofumi Yamamoto

Krishnan Menon

Sandra G Roberts

Alan Stephenson

Pak Kiu Chung

Charu Chandiram

Siddhartha Prakash

John C Jansen

Systems and methods for rendering VR content at a VR rendering device include identifying, by a content facilitator, that that first content presented via a first device to a user includes metadata indicating availability of second content. The second content includes at least one of a three-dimensional (3D) video, 360&#xb0; image, or virtual reality (VR) content. The content facilitator provides an interface element to the user at the first device responsive to the metadata indicating availability of the second content. The content facilitator receives a user selection of the interface element. The content facilitator provides access to the second content via a VR rendering device for the user responsive to the user selection. The VR rendering device is configured to render the second content.

Saving content for viewing on a virtual reality rendering device

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.

Virtual tabs supporting web content suspension

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.

Web resource compatibility with web applications

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.

Supporting different event models using a single input source

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.

Instantiable gesture objects

In one embodiment, a unified pointer messagemay describe in a single type of pointer message a coordinate input from a user via multiple types of pointer devices. An input device interfacemay receive a coordinate inputfrom an input device. A processormay execute an application programming interface layerthat creates a unified pointer messagefor the coordinate input. The processormay send the unified pointer messageto an application. The processormay process a device specific data setunhandled by the application.

Device specific data in a unified pointer message

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.

Input pointer delay and zoom logic

Growing community of inventors

Seattle, WA, United States of America

Jacob Rossi