Fix front-end performance and scalability of search functionality in navigator

Created on 30 June 2025, 27 days ago

Overview

The functionality that Allow searching for content in the editor navigation Active introduced works, but its debounce functionality doesn't work:

  1. it sends a request from the first searched character
  2. it sends every subsequent character, even if typing very fast
  3. this causes needlessly many requests, thus negatively impacting front-end performance
  4. … which the server must respond to, thus negatively impacting scalability

Proposed resolution

Properly debounce, and only start talking to the server when there's >=3 characters typed.

User interface changes

None.

🐛 Bug report
Status

Active

Version

0.0

Component

Page builder

Created by

🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024