                 
             case MouseEvent.MOUSE_UP:
             {
-				// If someone mouses up on us, then they must be hovered over 
-				// us now.
+                // If someone mouses up on us, then they must be hovered over 
+                // us now.
                 hovered = true;
                 
                 if (mouseCaptured)

 *  if they should be in the up, over, or down states.
 * 
 *  <p>As the state changes, if the transition should play, the 
 *  playTransitions 
 * 
 *  @see spark.components.supportClasses.InteractionState
 *  

     *  the renderer was actually selected.
     */
    private var mouseUpDeselectTimer:Timer;
    
    /**
     *  @private
     *  Whether the component using this InteractionStateDetector should 
     *  play transitions on a particular state change.
     * 
     *  <p>This could be moved to the CHANGE event itself, but 
     *  seeing as we don't have a formal mechanism for dealing with ItemRenderer
     *  transitions in the first place, this seems like an acceptable solution.<p>
     * 
     *  <p>Currently, InteractionStateDetector is the one who would know whether a 
     *  transition should play or not because it knows how it got in to a particular 
     *  state and that's what we use to determine whether transitions play or not.  
     *  For instance, if a scroll starts while you're in the down state, that should 
     *  cancel the down state and not play a transition.</p>
     */
    mx_internal var playTransitions:Boolean = true;
    
    //--------------------------------------------------------------------------
    //
