title: Why does mx:states have trouble being resolved to a component implementation?
body: <p>Every now and then I get an error when I set up states in an MXML file.  The error I get says that mx:states could not be resolved to a component implementation.</p>
  
  <p>I read, at the following url, that this issue is caused by extending components - that somehow throws off the compiler's ability to resolve mx:states.  I don't see why this should be the case, but I don't have any answer of my own.  I also can't necessarily make this approach work with all of my extended components.</p>
  
  <p><a href="http://life.neophi.com/danielr/2007/01/could_not_resolve_to_a_compone.html" rel="nofollow noreferrer">http://life.neophi.com/danielr/2007/01/could_not_resolve_to_a_compone.html</a></p>
  
  <p>The workaround I've come up with is to not use any namespace.
  So, my code then looks like this:</p>
  
  <pre><code>&lt;states&gt;...&lt;/states&gt;
  </code></pre>
  
  <p>rather than:</p>
  
  <pre><code>&lt;mx:states&gt;...&lt;/mx:states&gt;
  </code></pre>
  
  <p>Making this stranger (at least, to me) is the fact that the children of the  tag -  - does not have this issue.  mx:states can not be resolved, but its child mx:State can.  And mx:SetProperty - a child of mx:State - is also resolved.</p>
  
  <p>Can anyone explain this, and/or offer a better solution to the problem than what I've come up with?</p>
  
  <p>Incidentally, I see the same issue with mx:transitions.</p>