Collapse toggle via JavaScript in Bootsrap - Performance & Optimization

Performance: Collapse toggle via JavaScript

MEDIUM IMPACT

This affects interaction responsiveness and visual stability when toggling collapsible content on the page.

Toggling a collapsible section on user click

Bootsrap

const collapseInstance = new bootstrap.Collapse(document.getElementById('collapseExample'), { toggle: false });
// On toggle button click:
collapseInstance.toggle();

Uses Bootstrap's optimized collapse methods that handle CSS transitions and minimize layout recalculations.

📈 Performance GainSingle reflow with GPU-accelerated transitions, smoother interaction

Toggling a collapsible section on user click

Bootsrap

const content = document.getElementById('collapseExample');
content.style.display = content.style.display === 'none' ? 'block' : 'none';

Directly changing style.display causes layout thrashing and forces reflow on every toggle.

📉 Performance CostTriggers 2 reflows per toggle, causing input delay and jank

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Direct style.display toggle	Minimal DOM nodes affected	2 reflows per toggle	High paint cost due to forced layout	[X] Bad
Bootstrap Collapse toggle method	Minimal DOM nodes affected	1 reflow per toggle	Lower paint cost with GPU compositing	[OK] Good

Rendering Pipeline

Toggling collapse changes element visibility and height, affecting Style Calculation and Layout stages, then triggering Paint and Composite for smooth animation.

→Style Calculation

→Layout

→Paint

→Composite

⚠️ BottleneckLayout stage is most expensive due to height recalculation and reflow.

Core Web Vital Affected

INP

This affects interaction responsiveness and visual stability when toggling collapsible content on the page.

Optimization Tips

1Avoid direct style.display changes for toggling collapse to prevent forced reflows.

2Use CSS transitions and class toggling to enable GPU-accelerated animations.

3Leverage Bootstrap's Collapse API to handle toggling efficiently and reduce layout thrashing.

Performance Quiz - 3 Questions

What is the main performance problem with toggling collapse by directly changing style.display?

A It increases bundle size significantly

B It triggers multiple reflows causing input delay

C It blocks network requests

D It causes memory leaks

DevTools: Performance

How to check: Record a performance profile while toggling the collapse. Look for Layout and Recalculate Style events in the flame chart.

What to look for: High number or long duration of Layout events indicates inefficient toggling causing jank.

Practice

1. What does the toggle() method do when used with new bootstrap.Collapse(element) in Bootstrap?

easy

A. It reloads the entire page.

B. It shows the hidden content if collapsed, or hides it if shown.

C. It permanently disables the collapse functionality.

D. It changes the color of the collapsed content.

Solution

1. Step 1: Understand the collapse object

   The new bootstrap.Collapse(element) creates a controller for the collapsible content.

2. Step 2: Role of toggle() method

   The toggle() method switches the content between visible and hidden states smoothly.

3. Final Answer:

   It shows the hidden content if collapsed, or hides it if shown. -> Option B

4. Quick Check:

   toggle() switches collapse state [OK]

Hint: toggle() flips collapse open or closed [OK]

Common Mistakes:

• Thinking toggle disables collapse
• Confusing toggle with page reload
• Assuming toggle changes styles only

2. Which of the following is the correct way to create a Bootstrap collapse instance for an element with id myCollapse in JavaScript?

easy

A. const collapse = new bootstrap.Collapse('myCollapse');

B. const collapse = bootstrap.Collapse('#myCollapse');

C. const collapse = new bootstrap.Collapse(document.getElementById('myCollapse'));

D. const collapse = new Collapse('myCollapse');

Solution

1. Step 1: Identify the element reference

   The Bootstrap Collapse constructor requires a DOM element, not a selector string.

2. Step 2: Correct syntax for element selection

   Using document.getElementById('myCollapse') returns the element to pass to the constructor.

3. Final Answer:

   const collapse = new bootstrap.Collapse(document.getElementById('myCollapse')); -> Option C

4. Quick Check:

   Pass DOM element, not selector string [OK]

Hint: Use getElementById to pass element, not string [OK]

Common Mistakes:

• Passing selector string instead of element
• Omitting 'new' keyword
• Using undefined Collapse without bootstrap prefix

3. Given the following code, what will be the visible state of the collapsible content after the button is clicked once?

const collapse = new bootstrap.Collapse(document.getElementById('content'), { toggle: false });
document.getElementById('toggleBtn').addEventListener('click', () => {
  collapse.toggle();
});

The content is initially hidden.

medium

A. The content will become visible.

B. The content will remain hidden.

C. The content will be removed from the DOM.

D. An error will occur because toggle is false.

Solution

1. Step 1: Understand initial state and options

   The content starts hidden and toggle: false means it won't auto-toggle on creation.

2. Step 2: Effect of calling toggle() on click

   Calling toggle() manually switches the state, so hidden content becomes visible.

3. Final Answer:

   The content will become visible. -> Option A

4. Quick Check:

   Manual toggle() shows hidden content [OK]

Hint: toggle() always flips visibility regardless of options [OK]

Common Mistakes:

• Thinking toggle:false disables toggle() method
• Assuming content stays hidden without auto toggle
• Confusing toggle() with remove()

4. Identify the error in this code snippet that tries to toggle a Bootstrap collapse:

const collapse = new bootstrap.Collapse('content');
document.getElementById('btn').addEventListener('click', () => {
  collapse.toggle();
});

medium

A. The selector 'content' should be a DOM element, not a string.

B. The toggle() method is not available on collapse instances.

C. The event listener is attached to the wrong element.

D. Missing parentheses when calling toggle.

Solution

1. Step 1: Check constructor argument

   The constructor expects a DOM element, but 'content' is a string selector, which is incorrect.

2. Step 2: Correct way to pass element

   Use document.getElementById('content') to get the element before passing it.

3. Final Answer:

   The selector 'content' should be a DOM element, not a string. -> Option A

4. Quick Check:

   Pass DOM element, not string selector [OK]

Hint: Always pass DOM element, not string selector [OK]

Common Mistakes:

• Passing string selector instead of element
• Assuming toggle() is unavailable
• Incorrect event listener target

5. You want to toggle a Bootstrap collapse and update the button text between 'Show' and 'Hide' accordingly. Which JavaScript code correctly achieves this?

const collapse = new bootstrap.Collapse(document.getElementById('panel'), { toggle: false });
const btn = document.getElementById('toggleBtn');
btn.addEventListener('click', () => {
  collapse.toggle();
  if (btn.textContent === 'Show') {
    btn.textContent = 'Hide';
  } else {
    btn.textContent = 'Show';
  }
});

hard

A. The collapse instance must be recreated inside the click event.

B. The button text update should happen before calling toggle().

C. You must use btn.innerHTML instead of textContent.

D. This code works correctly to toggle and update button text.

Solution

1. Step 1: Check toggle and button text update order

   The code calls collapse.toggle() then updates the button text based on current text, which is logical.

2. Step 2: Validate textContent usage and event setup

   Using textContent is correct for plain text updates, and the collapse instance is created once outside the event.

3. Final Answer:

   This code works correctly to toggle and update button text. -> Option D

4. Quick Check:

   Toggle then update textContent works [OK]

Hint: Toggle first, then update button text [OK]

Common Mistakes:

• Updating text before toggle causing mismatch
• Using innerHTML unnecessarily
• Recreating collapse instance on every click