Split ContentViewCore for Blimp |
||||||||||||
Issue description- Create a ContentViewCore base class and a Content and Blimp subclass for each content source. - Pull out RWHVA and WC specific code to the content subclass. - Add BlimpHostView and BlimpContents code to the Blimp subclass. - Share as much as the view logic and marshalling as we can. - Pull out Chrome text entry code to the content subclass since we need custom text entry for Blimp.
,
May 11 2016
,
May 16 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 20 2016
,
Jul 10 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
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
This is a long running task. Moving this to M-56.
,
Aug 23 2016
,
Sep 6 2016
,
Nov 16 2016
No longer relevant.
,
Dec 9 2016
|
||||||||||||
►
Sign in to add a comment |
||||||||||||
Comment 1 by dtrainor@chromium.org
, May 11 2016