[Compositor] Restructure input pipeline to use engine driven commits? |
||||||||||||
Issue descriptionCopied from tracking spreadsheet, could not find corresponding bug, please dupe if this was unnecessary.
,
Apr 1 2016
Khushal, can you elaborate on the context for this?
,
Apr 1 2016
The input events require an unnecessary round trip to get the compositor frame pushed to the client. If we have commits that can be initiated by the engine, we would need to restructure the input pipeline to inform the engine compositor to push a commit.
,
Apr 1 2016
,
Apr 1 2016
,
May 23 2016
,
May 25 2016
[Bulk edit] Setting tracking label Blimp-M53-Proj-Scope. This label is for scope tracking purposes only and should not be added / removed from any bugs, even if we add additional bugs to M-53 scope, or remove this bug from M-53 scope.
,
Jun 3 2016
,
Jul 13 2016
,
Jul 26 2016
[Bulk edit] Setting tracking label Blimp-M54-Proj-Scope. This label is for scope tracking purposes only and should not be added / removed from any bugs, even if we add additional bugs to M-54 scope, or remove this bug from M-54 scope.
,
Aug 23 2016
Moving to M-56. Not blocking 0.6.
,
Nov 29 2016
Obsolete, WontFix.
,
Dec 9 2016
|
||||||||||||
►
Sign in to add a comment |
||||||||||||
Comment 1 by klo...@chromium.org
, Mar 28 2016Cc: dtrainor@chromium.org klo...@chromium.org
Owner: khushals...@chromium.org
Status: Assigned (was: Untriaged)