Project owner:Eugene Lazutkin


This class is the main component of the form manager, which provides the initialization and core functionality. It can be used on its own as a mixin to other widgets, or as a part of dojox.form.Manager. All other form manager mixins require this class to be mixed in as well.

On startup this mixin inspects its body and registers all found form widgets, and attached nodes (by data-dojo-attach-point). Additionally it provides some low-level properties and methods to handle controlled elements.

Methods and properties

This section describes all public methods and properties of the dojox.form.manager._Mixin class.


Only one property falls under this category: watch.


This is a Boolean property, which is used to control observers. When this property is true change events are processed and passed to relevant observers as usual. When it is false, change events are ignored.

This property is useful when you want to modify/update controlled elements, but you don’t want to cause observers to run.


// stop change event processing = false;
// update some fields without alerting observers
  lastName:  "Smith",
  firstName: "Jane"
// start change event processing = true;

Value access

Methods in this category provide primitives for low-level access to values of individual form elements. For high-level access to values use _ValueMixin.

Note: _NodeMixin implements a complimentary method: formNodeValue.


This method allows to get/set values of controlled form widgets. It can be used two ways: with one parameter to get the value, and with two parameters to set the value:

// reading the value
var value = fm.formWidgetValue("lastName");
// writing the value
fm.formWidgetValue("lastName", "Smith");

The first parameter is a name of a controlled form element (a string). The optional second parameter is a value to be set. It is usually a string too.

The returned value is:

  • A form element’s value for the getter version.
  • The form manager itself for the setter version providing easy chaining.


This method is similar to formWidgetValue method but works on nodes attached to the widget itself:

// reading the value
var value = fm.formPointValue("firstName");
// writing the value
fm.formPointValue("lastName", "Jane");

Usage and syntax is exactly the same as for formWidgetValue.


Methods in this category provide primitives to iterate over controlled elements. These methods are major building blocks for all other mixins. In most cases you should avoid using them directly relying on more high-level methods of other mixins. Do use them if you write your own mixins.

Note: _NodeMixin implements a complimentary method: inspectFormNodes.


This method iterates over controlled elements:

