Investigate if there's a way to get an actual max supported size, or if excessive sizes get cleanly rejected by existing code.
Revisit if we can support zero size, or alternatively we could resize to a minimum of 1x1 pixels.

we should avoid getting to the point where we pass 0. My understanding is that there is some sort of race that should be handled in Blink instead. - ddorwin@

More explicitly, IIRC, the cause of potential 0s is an initialization race in Blink.

The zero sizes should be addressed by  issue 836496 . We can focus on the maximum size here.

This is blocked on figuring out how to create a centralized way of getting memory / size limits for textures based on system data (see 845742).

Removing Blink>WebVR component and assigning to Blink>WebXR 

Removing Blink>WebVR component and assigning to Blink>WebXR 

based on perceived impact, triage did not think this was required (must/should).

Will be affected by AR Mode