unfiled → core
1.next → 1.5
undecided → blocker
new → open
.data really doesn’t make much sense in the context of a non-jQuery object at this point since it just ends up pointing the data cache to the object itself. I don’t feel like this is necessarily the right thing to do (it seems to me that it’s proper to let JS objects have metadata too instead of just hooking directly onto the object in a way that is likely to collide), but it is what happens currently, and I’m not sure I have the gumption to deal with it.
.attr will break completely on JS objects in 1.5 without a compatibility sim because it is being changed to always only set attributes via the DOM attribute manipulation methods, not properties or attributes. I have no idea what
.val does currently.
.bind/.trigger are used for custom event dispatching, even though JS objects can’t bubble, so most of the event system just ends up being overhead.
.delegate/.live makes no sense.
.animate works on JS objects as well as DOM elements, and just cycles properties.
.queue and friends needs to work.
.serialize documentation should probably have a link to
jQuery.param, since that is the appropriate way to serialize objects, but otherwise should not function on JS objects.
Since we currently perform pub/sub, etc. using
$(jsObj), it seems like that paradigm will need to stick around for a long time, even though it doesn’t make a lot of sense.