var inspector = function(name, widget, value){
  var oldValue = this.formWidgetValue(name);
  this.formWidgetValue(name, value);
  return oldValue;

var state = ["firstName", "lastName"];

var defaultValue = "X";

fm.inspectFormWidgets(inspector, state, defaultValue);

There are three ways to use this method:

  1. state is an array of form names. In this case inspector is called with the same 3rd parameter defaultValue for every widget in the array. The above example uses this form of inspection: both lastName and firstName will be set to "X".
  2. state is an object. In this case keys of the object are form names, while corresponding values are actual values to be passed to inspector as the 3rd parameter (in this case defaultValue is not used):
var state = {
  firstName: "Jill",
  lastName:  "Taylor"
fm.inspectFormWidgets(inspector, state);

The above example sets lastName to "Taylor" and firstName to "Jill".

  1. state is null or missing. In this case the method will iterate over all controlled widgets passing defaultValue as the value parameter to inspector.
fm.inspectFormWidgets(inspector, null, "X");

The above example sets all controlled widgets to "X".

While iterating the method collects all returned values of inspector in an object keyed by corresponding widget names, and returns it as the result.

var state = {
  firstName: "Jill",
  lastName:  "Taylor"
var result = fm.inspectFormWidgets(inspector, state);

console.log(result.firstName);                // Jane
console.log(result.lastName);                 // Smith

console.log(fm.formWidgetValue("firstName")); // Jill
console.log(fm.formWidgetValue("lastName"));  // Taylor

inspector function is called for every inspected widget in the context of the form manager. It has following signature:

var inspector = function(name, widget, value){
  // ...
  return someValue;

name is the name of the inspected widget, widget is the widget itself, or an array of widgets for radio button widgets, value is the value passed to the function according to the above described rules. inspector‘s return value will be collected and returned as a part of the result object as described above.

What inspector does is up to you. It can modify or just read widget values. It can return something meaningful or nothing at all. It is strongly suggested to use other form manager’s methods to get/set widget values rather than doing it manually.


This method is similar to inspectFormWidgets method but works on nodes attached to the widget itself. The only difference is the inspector signature, which uses a DOM node instead of a widget:

var inspector = function(name, node, value){
  // ...
  return someValue;

Everything else is the same. Example:

var inspector = function(name){
  return this.formPointValue(name);

// collect all current values of attached nodes
var result = fm.inspectAttachedPoints(inspector);


This is the high-level method, which has the same signature as inspectFormWidgets and inspectAttachedPoints. The major difference is: it iterates over widgets and attached nodes and form nodes (for the last one you have to include _NodeMixin):

var inspector = function(name){
  return this.formPointValue(name);

// collect all current values of attached nodes
var result = fm.inspect(inspector);

inspector‘s signature is similar to inspectFormWidgets‘s inspector, but the 2nd argument will be a form widget for widgets, a DOM node for attached nodes and form nodes, or an array of widgets or DOM nodes for radio buttons.


These functions can register/unregister widgets. In most cases these methods are not used directly because dojox.form.manager._Mixin registers all children form widgets automatically. But if you create/delete widgets dynamically, you should register/unregister them manually.

Note: _NodeMixin implements complimentary methods: registerNode, unregisterNode, registerNodeDescendants, unregisterNodeDescendants.


This method registers a form widget with a form manager, and connects its observers. This widget is not required to be a descendant of the form manager it is being registered with. Three signatures are recognized:

  1. Register by widget id:
  1. Register by widget’s DOM node:
  1. Register a widget object:


This method disconnects widget’s observers, and removes it from internal structures of a form manager. The only way to unregister a widget is by its form name:



This method calls registerWidget for every descendant form widget of a given widget (usually a layout widget). This method is useful when you add several widgets dynamically. These widgets do not need to be descendants of the form manager they are being registered with. For example you can register a dialog widget, which is attached directly to the body element.

Like with registerWidget widget three signatures are recognized:

  1. Register by widget id:
  1. Register by widget’s DOM node:
  1. Register by specifying a widget object:


This method calls unregisterWidget for every descendant form widget of a given widget (usually a layout widget). Its signature is the same as registerWidgetDescendants‘s signature (all three variants).


Lifecycle methods are part of every widget. They are used to initialize and destroy a widget. If you mix dojox.form.manager._Mixin in your own widget, make sure that these methods are not overwritten. If you overwrite them, make sure to call this.inherited(arguments) at the appropriate place, so they can initialize/destroy the widget properly.


This is the standard method of any widget. It is responsible for starting up the widget after it was created and the DOM was parsed. For more details, see dijit._Widget.


This is the standard method of any widget. It is responsible for tearing up internal widget structures preparing the widget for the garbage collection. Usually it detaches event handlers, and kills references to DOM nodes. For more details, see dijit._Widget.

Additional functions

For writers of additional mixins, this module provides several helper functions.


As described above the inspector can receive a widget/node as the 2nd parameter, or an array of widgets/nodes. This adapter checks the 2nd value and applies the inspector directly, if it was called with a widget/node. If it was called with the array, the adapter will apply the inspector to all elements of the array.

var inspector = function(name, elem, value){
  // ...
var adapted = dojox.form.manager.actionAdapter(inspector);

This adapter is useful when you want to do a uniform processing of form elements, e.g., disabling them, or adding a CSS class.


This is a slightly different adapter for arrays versus widgets/nodes. The difference with dojox.form.manager.actionAdapter is in case of arrays it applies the inspector only to the first element of the array.

var inspector = function(name){
  // ...
var adapted = dojox.form.manager.inspectorAdapter(inspector);

This adapter is useful when you want to do a uniform inspection of form elements, e.g., reading and returning their values.


This function takes an object and returns an array of all keys. It is very similar to dojox.lang.functional.object.keys(). It is defined there only to reduce the dependency on other packages.

Technical notes

_Mixin extends dijit._Widget with an extra attribute: observer. It makes this attribute valid for all widgets. You can read more on observers in the dojox.form.manager event processing documentation.

Error in the documentation? Can’t find what you are looking for? Let us know!