Focus on newly added input element


I have a new Angular 2 app with a list of input boxes. When the user hits the return key, I add a new input box immediately after the one they’re currently editing. Or rather, I (asynchronously) add a new entry to the array in the model, which causes Angular 2 to automatically generate a new input box in the near future.

How can I make it so that input focus changes to the newly added element automatically?

Alternatively, I get a reference to the model object that’s causing the DOM to be generated. From the component code, is there a way to search for a DOM element representing a particular model object?

Here’s my code to just make this work. Hopefully this is offensive enough to some Angular 2 devs to encourage a reply 🙂

app.WordComponent = ng.core
        selector: 'word-editor',
        template:'<input type="text" [value]="word.word" (input)="word.update($" (keydown)="keydown($event)"/>',
            function() {
        keydown:function(e) {
            if(e.which == 13) {
                var ul =;
                var childCount = ul.childNodes.length;

                this.list.addWord("").then(function(word) {
                    var interval = setInterval(function() {
                        if(childCount < ul.childNodes.length) {
                    }, 1);




If I’m allowed to do so, I will take part of @Sasxa answer and modify it to make it more like what you’re looking for.

A few changes

  • I will use a ngFor so angular2 adds the new input instead of doing it myself. The main purpose is just to make angular2 to iterate over it.
  • Instead of ViewChild I’m going to use ViewChildren that returns a QueryList which has a changes property. This property is an Observable and it returns the elements after they’ve changed.

Since in ES5, we have no decorators we have to use the queries property to use ViewChildren


    selector: 'cmp',
    template : `
            // We use a variable so we can query the items with it
            <input #input (keydown)="add($event)" *ngFor="#input of inputs">
    queries : {
        vc : new ng.core.ViewChildren('input')

Focus on the last element.

ngAfterViewInit: function() { => {


Like I said before, ViewChildren returns a QueryList which contains changes property. When we subscribe to it everytime it changes it will return the list of elements. The list elements contains a last property (among others) that in this case returns the last element, we use nativeElement on it and finally focus()

Add input elements This is for pure convenince, the inputs array has no real purpose more than redraw the ngFor.

add: function(key) {
    if(key.which == 13) {
        // See plnkr for "this.inputs" usage

We push a dummy item on the array so it redraws.

Example using ES5 :

Example using ES6/TS :

Update 29/03/2016

Time has passed, things have been clarified and there are always best practices to learn/teach. I’ve simplified this answer by changing a few things

  • Instead of using @ViewChildren and subscribing to it I made a Directive that will be instatiated everytime a new input is created
  • I’m using Renderer to make it WebWorker safe. The original answer accesses focus() directly on the nativeElement which is discouraged.
  • Now I listen to keydown.enter which simplifies the key down event, I don’t have to check which value.

To the point. The component looks like (simplified, full code on the plnkrs below)

  template: `<input (keydown.enter)="add()" *ngFor="#input of inputs">`,

add() {

And the directive

  selector : 'input'
class MyInput {
  constructor(public renderer: Renderer, public elementRef: ElementRef) {}

  ngOnInit() {
      this.elementRef.nativeElement, 'focus', []);

As you can see I’m calling invokeElementMethod to trigger focus on the element instead of accessing it directly.

This version is much cleaner and safer than the original one.

plnkrs updated to beta 12

Example using ES5 :

Example using ES6/TS :

Update 2018

invokeElementMethod is deprecated. Use Renderer2 instead of Renderer.

Give your element an id, and you can use selectRootElement:



  • 1

    Very elegant. I’m surprised that we can use the same local template variable name/identifier — #input — on multiple elements.

    Feb 9, 2016 at 4:04

  • 1

    I would rename the ngFor local template variable something else, so that it doesn’t look like it is related to the other #input: *ngFor="#in of inputs".

    Feb 9, 2016 at 4:04

  • 1

    Instead of adding an event handler to every input, I suggest putting it on the div and letting the event bubble up: <div (keydown)="add($event)"> <input #input *ngFor="#in of inputs">.

    Feb 9, 2016 at 4:05

  • 1

    For the 2018 update, instead of using an ID, I found this to work: this.renderer2.selectRootElement(this.elementRef.nativeElement).focus();

    Aug 20, 2018 at 19:55


Take a look at ViewChild, here’s a example.
This might be what you’re looking for:

import {Component, ViewChild} from 'angular2/core'

  selector: 'my-app',
  providers: [],
  template: `
      <input #name>
  directives: []
export class App {

  @ViewChild('name') vc: ElementRef;

  ngAfterViewInit() {;


  • still good in Angular 6 and omitting “ElementRef” ViewChild type declaration not a problem or for the vscode linter

    Jul 23, 2018 at 16:40

  • The only code that worked for me, thanks.

    Nov 30, 2021 at 4:38


With inline angular code, focus after conditional paint:

  <span *ngIf="">
    <input #taskEditText type="text" [(ngModel)]="editTask" (keydown.enter)="save()" (keydown.esc)="saveCancel()"/>
    <button (click)="save()">Save</button>
    <button (click)="saveCancel()">Cancel</button>