FYI, patch 2508703002 from yesterday's comment 4 is still based on the currently used compositor path, it includes various code comments referring to things that will need changing when moving to compositor bypass, these are linked to this bug.
The current compositor bypass work in progress is here: https://codereview.chromium.org/2508583002/
I've reopened issue 655733 "WebVR mobile: render directly to the surface that we want" since that feature got deferred, it's blocked on issue 690106 "non-virtualized WebGL contexts cause screen tearing / out of sync WebVR frames".
New plan is to implement compositor bypass without directly drawing to the destination surface, this needs an extra copy but works around the sync issue.
Comment 1 by meganlindsay@chromium.org
, Oct 13 2016