Link: http://docs.dojocampus.org/releasenotes/1.4#attr-value-val-false

During an upgrade from dojo 1.1.1 to 1.6.1, I found that dijit.byId('someWidget').set('value','someNewValue'), was causing the onChange event to fire for the input.

To prevent onChange from firing when the .set method is used, a third parameter priorityChange is used. Setting priorityChange to false prevents the onChange event from firing.

The updated code is: dijit.byId('someWidget').set('value','someNewValue',false)

A sed command to update the code. In this case the setValue or attr(’value’) calls had already been translated to set:

Code: