removeData() when not using jquery
See original GitHub issueHello,
removeData()
expects keys when removing data. I don’t know them as I don’t know what velocity caches about my elements.
Shouldn’t all the cache be destroyed when keys is not given ?
This is typically for the case when one is not using jquery at all and wants to properly unload everything velocity related.
Issue Analytics
- State:
- Created 8 years ago
- Comments:12 (1 by maintainers)
Top Results From Across the Web
.removeData() | jQuery API Documentation
removeData() will only remove data from jQuery's internal .data() cache, and any corresponding data- attributes on the element will not be removed.
Read more >custom data attribute - removeData() jquery method not working
When using .removeData("name"), jQuery will attempt to locate a data- attribute on the element if no property by that name is in the...
Read more >jQuery Misc removeData() Method - W3Schools
The removeData() method removes data previously set with the data() method. Syntax. $(selector).removeData(name). Parameter, Description. name, Optional.
Read more >jQuery removeData() method - javatpoint
The removeData() method is used to remove the data set previously using the data() method. It is an inbuilt method in jQuery. The...
Read more >jQuery | removeData() with Examples - GeeksforGeeks
The removeData() is an inbuilt method in jQuery which is used to remove those data which are previously set with the data() method....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I suspect many, many people actually have GC issues because they just don’t know they have to call removeData themselves; it’s so counter intuitive.
Fixed in v1.3.0