-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
9.12.0, 10.3.0
-
9.12
-
1
-
Severity 3 - Minor
-
Issue Summary
When a user in Chrome tries to edit a multi-select custom field, ex: the Components field, when there are 10k+ options, there is a significant lag (30s+) in the results being displayed. This is with the multiselect.frother.renderer dark feature enabled. This behavior does not occur in Firefox, and the options for the field are rendered almost immediately. When tested in Safari, the options were rendered a couple seconds slower than in Firefox, but still significantly faster than in Chrome.
Chrome: Version 139.0.7258.128 (Official Build) (arm64)
Firefox: 141.0.3 (aarch64)
Safari: Version 18.5 (20621.2.5.11.8)
Steps to Reproduce
- Create 10k components for a project
- Create an issue in the new project
- Edit the component field and start typing to get an autofill suggestion list of components
Expected Results
The components (or other multi-select) custom field data should render in less than a couple of seconds ; like with the Firefox browser
Actual Results
The components (or other multi-select) custom field data renders in 30-50 seconds in Chrome.
Workaround
- Use a different browser; ex: Firefox or Safari
- Disable the multiselect.frother.renderer dark feature