Hi everyone,
I am running into a persistent client-side UI issue while testing dynamic Select2 multi-select dropdowns and AJAX remote data loading in my web app. Whenever I keep a secondary browser tab open to run automated testing utilities and process background scripts here while simultaneously interacting with searchable select boxes and dynamic dropdown menus in my main window, the Select2 interface starts lagging severely and stops responding.
During continuous background JavaScript execution, clicking on the dropdown target fails to trigger the option menu, and the search input inside the active dropdown container completely loses focus.
I am also noticing a couple of related rendering and event listener glitches across desktop and mobile browsers. Switching back and forth between active browser tabs causes open Select2 dropdown overlays to detach from their target input element, which occasionally leaves floating option containers on the screen or forces a full browser tab reload to restore normal DOM event bindings. Furthermore, mobile WebKit browsers seem to experience touch responsiveness delays when closing active dropdown menus while secondary script execution tasks remain open in background tabs.
Has anyone else noticed Select2 dropdown UI freezes or input focus loss when running automated external testing tools alongside dynamic select controls, and are there specific browser hardware acceleration settings, memory flags, or event throttling patterns you would recommend tweaking to keep multi-tab workflows responsive?