Side navigation
#15205 closed feature (migrated)
Opened August 08, 2014 12:43PM UTC
Closed October 21, 2014 12:55AM UTC
No way to globally clean up data
| Reported by: | m_gol | Owned by: | |
|---|---|---|---|
| Priority: | low | Milestone: | 2.next |
| Component: | data | Version: | 2.1.1 |
| Keywords: | Cc: | dmethvin, rwaldron | |
| Blocked by: | Blocking: |
Description
When an element data is leaked (for example because it was detached/off-DOM and we lost reference to it) there is no way to get rid of its data. This matters in tests run in watch mode as leaks can accumulate & crash the browser.
The only alternative now seems to be initializing jQuery from scratch when we desire a clean environment. This is a little difficult now due to the fact that jQuery doesn't expose any initializing function so the lib would have be loaded once again (which, again, is not so easy/natural in many test frameworks).
Angular 1.3 betas were recently switched to use jQuery 2.1 instead of 1.x and this problem has arisen; see:
Attachments (0)
Change History (4)
Changed August 08, 2014 12:51PM UTC by comment:1
Changed August 08, 2014 02:14PM UTC by comment:2
| status: | new → open |
|---|
Changed August 11, 2014 04:45PM UTC by comment:3
| milestone: | None → 2.next |
|---|
Let's see how 2.2 data approach fares.
Changed October 21, 2014 12:55AM UTC by comment:4
| resolution: | → migrated |
|---|---|
| status: | open → closed |
Migrated to https://github.com/jquery/jquery/issues/1787
*If* we end up attaching data directly to nodes the problem may mostly go away. Mostly since we still may have leftover data from special events etc.