@title User Input @intro User input triggers DOM events. We listen to those events with event bindings that funnel updated values back into our components and models. @description User actions such as clicking a link, pushing a button, and entering text raise DOM events. This page explains how to bind those events to component event handlers using the Angular event binding syntax. Run the . ## Binding to user input events You can use [Angular event bindings](guide/template-syntax#event-binding) to respond to any [DOM event](https://developer.mozilla.org/en-US/docs/Web/Events). Many DOM events are triggered by user input. Binding to these events provides a way to get input from the user. To bind to a DOM event, surround the DOM event name in parentheses and assign a quoted [template statement](guide/template-syntax#template-statements) to it. The following example shows an event binding that implements a click handler: {@a click} The `(click)` to the left of the equals sign identifies the button's click event as the **target of the binding**. The text in quotes to the right of the equals sign is the **template statement**, which responds to the click event by calling the component's `onClickMe` method. When writing a binding, be aware of a template statement's **execution context**. The identifiers in a template statement belong to a specific context object, usually the Angular component controlling the template. The example above shows a single line of HTML, but that HTML belongs to a larger component: When the user clicks the button, Angular calls the `onClickMe` method from `ClickMeComponent`. ## Get user input from the $event object DOM events carry a payload of information that may be useful to the component. This section shows how to bind to the `keyup` event of an input box to get the user's input after each keystroke. The following code listens to the `keyup` event and passes the entire event payload (`$event`) to the component event handler. When a user presses and releases a key, the `keyup` event occurs, and Angular provides a corresponding DOM event object in the `$event` variable which this code passes as a parameter to the component's `onKey()` method. The properties of an `$event` object vary depending on the type of DOM event. For example, a mouse event includes different information than a input box editing event. All [standard DOM event objects](https://developer.mozilla.org/en-US/docs/Web/API/Event) have a `target` property, a reference to the element that raised the event. In this case, `target` refers to the [`` element](https://developer.mozilla.org/en-US/docs/Web/API/HTMLInputElement) and `event.target.value` returns the current contents of that element. After each call, the `onKey()` method appends the contents of the input box value to the list in the component's `values` property, followed by a separator character (|). The [interpolation](guide/template-syntax#interpolation) displays the accumulating input box changes from the `values` property. Suppose the user enters the letters "abc", and then backspaces to remove them one by one. Here's what the UI displays: a | ab | abc | ab | a | |

{@a keyup1} ### Type the _$event_ The example above casts the `$event` as an `any` type. That simplifies the code at a cost. There is no type information that could reveal properties of the event object and prevent silly mistakes. The following example rewrites the method with types: The `$event` is now a specific `KeyboardEvent`. Not all elements have a `value` property so it casts `target` to an input element. The `OnKey` method more clearly expresses what it expects from the template and how it interprets the event. ### Passing _$event_ is a dubious practice Typing the event object reveals a significant objection to passing the entire DOM event into the method: the component has too much awareness of the template details. It can't extract information without knowing more than it should about the HTML implementation. That breaks the separation of concerns between the template (_what the user sees_) and the component (_how the application processes user data_). The next section shows how to use template reference variables to address this problem. ## Get user input from a template reference variable There's another way to get the user data: use Angular [**template reference variables**](guide/template-syntax#ref-vars). These variables provide direct access to an element from within the template. To declare a template reference variable, precede an identifier with a hash (or pound) character (#). The following example uses a template reference variable to implement a keystroke loopback in a simple template. The template reference variable named `box`, declared on the `` element, refers to the `` element itself. The code uses the `box` variable to get the input element's `value` and display it with interpolation between `

` tags. The template is completely self contained. It doesn't bind to the component, and the component does nothing. Type something in the input box, and watch the display update with each keystroke.

**This won't work at all unless you bind to an event**. Angular updates the bindings (and therefore the screen) only if the app does something in response to asynchronous events, such as keystrokes. This example code binds the `keyup` event to the number 0, the shortest template statement possible. While the statement does nothing useful, it satisfies Angular's requirement so that Angular will update the screen.

It's easier to get to the input box with the template reference variable than to go through the `$event` object. Here's a rewrite of the previous `keyup` example that uses a template reference variable to get the user's input. A nice aspect of this approach is that the component gets clean data values from the view. It no longer requires knowledge of the `$event` and its structure. {@a key-event} ## Key event filtering (with `key.enter`) The `(keyup)` event handler hears *every keystroke*. Sometimes only the _Enter_ key matters, because it signals that the user has finished typing. One way to reduce the noise would be to examine every `$event.keyCode` and take action only when the key is _Enter_. There's an easier way: bind to Angular's `keyup.enter` pseudo-event. Then Angular calls the event handler only when the user presses _Enter_. Here's how it works.

## On blur In the previous example, the current state of the input box is lost if the user mouses away and clicks elsewhere on the page without first pressing _Enter_. The component's `value` property is updated only when the user presses _Enter_. To fix this issue, listen to both the _Enter_ key and the _blur_ event. ## Put it all together The previous page showed how to [display data](guide/displaying-data). This page demonstrated event binding techniques. Now, put it all together in a micro-app that can display a list of heroes and add new heroes to the list. The user can add a hero by typing the hero's name in the input box and clicking **Add**.

Below is the "Little Tour of Heroes" component. ### Observations * **Use template variables to refer to elements** — The `newHero` template variable refers to the `` element. You can reference `newHero` from any sibling or child of the `` element. * **Pass values, not elements** — Instead of passing the `newHero` into the component's `addHero` method, get the input box value and pass *that* to `addHero`. * **Keep template statements simple** — The `(blur)` event is bound to two JavaScript statements. The first statement calls `addHero`. The second statement, `newHero.value=''`, clears the input box after a new hero is added to the list. ## Source code Following is all the code discussed in this page.

## Summary You have mastered the basic primitives for responding to user input and gestures. These techniques are useful for small-scale demonstrations, but they quickly become verbose and clumsy when handling large amounts of user input. Two-way data binding is a more elegant and compact way to move values between data entry fields and model properties. The next page, `Forms`, explains how to write two-way bindings with `NgModel`.