X-Git-Url: http://git.ithinksw.org/extjs.git/blobdiff_plain/c930e9176a5a85509c5b0230e2bff5c22a591432..10a866c12701c0a0afd0ac85dcdcf32a421514ac:/docs/source/TextField.html?ds=sidebyside
diff --git a/docs/source/TextField.html b/docs/source/TextField.html
index d32d2e97..c4cc7f8b 100644
--- a/docs/source/TextField.html
+++ b/docs/source/TextField.html
@@ -1,5 +1,6 @@
+
The source code
@@ -12,44 +13,10 @@
* or as the base class for more sophisticated input controls (like {@link Ext.form.TextArea}
* and {@link Ext.form.ComboBox}).
*
Validation
- *
Field validation is processed in a particular order. If validation fails at any particular
- * step the validation routine halts.
+ *
The validation procedure is described in the documentation for {@link #validateValue}.
+ *
Alter Validation Behavior
+ *
Validation behavior for each field can be configured:
*
- *
1. Field specific validator
- *
- *
If a field is configured with a {@link Ext.form.TextField#validator validator} function,
- * it will be passed the current field value. The {@link Ext.form.TextField#validator validator}
- * function is expected to return boolean true if the value is valid or return a string to
- * represent the invalid message if invalid.
- *
- *
2. Built in Validation
- *
- *
Basic validation is affected with the following configuration properties:
Using VTypes offers a convenient way to reuse validation. If a field is configured with a
- * {@link Ext.form.TextField#vtype vtype}, the corresponding {@link Ext.form.VTypes VTypes}
- * validation function will be used for validation. If invalid, either the field's
- * {@link Ext.form.TextField#vtypeText vtypeText} or the VTypes vtype Text property will be
- * used for the invalid message. Keystrokes on the field will be filtered according to the VTypes
- * vtype Mask property.
- *
- *
4. Field specific regex test
- *
- *
Each field may also specify a {@link Ext.form.TextField#regex regex} test.
- * The invalid message for this test is configured with
- * {@link Ext.form.TextField#regexText regexText}.
- *
- *
Alter Validation Behavior
- *
- *
Validation behavior for each field can be configured:
*
{@link Ext.form.TextField#invalidText invalidText} : the default validation message to
* show if any validation step above does not provide a message when invalid
*
{@link Ext.form.TextField#maskRe maskRe} : filter out keystrokes before any validation occurs
@@ -59,12 +26,11 @@
*
{@link Ext.form.Field#validateOnBlur validateOnBlur},
* {@link Ext.form.Field#validationDelay validationDelay}, and
* {@link Ext.form.Field#validationEvent validationEvent} : modify how/when validation is triggered
- *
- *
*
- * @constructor
- * Creates a new TextField
+ *
+ * @constructor Creates a new TextField
* @param {Object} config Configuration options
+ *
* @xtype textfield
*/
Ext.form.TextField = Ext.extend(Ext.form.Field, {
@@ -152,11 +118,22 @@ var myField = new Ext.form.NumberField({
*/
blankText : 'This field is required',
/**
- * @cfg {Function} validator A custom validation function to be called during field validation
+ * @cfg {Function} validator
+ *
A custom validation function to be called during field validation ({@link #validateValue})
* (defaults to null). If specified, this function will be called first, allowing the
- * developer to override the default validation process. This function will be passed the current
- * field value and expected to return boolean true if the value is valid or a string
- * error message if invalid.
+ * developer to override the default validation process.
+ *
This function will be passed the following Parameters:
Validates a value according to the field's validation rules and marks the field as invalid
+ * if the validation fails. Validation rules are processed in the following order:
+ *
+ *
+ *
1. Field specific validator
+ *
+ *
A validator offers a way to customize and reuse a validation specification.
+ * If a field is configured with a {@link #validator}
+ * function, it will be passed the current field value. The {@link #validator}
+ * function is expected to return either:
+ *
+ *
Boolean true if the value is valid (validation continues).
+ *
a String to represent the invalid message if invalid (validation halts).
+ *
+ *
+ *
+ *
2. Basic Validation
+ *
+ *
If the {@link #validator} has not halted validation,
+ * basic validation proceeds as follows:
+ * Depending on the configuration of {@link #allowBlank}, a
+ * blank field will cause validation to halt at this step and return
+ * Boolean true or false accordingly.
+ *
+ * If the passed value does not satisfy the {@link #maxLength}
+ * specified, validation halts.
+ *
+ *
+ *
+ *
+ *
+ *
3. Preconfigured Validation Types (VTypes)
+ *
+ *
If none of the prior validation steps halts validation, a field
+ * configured with a {@link #vtype} will utilize the
+ * corresponding {@link Ext.form.VTypes VTypes} validation function.
+ * If invalid, either the field's {@link #vtypeText} or
+ * the VTypes vtype Text property will be used for the invalid message.
+ * Keystrokes on the field will be filtered according to the VTypes
+ * vtype Mask property.
+ *
+ *
+ *
4. Field specific regex test
+ *
+ *
If none of the prior validation steps halts validation, a field's
+ * configured {@link #regex} test will be processed.
+ * The invalid message for this test is configured with
+ * {@link #regexText}.
+ *
+ *
* @param {Mixed} value The value to validate
* @return {Boolean} True if the value is valid, else false
*/
@@ -473,8 +521,8 @@ var myField = new Ext.form.NumberField({
var d = document.createElement('div');
d.appendChild(document.createTextNode(v));
v = d.innerHTML;
- d = null;
Ext.removeNode(d);
+ d = null;
v += ' ';
var w = Math.min(this.growMax, Math.max(this.metrics.getWidth(v) + /* add extra padding */ 10, this.growMin));
this.el.setWidth(w);