Document that fade-out duration can't be modified through the speedFa…

…ctor

src/lib/core/ripple/ripple-renderer.ts

@@ -1,8 +1,10 @@
 import {ElementRef, NgZone} from '@angular/core';
 import {ViewportRuler} from '../overlay/position/viewport-ruler';
 
-
+/** Fade-in speed in pixels per second. Can be modified with the speedFactor option. */
 export const RIPPLE_SPEED_PX_PER_SECOND = 170;
+
+/** Fade-out speed for the ripples in milliseconds. This can't be modified by the speedFactor. */
 export const RIPPLE_FADE_OUT_DURATION = 600;
 
 /**

src/lib/core/ripple/ripple.ts

@@ -54,6 +54,7 @@ export class MdRipple implements OnChanges, OnDestroy {
   /**
    * If set, the normal duration of ripple animations is divided by this value. For example,
    * setting it to 0.5 will cause the animations to take twice as long.
+   * A changed speedFactor will not modify the fade-out duration of the ripples.
    */
   @Input('mdRippleSpeedFactor') speedFactor: number = 1;
 

src/lib/radio/radio.html

@@ -1,12 +1,12 @@
 <!-- TODO(jelbourn): render the radio on either side of the content -->
 <!-- TODO(mtlin): Evaluate trade-offs of using native radio vs. cost of additional bindings. -->
-<label [attr.for]="inputId" class="mat-radio-label">
+<label [attr.for]="inputId" class="mat-radio-label" #label>
   <!-- The actual 'radio' part of the control. -->
   <div class="mat-radio-container">
     <div class="mat-radio-outer-circle"></div>
     <div class="mat-radio-inner-circle"></div>
-    <div md-ripple *ngIf="!_isRippleDisabled()" class="mat-radio-ripple"
-         [mdRippleTrigger]="_getInputElement()"
+    <div mat-ripple *ngIf="!_isRippleDisabled()" class="mat-radio-ripple"
+         [mdRippleTrigger]="label"
          [mdRippleCentered]="true"
          [mdRippleSpeedFactor]="0.3"></div>
   </div>

src/lib/radio/radio.ts

@@ -503,10 +503,6 @@ export class MdRadioButton implements OnInit {
       }
     }
   }
-
-  _getInputElement() {
-    return this._inputElement.nativeElement;
-  }
 }