User interface security in a virtual reality environment

1. A method comprising, by a client system:

receiving a request to display a user interface element in a virtual reality environment;

determining 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; and

selectively displaying the user interface element in a first dedicated plane or a second dedicated plane of the virtual reality environment, wherein:

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; or

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;

wherein the first dedicated plane is distinct from the second dedicated plane.

2. The method of claim 1 , further comprising:

receiving, from a first third-party application, a request to access sensor data;

determining whether the first third-party application is a presently active application, wherein the presently active application is a current application with which a user associated with the client system is interfacing;

based on the determination of whether the first third-party application is the presently active application, selectively authorizing or preventing the third-party application from receiving sensor data, wherein:

the first third-party application is authorized to receive sensor data from the client system upon determining the first third-party application is the presently active application; or

the first third-party application is prevented from receiving sensor data from the client system upon determining the first third-party application is not the presently active application; and

sending the sensor data to the first third-party application in response to determining the first third-party application is authorized to receive sensor data.

3. The method of claim 2 , wherein the sensor data includes at least one of gyroscope data, accelerometer data, magnetometer data, or eye tracking data.

4. The method of claim 2 , further comprising:

receiving authorization from the user to authorize a second third-party application to receive sensor data from the client system; and

sending, while the first third-party application is the presently active application the sensor data to the second third-party application based on the authorization.

5. The method of claim 2 , wherein the authorizing of the first third-party application to receive sensor data from the client system is based on a determination that the user interface element is requested by the first third-party application.

6. The method of claim 2 , wherein the preventing of the first third-party application from receiving sensor data is based on a determination that the user interface element is not requested by the first third-party application.

7. The method of claim 2 , wherein one or more third-party applications are placed on a list to automatically authorize the one or more third-party applications to receive sensor data.

8. The method of claim 2 , wherein one or more third-party applications are placed on a list to automatically prevent the one or more third-party applications from receiving sensor data.

9. The method of claim 1 , wherein the first dedicated plane is dedicated to displaying system user interface elements generated by the operating system.

10. The method of claim 1 , wherein the first dedicated plane has a different depth relative to a viewpoint of a user than the second dedicated plane.

11. The method of claim 10 , wherein the first dedicated plane is closer to the viewpoint of the user than the second dedicated plane.

12. One or more computer-readable non-transitory storage media embodying software that is operable when executed to:

receive a request to display a user interface element in a virtual reality environment;

determine 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; and

selectively display the user interface element in a first dedicated plane or a second dedicated plane of the virtual reality environment, wherein:

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; or

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;

wherein the first dedicated plane is distinct from the second dedicated plane.

13. The media of claim 12 , wherein the software is further operable when executed to:

receive, from a first third-party application, a request to access sensor data;

determine whether the first third-party application is a presently active application, wherein the presently active application is a current application with which a user associated with the client system is interfacing;

based on the determination of whether the first third-party application is the presently active application, selectively authorize or prevent the third-party application from receiving sensor data, wherein:

the first third-party application is authorized to receive sensor data from the client system upon determining the first third-party application is the presently active application; or

the first third-party application is prevented from receiving sensor data from the client system upon determining the first third-party application is not the presently active application; and

send the sensor data to the first third-party application in response to determining the first third-party application is authorized to receive sensor data.

14. The media of claim 12 , wherein the first dedicated plane is dedicated to displaying system user interface elements generated by the operating system.

15. The media of claim 12 , wherein the first dedicated plane has a different depth relative to a viewpoint of a user than the second dedicated plane.

16. A system comprising: one or more processors; and a non-transitory memory coupled to the processors comprising instructions executable by the processors, the processors operable when executing the instructions to:

receive a request to display a user interface element in a virtual reality environment;

determine 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; and

selectively display the user interface element in a first dedicated plane or a second dedicated plane of the virtual reality environment, wherein:

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; or

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;

wherein the first dedicated plane is distinct from the second dedicated plane.

17. The system of claim 16 , wherein the processors are further operable when executing the instructions to:

receive, from a first third-party application, a request to access sensor data;

determine whether the first third-party application is a presently active application, wherein the presently active application is a current application with which a user associated with the client system is interfacing;

based on the determination of whether the first third-party application is the presently active application, selectively authorize or prevent the third-party application from receiving sensor data, wherein:

the first third-party application is authorized to receive sensor data from the client system upon determining the first third-party application is the presently active application; or

the first third-party application is prevented from receiving sensor data from the client system upon determining the first third-party application is not the presently active application; and

send the sensor data to the first third-party application in response to determining the first third-party application is authorized to receive sensor data.

18. The system of claim 16 , wherein the first dedicated plane is dedicated to displaying system user interface elements generated by the operating system.

19. The system of claim 16 , wherein the first dedicated plane has a different depth relative to a viewpoint of a user than the second dedicated plane.

20. The system of claim 19 , wherein the first dedicated plane is closer to the viewpoint of the user than the second dedicated plane.