aboutsummaryrefslogtreecommitdiffstats
path: root/src/data.js
diff options
context:
space:
mode:
authorDave Methvin <dave.methvin@gmail.com>2011-10-26 17:04:15 -0400
committerDave Methvin <dave.methvin@gmail.com>2011-10-26 17:04:15 -0400
commit24e416dca36df4b182a612dba37f8b6cdaa25916 (patch)
tree2e0fc21c0af4c9b57d42ea567fc22bf4b7b591b4 /src/data.js
parent35bc30cd87c0578359c3127033dd85e1af132f69 (diff)
downloadjquery-24e416dca36df4b182a612dba37f8b6cdaa25916.tar.gz
jquery-24e416dca36df4b182a612dba37f8b6cdaa25916.zip
Fix #10588. For now, event voyeurism only merits the look of disapproval.
If you are using `.data("events")` we would like to know how we can provide a documented interface that satisfies the need.
Diffstat (limited to 'src/data.js')
-rw-r--r--src/data.js5
1 files changed, 2 insertions, 3 deletions
diff --git a/src/data.js b/src/data.js
index 02f96a849..24011c6b7 100644
--- a/src/data.js
+++ b/src/data.js
@@ -101,9 +101,8 @@ jQuery.extend({
thisCache[ jQuery.camelCase( name ) ] = data;
}
- // TODO: This is a hack for 1.5 ONLY. It will be removed in 1.6. Users should
- // not attempt to inspect the internal events object using jQuery.data, as this
- // internal data object is undocumented and subject to change.
+ // Users should not attempt to inspect the internal events object using jQuery.data,
+ // it is undocumented and subject to change. But does anyone listen? No.
if ( name === "events" && !thisCache[name] ) {
return thisCache[ internalKey ] && thisCache[ internalKey ].events;
}