New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 793080 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android , Windows
Pri: 1
Type: Feature
Proj-XR



Sign in to add a comment

Measure runtime type for non-presenting

Project Member Reported by billorr@chromium.org, Dec 7 2017

Issue description

VRViewerType is only measured when we enter VR (presenting either webvr or vr browsing).

We should measure something when devices are used for magic window as well.

Figure out what we want to measure and consider a new metric to measure that.

Maybe we should record the device returned by navigator.xr.requestDevice.  It could be handled by the vrdevicemanager in the browser process, or in blink.
 
Cc: offenwanger@chromium.org bajones@chromium.org ddorwin@chromium.org billorr@chromium.org
Cc: tiborg@chromium.org
Labels: VR-metrics M-65
Note that it's not just magic window, though we could also track that. This would be anytime a device is returned. That may be for magic window, it may eventually be used for presentation, or it may just be obtained and never used for presentation (e.g., because the user never decided to enter VR presentation).
Labels: -Pri-3 Pri-2
Status: Assigned (was: Untriaged)
Labels: -M-65 M-66
Labels: -Type-Bug -Pri-2 Pri-1 Type-Feature

Comment 6 by sko...@chromium.org, Feb 27 2018

Labels: -M-66 M-68
Don't think this is required for M66 or MVP browser.
Labels: -M-68
Removing milestone to prevent continually pushing it out.


Summary: Measure runtime type for non-presenting (was: Measure VRViewerType for non-presenting)
Measure usage for ARCore, GVR, orientation sensor for magic window usage.
Components: Internals>XR
Removing Internals>VR component and assigning to Internals>XR
Components: -Internals>VR

Sign in to add a comment