interactionSpace -> interactionMode

Manishearth · toji · commit a1c0eba0faae · 2020-03-27T10:28:50.000-07:00
diff --git a/ar-module-explainer.md b/ar-module-explainer.md
@@ -70,27 +70,27 @@ function drawScene() {
 
 ### Drawing UI elements
 
-The AR module supports a variety of device form factors, including "handheld" phone AR as well as "headworn" glasses-style AR. If the application wishes to show UI elements to the user, it needs to be done differently based on the form factor. This information is exposed through `XRSession`'s `interactionSpace` attribute.
+The AR module supports a variety of device form factors, including "handheld" phone AR as well as "headworn" glasses-style AR. If the application wishes to show UI elements to the user, it needs to be done differently based on the form factor. This information is exposed through `XRSession`'s `interactionMode` attribute.
 
-For handheld devices, the UI elements probably should be drawn directly to the screen in screen-space coordinates, without applying any projections. In such a case, `interactionSpace` will report `"screen-space"`.
+For handheld devices, the UI elements probably should be drawn directly to the screen in screen-space coordinates, without applying any projections. In such a case, `interactionMode` will report `"screen-space"`.
  
-For headworn devices, the UI elements probably should be drawn in the world space, perhaps at some distance from the user's head so that they may easily interact with it. In such a case, `interactionSpace` will report `"world-space"`.
+For headworn devices, the UI elements probably should be drawn in the world space, perhaps at some distance from the user's head so that they may easily interact with it. In such a case, `interactionMode` will report `"world-space"`.
 
 The <a href="https://immersive-web.github.io/dom-overlays/">WebXR DOM Overlays module</a>, if implemented for the device, is able to automatically place UI for both handheld and headworn sessions. However, it is only useful if you wish to do your UI as DOM elements as opposed to using graphics primitives and input source selection events.
 
 ```js
 function drawScene() {
   // draw the rest of the scene
 
-  if (xrSession.interactionSpace == "world-space") {
+  if (xrSession.interactionMode == "world-space") {
     // Add UI elements to actual scene
   } else {
     // Draw UI elements directly to screen
   }
 }
 
 xrSession.onselect = function(e) {
-  if (xrSession.interactionSpace == "world-space") {
+  if (xrSession.interactionMode == "world-space") {
     // intersect the target ray with the UI elements in world space
     // to determine which UI element, if any, was selected
   } else {
@@ -127,6 +127,6 @@ enum XRInteractionSpace {
 
 partial interface XRSession {
   readonly attribute XREnvironmentBlendMode environmentBlendMode;
-  readonly attribute XRInteractionSpace interactionSpace;
+  readonly attribute XRInteractionSpace interactionMode;
 }
 ```
diff --git a/index.bs b/index.bs
@@ -206,15 +206,15 @@ enum XRInteractionSpace {
 
 partial interface XRSession {
   // Attributes
-  readonly attribute XRInteractionSpace interactionSpace;
+  readonly attribute XRInteractionSpace interactionMode;
 };
 </pre>
 
-The <dfn attribute for="XRSession">interactionSpace</dfn> attribute describes the best space (according to the user agent) for the application to draw interactive UI for the current session.
+The <dfn attribute for="XRSession">interactionMode</dfn> attribute describes the best space (according to the user agent) for the application to draw interactive UI for the current session.
 
- - An {{XRSession/interactionSpace}} value of {{XRInteractionSpace/"screen-space"}} indicates that the UI should be drawn directly to the screen without projection. Typically in this scenario, {{select!!event}} events are triggered with {{XRInputSourceEvent/inputSource}}s having an {{XRInputSource/targetRayMode}} of {{XRTargetRayMode/"screen"}}.
+ - An {{XRSession/interactionMode}} value of {{XRInteractionSpace/"screen-space"}} indicates that the UI should be drawn directly to the screen without projection. Typically in this scenario, {{select!!event}} events are triggered with {{XRInputSourceEvent/inputSource}}s having an {{XRInputSource/targetRayMode}} of {{XRTargetRayMode/"screen"}}.
 
- - An {{XRSession/interactionSpace}} value of {{XRInteractionSpace/"world-space"}} indicates that the UI should be drawn in the world, some distance from the user, so that they may interact with it using controllers. Typically in this scenario, {{select!!event}} events are triggered with {{XRInputSourceEvent/inputSource}}s having an {{XRInputSource/targetRayMode}} of {{XRTargetRayMode/"tracked-pointer"}} or {{XRTargetRayMode/"gaze"}}.
+ - An {{XRSession/interactionMode}} value of {{XRInteractionSpace/"world-space"}} indicates that the UI should be drawn in the world, some distance from the user, so that they may interact with it using controllers. Typically in this scenario, {{select!!event}} events are triggered with {{XRInputSourceEvent/inputSource}}s having an {{XRInputSource/targetRayMode}} of {{XRTargetRayMode/"tracked-pointer"}} or {{XRTargetRayMode/"gaze"}}.
 
 Note: The <a href="https://immersive-web.github.io/dom-overlays/">WebXR DOM Overlays module</a>, if supported, can be used in some of these cases instead.
 
