VR: Investigate when to lock the compositor |
||||
Issue descriptionhttps://chromium-review.googlesource.com/c/chromium/src/+/832959 has some great information about compositor locking and the Android preview window. We should rethink how we handle resizes and initialization in VR.
,
Feb 7 2018
@mthiesse, if we're targeting M66 and its P1, it should have an owner. Do you know who will be investigating this?
,
Feb 7 2018
Less urgent that I fixed double resizing. Maybe nothing to do here, but we should at least investigate.
,
May 15 2018
Removing M-67 milestone during a triage sweep with ericde@. A milestone should be reassigned when the issue is in scope.
,
Jun 27 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by mthiesse@chromium.org
, Jan 17 2018