Chrome Controls

edited January 2012 in Enyo 2
Noticed that controls with chrome do not work the same in v2 as in v1. In v1, you used the special chrome member to declare those components. In v2, any components declared in a kind are treated as chrome if one of them is named "client" (or whatever controlParentName is).

The consequence of this is when you declare a kind (Kind A) that inherits from another kind (Kind B), any components declared in Kind A override those declared in Kind B rather than placed within Kind B's "client" control. I tried to illustrate this in a jsfiddle example. Hopefully the example is more clear than my explanation.


Sign In or Register to comment.