Chrome 140 regression breaks $.fn.sortSelect (option sorting/selection); function temporarily disabled #4697
Description
Describe the bug
On Chrome v140, the in-app utility $.fn.sortSelect (used to alphabetically sort options while preserving the selected option and optionally pinning a value at the top) behaves incorrectly. Symptoms include:
Options not being sorted as expected.
The selected option being lost/changed after sorting.
Options appearing duplicated or missing after a sort.
As a mitigation, the function is currently disabled in the code.
Reference:
src/js/utils/common.js lines 67–68: “Chrome v140 does not work with sortSelect function properly. Disabling it for now until a fix is found.”
To Reproduce
App repro (Chrome 140):
Run yarn dev and open http://localhost:8000/ in Chrome v140.
Navigate to any tab using sorted dropdowns (e.g., Receiver, OSD, Failsafe, Ports).
Interact with a dropdown expected to be alphabetically sorted.
Observe incorrect sort order and/or that the selected option changes unexpectedly.
Minimal code repro (Chrome 140):
Create a with multiple s and one selected.
sortSelect (collect options → sort by text using localeCompare → clear → re-add using select.add(option)).Expected behavior
- Options are alphabetically sorted (locale-aware).
- The previously selected option remains selected.
- No options are lost or duplicated.
- Any “pin-to-top” option remains at the top.
Configurator version
2025.12.0-beta
Flight controller configuration
Add any other context about the problem that you think might be relevant here
Google Chrome 140.x