Template refs for DOM access in Vue - Performance & Optimization

Performance: Template refs for DOM access

MEDIUM IMPACT

Accessing DOM elements via template refs affects interaction responsiveness and can impact layout recalculations if used inefficiently.

Accessing and manipulating a DOM element in Vue

Vue

<template>
  <button @click="updateStyle">Click me</button>
  <div ref="box">Box</div>
</template>

<script setup>
import { ref } from 'vue'
const box = ref(null)
function updateStyle() {
  let newWidth = 100
  // Calculate final width once
  newWidth += 100
  box.value.style.width = `${newWidth}px`
}
</script>

Updates the DOM style only once, minimizing layout recalculations and improving responsiveness.

📈 Performance GainSingle reflow and repaint instead of 100, improving interaction speed.

Accessing and manipulating a DOM element in Vue

Vue

<template>
  <button @click="updateStyle">Click me</button>
  <div ref="box">Box</div>
</template>

<script setup>
import { ref } from 'vue'
const box = ref(null)
function updateStyle() {
  for (let i = 0; i < 100; i++) {
    box.value.style.width = `${100 + i}px`
  }
}
</script>

This code updates the DOM style 100 times in a loop, causing multiple layout recalculations and reflows.

📉 Performance CostTriggers 100 reflows and repaints, blocking interaction responsiveness.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Multiple style updates in loop via ref	Many writes	100 reflows	High paint cost	[X] Bad
Single style update via ref	One write	1 reflow	Low paint cost	[OK] Good

Rendering Pipeline

Template refs provide direct access to DOM nodes after Vue renders. Reading or writing styles via refs triggers style recalculation, layout, and paint stages.

→Style Calculation

→Layout

→Paint

⚠️ BottleneckLayout stage is most expensive when DOM styles are changed repeatedly.

Core Web Vital Affected

INP

Accessing DOM elements via template refs affects interaction responsiveness and can impact layout recalculations if used inefficiently.

Optimization Tips

1Avoid multiple DOM writes in loops when using template refs.

2Batch style updates to trigger fewer layout recalculations.

3Use template refs only when necessary to minimize DOM access cost.

Performance Quiz - 3 Questions

What is the main performance risk when using template refs to update DOM styles inside a loop?

A Triggering many layout recalculations and reflows

B Increasing JavaScript bundle size

C Causing network delays

D Blocking CSS parsing

DevTools: Performance

How to check: Record a performance profile while interacting with the component. Look for multiple Layout and Recalculate Style events triggered by the ref usage.

What to look for: Excessive layout recalculations and long scripting times indicate inefficient DOM access via refs.

Practice

1. What is the main purpose of using template refs in Vue?

easy

A. To directly access DOM elements or child components from the template

B. To define reactive state variables

C. To create computed properties

D. To register global components

Solution

1. Step 1: Understand what template refs do

   Template refs provide a way to directly access DOM elements or child components inside Vue templates.

2. Step 2: Compare with other Vue features

   Reactive state variables and computed properties are for data management, not direct DOM access. Global components registration is unrelated.

3. Final Answer:

   To directly access DOM elements or child components from the template -> Option A

4. Quick Check:

   Template refs = direct DOM/component access [OK]

Hint: Template refs connect template elements to script variables [OK]

Common Mistakes:

• Confusing refs with reactive state
• Thinking refs create computed properties
• Assuming refs register components

2. Which of the following is the correct way to declare a template ref in Vue 3's <script setup> syntax?

easy

A. const myRef = ref(null);

B. let myRef = reactive(null);

C. const myRef = computed(() => null);

D. var myRef = ref('element');

Solution

1. Step 1: Recall how to declare refs in Vue 3 script setup

   Use const myRef = ref(null); to create a ref variable initialized to null.

2. Step 2: Check other options for correctness

   reactive is for objects, not refs. computed is for derived values. Using var is discouraged and 'element' is not a valid initial value for a ref to DOM.

3. Final Answer:

   const myRef = ref(null); -> Option A

4. Quick Check:

   Declare ref with ref(null) [OK]

Hint: Use ref(null) to declare template refs in script setup [OK]

Common Mistakes:

• Using reactive instead of ref for DOM refs
• Initializing ref with wrong value
• Using var instead of const

