Text in radio button 'jumps out' on hover

I think it is a bug in the end-user-experience perspective, but I don't think it will fit Articulate's definition of a bug. They'll think of it as a "feature" that all variables of the text box get carried over. Part of the problem is a lack of clarity on what a "state" is. The object isn't a "master". You can edit the normal state and paste something into the state, and it does not copy over to all of the "child-but-not-children" states. The states behave more like groups with built-in triggers; but then Articulate hasn't committed to that UX either, as you can't access that group in the timeline. Articulate has done us the "favor" of treating states like groups when it comes to focus order; that is, not including the child-but-not-children objects (so frustrating).

So my understanding of the solution, in order:

1) Submit "another" feature request that grouped objects appear in the focus order

2) Then submit a feature request that states get a UI treatment that better parallels their UX behavior as groups.

3) Then submit "another" feature request that "set as default" actually applies the variables of the text box as well.