Microsoft Technology Licensing, LLC

Facebook Technologies, LLC

Justin Rogers

Curtis Cheng-Cheng Man

Yong Qu

Nathan J E Furtwangler

Steven E Lucco

Miladin Pavlicic

Travis Leithead

Reza A Nourai

Markus W Mielke

Jacob Rossi

Matthew Allen Rakow

Praveen Kumar Muralidhar Rao

Tony Edward Schreiner

Eric M Lawrence

Bradley Joseph Litterell

Kevin Michael Babbitt

Arron J Eicholz

Sylvain Pierre Galineau

Henry F Bridge

Brandon C Furtwangler

Jane T Kim

Mirko Mandic

Rico Mariani

Stephen Harry Wright

Jason Joseph Weber

Li-Hsin Huang

Christian Fortini

Michael J Ens

Richard Keith James

Rossen Atanassov

Brian E Manthos

Samuel R Fortiner

Joshua Jacob Inch

R Scott Briggs

Sergey Z Malkin

Sandra G Roberts

Raju Ramanathan

Matthew P Kotsenas

Anjali S Parikh

Diana Liao

Yuanzhe Wang

Nirankush Panchbhai

Peter Salas

Siddhartha Prakash

Charu Chandiram

Reilly Donovan

Grant A Watters

Embodiments of a 3D web interaction system are disclosed that allow a user to select a content item from a browser, displayed in an artificial reality environment, and present a corresponding version of the content item in the artificial reality environment. The 3D web interaction system can create the version of the selected content item in different ways depending on whether the selected content item is associated with 3D content and, if so, the type of the associated 3D content. For example, the 3D web interaction system can create and present different versions of the selected content item depending on whether the selected content item is (a) not associated with 3D content, (b) associated with 'environment content,' or (c) associated with one or more 3D models.

3D interactions with web content

In one embodiment, a client system receives a request to access a user interface element in a virtual reality environment for an application and generates the user interface element in the virtual reality environment. The user interface element at the generated position occludes a portion of the application. The client system detects an input to move the user interface element from one position in the virtual reality environment to another position in the virtual reality environment relative to a display region of the application and stores position data associated with the other position of the virtual reality environment in a position database. The position data is associated with the application. The client system receives another request to access the user interface element in the virtual reality environment for the application and generates the user interface element in the virtual reality environment based on the position data associated with the application.

Prevention of user interface occlusion in a virtual reality environment

In one embodiment, a client system receives requests to display user interface elements in a virtual reality environment. The user interface elements being of the same type. The client system determines that the user interface elements include at least one user interface element generated by an operating system running on the client system. The client system determines that the user interface elements include at least one user interface element generated by a third-party application or based on third-party content. The client system displays the user interface elements with one or more predetermined indicators that allow a user to identify which of the user interface elements is generated by the operating system.

User interface security in a virtual reality environment

In one embodiment, a client system receives a request to display a user interface element in a virtual reality environment. The client system determines whether the requested user interface element is a system user interface element generated by an operating system running on the client system or a third-party user interface element that is generated by a third-party application or based on third-party content. The client system selectively displays the user interface element in a first dedicated plane or a second dedicated plane of the virtual reality environment. The requested user interface element is displayed in the first dedicated plane of the virtual reality environment upon determining that the requested user interface element is a system user interface element. The requested user interface element is displayed in the second dedicated plane of the virtual reality environment upon determining that the requested user interface element is a third-party user interface element.

Various embodiments provide an interface between a Web browser's layout engine and a scripting engine. The interface enables objects from the layout engine to be recognized by a memory manager in the scripting engine and interact in a streamlined, efficient manner. In accordance with one or more embodiments, the interface allows browser layout engine objects to be created as objects that are native to the scripting engine. Alternately or additionally, in some embodiments, the native objects are further configured to proxy functionality between the layout engine and the scripting engine.

Memory model for a layout engine and scripting engine

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

In at least some embodiments, a mechanism is provided for web developers to request specific default behaviors, such as touch behaviors, on their webpages. In at least some implementations, a Cascading Style Sheets (CSS) rule is utilized to enable or disable manipulations such as panning, pinch zoom, and double-tap-zoom manipulations. The mechanism can be extensible to accommodate additional default behaviors that are added in the future. In various embodiments, the behaviors are declared up front and thus differ from solutions which employ an imperative model. The declarative nature of this approach allows achievement of full independence from the main thread and deciding the correct response using independent hit testing.

Declarative style rules for default touch behaviors

Interface definition language extensions

An illustrative implementation is described for copying an identified portion of source content along with style information associated with the portion. The implementation allows the identified portion to be pasted into target content. By virtue of the extraction and retention of style information, the identified portion that is pasted into the target content visually resembles the identified portion as it appears in the source content. The implementation can identify relevant style information to be preserved based on a contextual analysis of style information applied to the source content. In one illustrative case, some of the style information may be revealed by parts of the content that are not directly demarcated by the identified portion.

Retaining style information when copying content

Security model for a layout engine and scripting engine

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

Techniques for synchronization points for state information are described. In at least some embodiments, synchronization points are employed to propagate state information among different processing threads. A synchronization point, for example, can be employed to propagate state information among different independently-executing threads. Accordingly, in at least some embodiments, synchronization points serve as inter-thread communications among different independently-executing threads.

Synchronization points for state information

Growing community of inventors

Redmond, WA, United States of America

Justin Rogers