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

Issue 803636 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Task
Proj-VR
Proj-XR



Sign in to add a comment

Create a new.crbug.com template for VR

Project Member Reported by ddorwin@chromium.org, Jan 18 2018

Issue description

There are specific details we'd like to have included in bug reports for VR browsing and WebVR/WebXR. We should create a template that asks the relevant questions and sets VR labels.

Possible content:
* Device manufacturer & model (host)
* GPU model [1]
* OS and version
* Headset type
* Controller type
* VR runtime and version

We should probably assign it to Components: Internals>VR and label Proj-VR by default.

It would be nice if we could directly link to this template (not using the URL query parameters) so we can provide it on Slack, etc.

[1] In some cases, we might want to ask the user to include data from chrome://gpu. For example, we could say, "If this is related to rendering, performance, or feature availability, please include output from chrome://gpu."
 
Components: Internals>XR
Removing Internals>VR component and assigning to Internals>XR
Components: -Internals>VR

Sign in to add a comment