Bug #8357
closed
cbselect rebind event not working correctly in repeats
Added by krileon almost 4 years ago.
Updated over 3 years ago.
Start date:
28 January 2021
Description
This is causing the destroy behavior on the select2 to fail, but only inside repeat usages and only on rebind behavior. Specifically to see issue use the below steps.
1. Edit/Create Userlist
2. Add 2 Columns to Userlist
3. Move Second Column to be above the First Column
This is caused by the internal cache in select2 calling destroy if a select2 instance already exists in the cache. So basically destroy is being called twice on the select2 instance because select2 doesn't correctly clean up after itself.
Either fix this in select2 itself or add a workaround in cbselect.
- Status changed from Assigned to Resolved
- % Done changed from 0 to 100
Fixed in MR !1625
Reverted select2 pointless change of native data API to internal cache. Native data API is significantly more reliable and not prone to memory leaks due to uncleared data.
- Status changed from Resolved to Closed
Also available in: Atom
PDF
Updated by 
Updated by