3. Given the following Vue 3 component code, what will be logged when the button is clicked?

<template>
  <input ref="inputRef" />
  <button @click="focusInput">Focus</button>
</template>

<script setup>
import { ref } from 'vue';
const inputRef = ref(null);
function focusInput() {
  console.log(inputRef.value.tagName);
  inputRef.value.focus();
}
</script>

medium

A. undefined will be logged and an error occurs

B. "inputRef" will be logged and the input will get focus

C. "INPUT" will be logged and the input will get focus

D. Nothing will be logged and no focus happens

Solution

1. Step 1: Understand what inputRef.value refers to

   inputRef is a ref to the input DOM element, so inputRef.value is the actual input element.

2. Step 2: Check what tagName returns and focus behavior

   inputRef.value.tagName returns the uppercase tag name "INPUT". Calling focus() sets keyboard focus on the input.

3. Final Answer:

   "INPUT" will be logged and the input will get focus -> Option C

4. Quick Check:

   inputRef.value.tagName = "INPUT" and focus works [OK]

Hint: Ref value holds the DOM element; tagName is uppercase [OK]

Common Mistakes:

• Logging the ref variable name instead of its value
• Forgetting to use .value to access the element
• Assuming tagName is lowercase

4. Identify the error in this Vue 3 code snippet using template refs:

<template>
  <div ref="box">Content</div>
</template>

<script setup>
import { ref } from 'vue';
const box = ref();
console.log(box.value.textContent);
</script>

medium

A. The ref variable 'box' is not initialized with null

B. Accessing box.value.textContent before DOM is mounted causes error

C. The ref attribute should be used as :ref instead of ref

D. Missing import of onMounted to access DOM safely

Solution

1. Step 1: Check ref initialization and usage timing

   box is declared as ref() without initial value, which defaults to undefined. Accessing box.value.textContent immediately runs before DOM is ready.

2. Step 2: Understand Vue lifecycle for DOM refs

   Template refs are assigned after the component mounts. Accessing them too early (during setup) causes box.value to be null or undefined, so textContent access fails.

3. Final Answer:

   Accessing box.value.textContent before DOM is mounted causes error -> Option B

4. Quick Check:

   Access DOM refs only after mount [OK]

Hint: Access refs after mount, not immediately in setup [OK]

Common Mistakes:

• Trying to read ref value before DOM exists
• Not initializing ref with null (less critical)
• Confusing ref attribute syntax

5. You want to create a Vue 3 component that automatically focuses an input element when the component is mounted using template refs. Which code snippet correctly implements this behavior?

hard

A. <template>
<input :ref="inputRef" />
</template>

<script setup>
import { ref, onMounted } from 'vue';
const inputRef = ref(null);
onMounted(() => {
inputRef.focus();
});
</script>

B. <template>
<input ref="inputRef" />
</template>

<script setup>
import { ref } from 'vue';
const inputRef = ref(null);
inputRef.value.focus();
</script>

C. <template>
<input ref="inputRef" />
</template>

<script setup>
import { ref, onMounted } from 'vue';
const inputRef = ref(null);
onMounted(() => {
inputRef.value.focus();
});
inputRef.value.focus();
</script>

D. <template>
<input ref="inputRef" />
</template>

<script setup>
import { ref, onMounted } from 'vue';
const inputRef = ref(null);
onMounted(() => {
inputRef.value.focus();
});
</script>

Solution

1. Step 1: Use onMounted to run code after DOM is ready

   To safely access the input element, focus must be called inside onMounted lifecycle hook.

2. Step 2: Access the DOM element via inputRef.value and call focus()

   inputRef is a ref initialized to null, and inputRef.value holds the DOM element after mount. Calling inputRef.value.focus() sets focus correctly.

3. Final Answer:

   Code snippet C correctly uses onMounted and inputRef.value.focus() -> Option D

4. Quick Check:

   Use onMounted + inputRef.value.focus() [OK]

Hint: Focus input inside onMounted using inputRef.value.focus() [OK]

Common Mistakes:

• Calling focus outside onMounted before DOM ready
• Using :ref instead of ref attribute
• Calling focus on ref instead of ref.value