DatePicker: instActive not released on instance destroy
|Reported by:||eshcharc||Owned by:|
In the days of client side frameworks and SPAs, considerations need to be made regarding client side page switch and optimizations and cleaning of assets.
When we examined and profiled our SPA on a page switch scenario, we've noticed that a jQuery-UI plugin is holding a whole element tree. A further examination led us to a date-picker component and the "global" "instActive".
It seems that when a datePicker instance is being destryed via _destroyDatePicker, "instActive" which is linked to this instance, is not taken care of and keep a reference to this instance and all of its tree elements. When a client side framework is involved, that makes it worse.
That can quite easily be treated.
Change History (6)
comment:2 Changed 2 years ago by tj.vantoll
- Component changed from ui.core to ui.datepicker
- Status changed from new to open
comment:3 Changed 2 years ago by Chen Eshchar
- Resolution set to fixed
- Status changed from open to closed