Bug Tracker

Opened 12 years ago

Closed 9 years ago

Last modified 9 years ago

#2316 closed enhancement (wontfix)

removeData for complete namespaces

Reported by: klaus Owned by:
Priority: low Milestone: 1.5
Component: data Version: 1.5
Keywords: data Cc:
Blocked by: Blocking:

Description

The removeData methods should work on complete namespaces - similiar to unbind - so instead of

$(el).removeData('foo.ns').removeData('bar.ns');

you can write:

$(el).removeData('.ns'); 

Change History (7)

comment:1 Changed 9 years ago by dmethvin

Component: coredata

comment:2 Changed 9 years ago by boushley

This seems like a reasonable enhancement, and would make the api more consistent to allow for namespacing data within .data()

comment:3 Changed 9 years ago by snover

Keywords: needsreview added
Milestone: 1.2.4
Priority: minorlow
Version: 1.2.31.4.4rc

The .data method doesn’t do namespacing like that. Namespacing for .data would look more like:

$('#foo').data('bar', {});
$('#foo').data('bar').baz = 2;
$('#foo').removeData('bar');

I am pretty sure this will be wontfix but gonna discuss it with some folks.

comment:4 Changed 9 years ago by Rick Waldron

Milestone: 1.4.5

comment:5 Changed 9 years ago by dmethvin

Keywords: needsreview removed
Resolution: wontfix
Status: newclosed

The period is not currently a special character in .data() names. Implementing this could cause regressions for anyone who used names that contained a period.

It's simple for a user to implement their own namespace by assigning a Javascript object to a simply-named .data() item.

comment:6 Changed 9 years ago by john

Version: 1.4.4rc1.5

There wasn't a 1.4.5 release, was actually 1.5.

comment:7 Changed 9 years ago by john

Milestone: 1.4.51.5

There was no 1.4.5 release, was actually 1.5.

Note: See TracTickets for help on using tickets.