Thanks for taking the time to contribute to the jQuery project! Please provide a jsFiddle that outlines practical use cases for your enhancement request.

Example: http://jsfiddle.net/QtacS/

Thanks, I've forked the fiddle and have a few brainstorming questions that I've noted in the code as comments.

http://jsfiddle.net/rwaldron/tAnMH/1/

Per discussion: This feature provides a convenience method for disabling/enabling form elements that support the disabled property, as well as any plugins that support listening for triggered "disabled" or "enabled" events.

http://jsfiddle.net/rwaldron/tAnMH/2/

(fixed a typo with trigger("enabled") )

Will there also be convenience functions for detecting/modifying checked and selected elements as part of this change?

I'd like to see this done a bit differently, with a single .disable(boolean) method. Otherwise the code will often look like $("#thing")[cond?"enable":"disable"]();

We should consider this for 1.7.

I think the problem of check()/select() is different - as both of those can (and probably should) be manipulated through .val().

#9189 is a duplicate of this ticket.

Select should be manipulated through val. Check can't be though. I'm not sure how I feel about all this. It's a little too easy to do this with raw javascript, but this might be something more in dave's direction:

http://jsfiddle.net/timmywil/QtacS/3/

Nominating ticket for 1.7 discussion.

+1,

-1, again, let's make an official plugin with all those helpers and let's not clobber core anymore than it needs to.

+0, disable could be convenient. I've gravitated towards against doing .check at all though.

-1, Don't think this is really needed much anymore, given that we have .attr("checked", true) working.

-1, I don't think we need help methods for every little thing, these are already straight-forward with existing APIs

-1, I've been really unclear of the utility of these to begin with

-1

We recommend using attr()