>>Why don't you create a component which uses the mixin instead of one that extends the mixin?
Well, I've already got that component. I'd like to simplify it and have better control over it, and am exploring my options. My thought would be to subclass it and apply its behavior to a textfield within the subclassed .tml
