Opened 11 years ago

Closed 10 years ago

Last modified 9 years ago

#10902 closed defect (fixed)

[patch] [cla] Checkbox's setValueAttr doesn't respect priorityChange

Reported by: Dustin Machi Owned by:
Priority: high Milestone: 1.5
Component: Dijit - Form Version: 1.4.2
Keywords: Cc: [email protected]…, Douglas Hays
Blocked By: Blocking:


Most of the form widgets now support a third parameter to .attr('value', val, priorty) which allows you to prevent triggering onChange() essentially. This exists for doing attr("checked"), which is what attr('value') ultimately calls. Here is a small patch to allow the priority change attribute from _setValueAttr to be passed through to setCheckedAttr.

Change History (5)

comment:1 Changed 11 years ago by Adam Peller

Cc: [email protected] added
Component: GeneralDijit
Owner: anonymous deleted

comment:2 Changed 11 years ago by bill

Cc: Douglas Hays added
Summary: Checkbox's setValueAttr doesn't respect priorityChange[patch] [cla] Checkbox's setValueAttr doesn't respect priorityChange

Looks good to me, Doug do you see any problems?

comment:3 Changed 11 years ago by Douglas Hays

That'll work

comment:4 Changed 10 years ago by bill

Resolution: fixed
Status: newclosed

(In [21874]) Apply Dustin's fix so priorityChange works when set("value", ...) is used to adjust the checked/unchecked state. Fixes #10902 !strict.

comment:5 Changed 9 years ago by bill

Component: DijitDijit - Form
Note: See TracTickets for help on using tickets.