docs(user-input): misc fixes (#2430)

- Remove nonexistent `<important>` “element” since it causes problems
for ng2.io. This is probably a typo. It was more likely meant to be an
anchor name than an element name.
- Fix two PENDING links.
This commit is contained in:
Patrice Chalin 2016-09-21 08:48:38 -07:00 committed by Kathy Walrath
parent 8d756808b9
commit 36a3ea2c21
1 changed files with 2 additions and 3 deletions

View File

@ -23,7 +23,7 @@ include ../_util-fns
:marked :marked
The `(click)` to the left of the equal sign identifies the button's click event as the **target of the binding**. The `(click)` to the left of the equal sign identifies the button's click event as the **target of the binding**.
The text within quotes on the right is the **template statement** in which we The text within quotes on the right is the **template statement** in which we
respond to the click event by calling the component's `onClickMe` method. A template statement <!-- PENDING: link to ./template-syntax.html#template-statements --> is a subset respond to the click event by calling the component's `onClickMe` method. A [template statement](./template-syntax.html#template-statements) is a subset
of Dart with restrictions and a few added tricks. of Dart with restrictions and a few added tricks.
When writing a binding we must be aware of a template statement's **execution context**. When writing a binding we must be aware of a template statement's **execution context**.
@ -49,7 +49,6 @@ include ../_util-fns
which we pass to the component's `onKey()` method. which we pass to the component's `onKey()` method.
The user data we want is in that variable somewhere. The user data we want is in that variable somewhere.
important
.callout.is-important .callout.is-important
header $event vs. \$event header $event vs. \$event
:marked :marked
@ -67,7 +66,7 @@ important
The `onKey()` component method is where we extract the user's input The `onKey()` component method is where we extract the user's input
from the event object, adding that input to the list of user data that we're accumulating in the component's `values` property. from the event object, adding that input to the list of user data that we're accumulating in the component's `values` property.
We then use interpolation <!-- PENDING: link to ./template-syntax.html#interpolation) --> We then use [interpolation](./template-syntax.html#interpolation)
to display the accumulating `values` property back on screen. to display the accumulating `values` property back on screen.
Enter the letters "abc", and then backspace to remove them. Enter the letters "abc", and then backspace to remove them.