jQuery Forum

That's what the .prop() function is for.

One of the many problems with getters/setters is that you can’t wildcard them. You would need to create one for checked, one for selected, and another for each of the other KNOWN properties. .prop() doesn’t care and does not need to be updated when new properties are created by browser developers and the Ecma folks.

This is where you can talk about the feature. We know that the core developers have rejected getter/setters before. But you are free to make any request of them at the link you were given.

OK, I tried searching for it before posting, but I must not have used the correct search terms. If it's been proposed and rejected before, no point in bringing it up again.

Because I, personally, love getters and setters. I’ve written a lot of generic code that uses them