Template Refs
While Vue's declarative rendering model abstracts away most of the direct DOM operations for you, there may still be cases where we need direct access to the underlying DOM elements. To achieve this, we can use the special
ref
attribute:
ref
is a special attribute, similar to the
key
attribute discussed in the
v-for
chapter. It allows us to obtain a direct reference to a specific DOM element or child component instance after it's mounted. This may be useful when you want to, for example, programmatically focus an input on component mount, or initialize a 3rd party library on an element.
Accessing the Refs
To obtain the reference with Composition API, we need to declare a ref with the same name:
If not using
<script setup>
, make sure to also return the ref from
setup()
:
Note that you can only access the ref
after the component is mounted.
If you try to access
input
in a template expression, it will be
null
on the first render. This is because the element doesn't exist until after the first render!
If you are trying to watch the changes of a template ref, make sure to account for the case where the ref has
null
value:
See also: Typing Template Refs
Refs inside
v-for
Requires v3.2.25 or above
When
ref
is used inside
v-for
, the corresponding ref should contain an Array value, which will be populated with the elements after mount:
It should be noted that the ref array does not guarantee the same order as the source array.
Function Refs
Instead of a string key, the
ref
attribute can also be bound to a function, which will be called on each component update and gives you full flexibility on where to store the element reference. The function receives the element reference as the first argument:
Note we are using a dynamic
:ref
binding so we can pass it a function instead of a ref name string. When the element is unmounted, the argument will be
null
. You can, of course, use a method instead of an inline function.
Ref on Component
This section assumes knowledge of Components . Feel free to skip it and come back later.
ref
can also be used on a child component. In this case the reference will be that of a component instance:
If the child component is using Options API or not using
<script setup>
, the
referenced instance will be identical to the child component's
this
, which means the parent component will have full access to every property and method of the child component. This makes it easy to create tightly coupled implementation details between the parent and the child, so component refs should be only used when absolutely needed - in most cases, you should try to implement parent / child interactions using the standard props and emit interfaces first.
An exception here is that components using
<script setup>
are
private by default
: a parent component referencing a child component using
<script setup>
won't be able to access anything unless the child component chooses to expose a public interface using the
defineExpose
macro:
When a parent gets an instance of this component via template refs, the retrieved instance will be of the shape
{ a: number, b: number }
(refs are automatically unwrapped just like on normal instances).
See also: Typing Component Template Refs