Just adding some thoughts after looking at this from the related code review.

IIRC metrics are handled on the basis of a session which has a timeout.  If you come back to vr after having done something else for a while it should create a new session.

Ideally a session does include navigation across multiple sites and tabs as long as the user is still actively engaged so this does sound like something we should do, but I think it only needs to include what the user actually focuses on (ie if the user has 20 tabs open we don't need to create an observer on all of them until they actually switch to them in vr).

I think the metrics helper could probably track multiple web contents and maybe drop older web contents after some timeout similar to how it ends sessions now.

Bill will have more context on what works best here though, and I'm not sure if the above suggestion ends up being problematic in some way.

Removing issue 706436 as blocked on this since the v0 browser does not support tab switching from within VR.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

 Issue 817559 , which affects native pages, may be related.