[Compositor] Support Engine driven asynchronous commits to minimize round trips for sending compositor updates to client |
|||||||||||||
Issue descriptionCopied from tracking spreadsheet, could not find corresponding bug, please dupe if this was unnecessary.
,
Mar 28 2016
,
Apr 1 2016
Khushal, can you update the bug w/ a more complete description, please? Is the goal e.g. to mitigate latency effects?
,
Apr 1 2016
,
Apr 1 2016
,
Apr 1 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.
,
Oct 25 2016
This should be fixed with moving the split point to the cc embedder level, since that comes with a protocol change for a push model for frame updates from the engine.
,
Dec 9 2016
|
|||||||||||||
►
Sign in to add a comment |
|||||||||||||
Comment 1 by klo...@chromium.org
, Mar 28 2016Owner: khushals...@chromium.org
Status: Assigned (was: Untriaged)