jQuery Forum

I just think it's the expected behavior to trigger the change event when it has changed, no matter how.

The fact that it doesn't isn't even really documented. Apart from the following in the change() docs: 

 For select boxes, checkboxes, and radio buttons, the event is fired immediately when the user makes a selection with the mouse

But I don't think anyone will pick up on that. Especially considering that it completely omits change by keyboard.

In my case a third party script changes the checkbox state which is why I can't trigger the event manually.

http://jsfiddle.net/HC85Q/ 

Changes triggered by user input cause events to happen and changes made programatically do not.

Does jQuery really need to document native functionality?

Why should jQuery do something extra that doesn't natively happen? This removes control from the developer. If jQuery automatically triggered these events, the developer would have no way of disabling it.

As it stands now, the developer can trigger the event programmatically to get the functionality you are looking for.

$("someel").val("foobar").triggerHandler("change");

-- Kevin

Just because it's how native js handles it not mean it's correct.

I haven't heard one valid reason as to why there should not be an event (maybe even 'changedProgramatically' event) triggered.

If for example it wasn't possible in all browser that might be a reason. Since jQuery strives to create a solution that works in all browsers.

It is far more flexible for jQuery to NOT automatically trigger the event. If you need the event triggered, you always have the option to trigger it, and if you don't want it triggered, it won't be. How do we trigger an event when someone changes the value with this.value = "foobar"? you cant because that's native javascript and jquery has no way of intercepting that. Should it really be handled two completely different ways based on how you change the value?

-- Kevin