Skip to main content

Search and Top Navigation

#15245 new bug ()

Opened October 13, 2017 09:32AM UTC

Last modified October 13, 2017 09:35AM UTC

[Selectable] Number of bindings grow over time when programatically adding / removing selectable elements.

Reported by: Erowlin Owned by:
Priority: minor Milestone: none
Component: ui.selectable Version: 1.12.1
Keywords: Cc:
Blocked by: Blocking:
Description

There is a performance issue on selectable.js when programmatically adding/removing elements that can be selected. The number of bindings selectable is working on is growing over time.

Example:

https://jsfiddle.net/hzygug67/5/

Obviously with that small number of elements, it does not cause any issues, but when working with 300+ elements, it starts to be a problem when selecting / unselecting elements.

Only workaround I've found for now is to destroy and re-create the selectable widget.

Attachments (0)
Change History (1)

Changed October 13, 2017 09:35AM UTC by Erowlin comment:1

description: There is a performance issue on selectable.js when programmatically adding/removing elements that can be selected. The number of bindings selectable is working on is growing over time. \ \ Example: \ https://jsfiddle.net/hzygug67/3/ \ \ Obviously with that small number of elements, it does not cause any issues, but when working with 300+ elements, it starts to be a problem when selecting / unselecting elements. \ \ Only workaround I've found for now is to destroy and re-create the selectable widget. There is a performance issue on selectable.js when programmatically adding/removing elements that can be selected. The number of bindings selectable is working on is growing over time. \ \ Example: \ https://jsfiddle.net/hzygug67/5/ \ \ Obviously with that small number of elements, it does not cause any issues, but when working with 300+ elements, it starts to be a problem when selecting / unselecting elements. \ \ Only workaround I've found for now is to destroy and re-create the selectable widget.