If someone is watching a video in VR can we use the _exact_ same metrics and just have a isVR bit?

If we can, that is ideal, but we have to decide what components we want to know about VR.

I don't believe UMA supports arbitrary extra data associated with the histogram, but that is something we could work around (multiple histograms, interpret the highest bit as InVR, add support for an extra bit, stick it in metadata with os info, etc).

For UKMs we could use the same events and just add another metric - InVr.

Marking myself as owner so it isn't unowned.  Changing to M67 as the existing metrics have worked for several milestones, and fixing for M66 isn't critical.  Please change milestone back or let me know if 66 is critical.

Not worth merging a fix back, but we should address this soonish.

Removing milestone to prevent repeatedly pushing back.

What we are measuring is close to the same as video metrics, but we should merge code so we are measuring exactly the same.

Removing Internals>VR component and assigning to Internals>XR