Hierarchy
Ext.BaseExt.form.LabelableRequires
Mixed into
Files
A mixin which allows a component to be configured and decorated with a label and/or error message as is\ncommon for form fields. This is used by e.g. Ext.form.field.Base and Ext.form.FieldContainer\nto let them be managed by the Field layout.
\n\nNOTE: This mixin is mainly for internal library use and most users should not need to use it directly. It\nis more likely you will want to use one of the component classes that import this mixin, such as\nExt.form.field.Base or Ext.form.FieldContainer.
\n\nUse of this mixin does not make a component a field in the logical sense, meaning it does not provide any\nlogic or state related to values or validation; that is handled by the related Ext.form.field.Field\nmixin. These two mixins may be used separately (for example Ext.form.FieldContainer is Labelable but not a\nField), or in combination (for example Ext.form.field.Base implements both and has logic for connecting the\ntwo.)
\n\nComponent classes which use this mixin should use the Field layout\nor a derivation thereof to properly size and position the label and message according to the component config.\nThey must also call the initLabelable method during component initialization to ensure the mixin gets\nset up correctly.
\nIf specified, then the component will be displayed with this value as its active error when first rendered. Use\nsetActiveError or unsetActiveError to change it after component creation.
\nThe template used to format the Array of error messages passed to setActiveErrors into a single HTML\nstring. if the msgTarget is title, it defaults to a list separated by new lines. Otherwise, it\nrenders each message as an item in an unordered list.
\nAn optional string or XTemplate configuration to insert in the field markup\nat the end of the input containing element. If an XTemplate is used, the component's render data\nserves as the context.
An optional string or XTemplate configuration to insert in the field markup\nafter the label text. If an XTemplate is used, the component's render data\nserves as the context.
An optional string or XTemplate configuration to insert in the field markup\nafter the label element. If an XTemplate is used, the component's render data\nserves as the context.
An optional string or XTemplate configuration to insert in the field markup\nafter the subTpl markup. If an XTemplate is used, the\ncomponent's render data serves as the context.
Whether to adjust the component's body area to make room for 'side' or 'under' error messages.
\nDefaults to: true
The CSS class to be applied to the body content element.
\nDefaults to: Ext.baseCSSPrefix + 'form-item-body'
An optional string or XTemplate configuration to insert in the field markup\nat the beginning of the input containing element. If an XTemplate is used, the component's render data\nserves as the context.
An optional string or XTemplate configuration to insert in the field markup\nbefore the label text. If an XTemplate is used, the component's render data\nserves as the context.
An optional string or XTemplate configuration to insert in the field markup\nbefore the label element. If an XTemplate is used, the component's render data\nserves as the context.
An optional string or XTemplate configuration to insert in the field markup\nbefore the subTpl markup. If an XTemplate is used, the\ncomponent's render data serves as the context.
The CSS class to be applied to the special clearing div rendered directly after the field contents wrapper to\nprovide field clearing.
\nDefaults to: Ext.baseCSSPrefix + 'clear'
The CSS class to be applied to the error message element.
\nDefaults to: Ext.baseCSSPrefix + 'form-error-msg'
An extra CSS class to be applied to the body content element in addition to baseBodyCls.
\nDefaults to: ''
The label for the field. It gets appended with the labelSeparator, and its position and sizing is\ndetermined by the labelAlign, labelWidth, and labelPad configs.
\nA CSS class to be applied to the outermost element to denote that it is participating in the form field layout.
\nDefaults to: Ext.baseCSSPrefix + 'form-item'
When set to true, the label element (fieldLabel and labelSeparator) will be automatically\nhidden if the fieldLabel is empty. Setting this to false will cause the empty label element to be\nrendered and space to be reserved for it; this is useful if you want a field without a label to line up with\nother labeled fields in the same form.
\n\nIf you wish to unconditionall hide the label even if a non-empty fieldLabel is configured, then set the\nhideLabel config to true.
\nDefaults to: true
Set to true to completely hide the label element (fieldLabel and labelSeparator). Also see\nhideEmptyLabel, which controls whether space will be reserved for an empty fieldLabel.
\nDefaults to: false
The CSS class to use when marking the component invalid.
\nDefaults to: Ext.baseCSSPrefix + 'form-invalid'
Controls the position and alignment of the fieldLabel. Valid values are:
\n\nDefaults to: 'left'
An optional string or XTemplate configuration to insert in the field markup\ninside the label element (as attributes). If an XTemplate is used, the component's\nrender data serves as the context.
The CSS class to be applied to the label element. This (single) CSS class is used to formulate the renderSelector\nand drives the field layout where it is concatenated with a hyphen ('-') and labelAlign. To add\nadditional classes, use labelClsExtra.
\nDefaults to: Ext.baseCSSPrefix + 'form-item-label'
An optional string of one or more additional CSS classes to add to the label element. Defaults to empty.
\nThe amount of space in pixels between the fieldLabel and the input field.
\nDefaults to: 5
Character(s) to be inserted at the end of the label text.
\n\nSet to empty string to hide the separator completely.
\nDefaults to: ':'
A CSS style specification string to apply directly to this field's label.
\nA CSS style specification string to apply directly to this field's label.
\nThe width of the fieldLabel in pixels. Only applicable if the labelAlign is set to \"left\" or\n\"right\".
\nDefaults to: 100
The rendering template for the field decorations. Component classes using this mixin\nshould include logic to use this as their renderTpl,\nand implement the getSubTplMarkup method to generate the field body content.
\n\nThe structure of a field is a table as follows:
\n\nIf labelAlign: 'left',msgTarget: 'side'`
+----------------------+----------------------+-------------+\n | Label: | InputField | sideErrorEl |\n +----------------------+----------------------+-------------+\nIf labelAlign: 'left',msgTarget: 'under'`
+----------------------+------------------------------------+\n | Label: | InputField (colspan=2) |\n | | underErrorEl |\n +----------------------+------------------------------------+\nIf labelAlign: 'top',msgTarget: 'side'`
+---------------------------------------------+-------------+\n | label | |\n | InputField | sideErrorEl |\n +---------------------------------------------+-------------+\nIf labelAlign: 'top',msgTarget: 'under'`
+-----------------------------------------------------------+\n | label |\n | InputField (colspan=2) |\n | underErrorEl |\n +-----------------------------------------------------------+\nThe total columns always the same for fields with each setting of labelAlign because when\nrendered into a Ext.layout.container.Form layout, just the TR of the table\nwill be placed into the form's main TABLE, and the columns of all the siblings\nmust match so that they all line up. In a Ext.layout.container.Form layout, different\nsettings of labelAlign are not supported because of the incompatible column structure.
When the triggerCell or side error cell are hidden or shown, the input cell's colspan\nis recalculated to maintain the correct 3 visible column count.
\nDefaults to: ['<tr role="presentation" id="{id}-inputRow" <tpl if="inFormLayout">id="{id}"</tpl> class="{inputRowCls}">', '<tpl if="labelOnLeft">', '<td role="presentation" id="{id}-labelCell" style="{labelCellStyle}" {labelCellAttrs}>', '{beforeLabelTpl}', '<label id="{id}-labelEl" {labelAttrTpl}<tpl if="inputId"> for="{inputId}"</tpl> class="{labelCls}"', '<tpl if="labelStyle"> style="{labelStyle}"</tpl>', ' unselectable="on"', '>', '{beforeLabelTextTpl}', '<tpl if="fieldLabel">{fieldLabel}{labelSeparator}</tpl>', '{afterLabelTextTpl}', '</label>', '{afterLabelTpl}', '</td>', '</tpl>', '<td role="presentation" class="{baseBodyCls} {fieldBodyCls} {extraFieldBodyCls}" id="{id}-bodyEl" colspan="{bodyColspan}" role="presentation">', '{beforeBodyEl}', '<tpl if="labelAlign==\\'top\\'">', '{beforeLabelTpl}', '<div role="presentation" id="{id}-labelCell" style="{labelCellStyle}">', '<label id="{id}-labelEl" {labelAttrTpl}<tpl if="inputId"> for="{inputId}"</tpl> class="{labelCls}"', '<tpl if="labelStyle"> style="{labelStyle}"</tpl>', ' unselectable="on"', '>', '{beforeLabelTextTpl}', '<tpl if="fieldLabel">{fieldLabel}{labelSeparator}</tpl>', '{afterLabelTextTpl}', '</label>', '</div>', '{afterLabelTpl}', '</tpl>', '{beforeSubTpl}', '{[values.$comp.getSubTplMarkup(values)]}', '{afterSubTpl}', '<tpl if="msgTarget===\\'side\\'">', '{afterBodyEl}', '</td>', '<td role="presentation" id="{id}-sideErrorCell" vAlign="{[values.labelAlign===\\'top\\' && !values.hideLabel ? \\'bottom\\' : \\'middle\\']}" style="{[values.autoFitErrors ? \\'display:none\\' : \\'\\']}" width="{errorIconWidth}">', '<div role="presentation" id="{id}-errorEl" class="{errorMsgCls}" style="display:none"></div>', '</td>', '<tpl elseif="msgTarget==\\'under\\'">', '<div role="presentation" id="{id}-errorEl" class="{errorMsgClass}" colspan="2" style="display:none"></div>', '{afterBodyEl}', '</td>', '</tpl>', '</tr>', {disableFormats: true}]
The location where the error message text should display. Must be one of the following values:
\n\nqtip Display a quick tip containing the message when the user hovers over the field.\nThis is the default.
Ext.tip.QuickTipManager.init must have been called for this setting to work.
title Display the message in a default browser title attribute popup.
under Add a block div beneath the field containing the error message.side Add an error icon to the right of the field, displaying the message in a popup on hover.none Don't display any error message. This might be useful if you are implementing custom error display.[element id] Add the error message directly to the innerHTML of the specified element.Defaults to: 'qtip'
true to disable displaying any error message set on this object.
\nDefaults to: false
The div Element wrapping the component's contents. Only available after the component has been rendered.
\nDefaults to: ['labelCell', 'labelEl', 'bodyEl', 'sideErrorCell', 'errorEl', 'inputRow']
Overrides: Ext.util.ElementContainer.childEls
The div Element that will contain the component's error message(s). Note that depending on the configured\nmsgTarget, this element may be hidden in favor of some other form of presentation, but will always\nbe present in the DOM for use by assistive technologies.
\nDefaults to: ['<tpl if="errors && errors.length">', '<ul class="{listCls}"><tpl for="errors"><li role="alert">{.}</li></tpl></ul>', '</tpl>']
private
\nDefaults to: Ext.baseCSSPrefix + 'form-item-input-row'
Flag denoting that this object is labelable as a field. Always true.
\nDefaults to: true
The <TD> Element which contains the label Element for this component. Only available after the component has been rendered.
The label Element for this component. Only available after the component has been rendered.
\nDefaults to: ['beforeBodyEl', 'afterBodyEl', 'beforeLabelTpl', 'afterLabelTpl', 'beforeSubTpl', 'afterSubTpl', 'beforeLabelTextTpl', 'afterLabelTextTpl', 'labelAttrTpl']
This is an array to avoid a split on every call to Ext.copyTo
\nDefaults to: ['allowBlank', 'id', 'labelAlign', 'fieldBodyCls', 'extraFieldBodyCls', 'baseBodyCls', 'clearCls', 'labelSeparator', 'msgTarget', 'inputRowCls']
Tells the layout system that the height can be measured immediately because the width does not need setting.
\nDefaults to: true
Defaults to: ['<tpl if="errors && errors.length">', '<tpl for="errors"><tpl if="xindex > 1">\\n</tpl>{.}</tpl>', '</tpl>']
Get the reference to the current class from which this object was instantiated. Unlike statics,\nthis.self is scope-dependent and it's meant to be used for dynamic inheritance. See statics\nfor a detailed comparison
Ext.define('My.Cat', {\n statics: {\n speciesName: 'Cat' // My.Cat.speciesName = 'Cat'\n },\n\n constructor: function() {\n alert(this.self.speciesName); // dependent on 'this'\n },\n\n clone: function() {\n return new this.self();\n }\n});\n\n\nExt.define('My.SnowLeopard', {\n extend: 'My.Cat',\n statics: {\n speciesName: 'Snow Leopard' // My.SnowLeopard.speciesName = 'Snow Leopard'\n }\n});\n\nvar cat = new My.Cat(); // alerts 'Cat'\nvar snowLeopard = new My.SnowLeopard(); // alerts 'Snow Leopard'\n\nvar clone = snowLeopard.clone();\nalert(Ext.getClassName(clone)); // alerts 'My.SnowLeopard'\nCall the original method that was previously overridden with override
\n\nExt.define('My.Cat', {\n constructor: function() {\n alert(\"I'm a cat!\");\n }\n});\n\nMy.Cat.override({\n constructor: function() {\n alert(\"I'm going to be a cat!\");\n\n this.callOverridden();\n\n alert(\"Meeeeoooowwww\");\n }\n});\n\nvar kitty = new My.Cat(); // alerts \"I'm going to be a cat!\"\n // alerts \"I'm a cat!\"\n // alerts \"Meeeeoooowwww\"\nThis method has been deprecated
\nas of 4.1. Use callParent instead.
\n\nThe arguments, either an array or the arguments object\nfrom the current method, for example: this.callOverridden(arguments)
Returns the result of calling the overridden method
\nCall the \"parent\" method of the current method. That is the method previously\noverridden by derivation or by an override (see Ext.define).
\n\n Ext.define('My.Base', {\n constructor: function (x) {\n this.x = x;\n },\n\n statics: {\n method: function (x) {\n return x;\n }\n }\n });\n\n Ext.define('My.Derived', {\n extend: 'My.Base',\n\n constructor: function () {\n this.callParent([21]);\n }\n });\n\n var obj = new My.Derived();\n\n alert(obj.x); // alerts 21\nThis can be used with an override as follows:
\n\n Ext.define('My.DerivedOverride', {\n override: 'My.Derived',\n\n constructor: function (x) {\n this.callParent([x*2]); // calls original My.Derived constructor\n }\n });\n\n var obj = new My.Derived();\n\n alert(obj.x); // now alerts 42\nThis also works with static methods.
\n\n Ext.define('My.Derived2', {\n extend: 'My.Base',\n\n statics: {\n method: function (x) {\n return this.callParent([x*2]); // calls My.Base.method\n }\n }\n });\n\n alert(My.Base.method(10); // alerts 10\n alert(My.Derived2.method(10); // alerts 20\nLastly, it also works with overridden static methods.
\n\n Ext.define('My.Derived2Override', {\n override: 'My.Derived2',\n\n statics: {\n method: function (x) {\n return this.callParent([x*2]); // calls My.Derived2.method\n }\n }\n });\n\n alert(My.Derived2.method(10); // now alerts 40\nTo override a method and replace it and also call the superclass method, use\ncallSuper. This is often done to patch a method to fix a bug.
\nThe arguments, either an array or the arguments object\nfrom the current method, for example: this.callParent(arguments)
Returns the result of calling the parent method
\nThis method is used by an override to call the superclass method but bypass any\noverridden method. This is often done to \"patch\" a method that contains a bug\nbut for whatever reason cannot be fixed directly.
\n\nConsider:
\n\n Ext.define('Ext.some.Class', {\n method: function () {\n console.log('Good');\n }\n });\n\n Ext.define('Ext.some.DerivedClass', {\n method: function () {\n console.log('Bad');\n\n // ... logic but with a bug ...\n\n this.callParent();\n }\n });\nTo patch the bug in DerivedClass.method, the typical solution is to create an\noverride:
Ext.define('App.paches.DerivedClass', {\n override: 'Ext.some.DerivedClass',\n\n method: function () {\n console.log('Fixed');\n\n // ... logic but with bug fixed ...\n\n this.callSuper();\n }\n });\nThe patch method cannot use callParent to call the superclass method since\nthat would call the overridden method containing the bug. In other words, the\nabove patch would only produce \"Fixed\" then \"Good\" in the console log, whereas,\nusing callParent would produce \"Fixed\" then \"Bad\" then \"Good\".
The arguments, either an array or the arguments object\nfrom the current method, for example: this.callSuper(arguments)
Returns the result of calling the superclass method
\nGets the active error message for this component, if any. This does not trigger validation on its own, it merely\nreturns any message that the component may already hold.
\nThe active error message on the component; if there is no error, an empty string is returned.
\nGets an Array of any active error messages currently applied to the field. This does not trigger validation on\nits own, it merely returns any messages that the component may already hold.
\nThe active error messages on the component; if there are no errors, an empty Array is\nreturned.
\nCalculates the colspan value for the body cell - the cell which contains the input field.
\n\nThe field table structure contains 4 columns:
\nReturns the label for the field. Defaults to simply returning the fieldLabel config. Can be overridden\nto provide a custom generated label.
\nThis is a template method.\n a hook into the functionality of this class.\n Feel free to override it in child classes.
\nThe configured field label, or empty string if not defined
\nGet the input id, if any, for this component. This is used as the \"for\" attribute on the label element.\nImplementing subclasses may also use this as e.g. the id for their own input element.
\nThe input id
\nGenerates the arguments for the field decorations rendering template.
\nThe template arguments
\nGets the markup to be inserted into the outer template's bodyEl. Defaults to empty string, should be implemented\nby classes including this mixin as needed.
\nThe markup to be inserted
\nTells whether the field currently has an active error message. This does not trigger validation on its own, it\nmerely looks for any message that the component may already hold.
\nInitialize configuration for this class. a typical example:
\n\nExt.define('My.awesome.Class', {\n // The default config\n config: {\n name: 'Awesome',\n isAwesome: true\n },\n\n constructor: function(config) {\n this.initConfig(config);\n }\n});\n\nvar awesome = new My.awesome.Class({\n name: 'Super Awesome'\n});\n\nalert(awesome.getName()); // 'Super Awesome'\nthis
\nPerforms initialization of this mixin. Component classes using this mixin should call this method during their\nown initialization.
\nUpdates the rendered DOM to match the current activeError. This only updates the content and\nattributes, you'll have to call doComponentLayout to actually update the display.
\nSets the active error message to the given string. This replaces the entire error message contents with the given\nstring. Also see setActiveErrors which accepts an Array of messages and formats them according to the\nactiveErrorsTpl. Note that this only updates the error message element's text and attributes, you'll\nhave to call doComponentLayout to actually update the field's layout to match. If the field extends Ext.form.field.Base you should call markInvalid instead.
\nThe error message
\nSet the active error message to an Array of error messages. The messages are formatted into a single message\nstring using the activeErrorsTpl. Also see setActiveError which allows setting the entire error\ncontents with a single string. Note that this only updates the error message element's text and attributes,\nyou'll have to call doComponentLayout to actually update the field's layout to match. If the field extends\nExt.form.field.Base you should call markInvalid instead.
\nThe error messages
\nApplies a set of default configuration values to this Labelable instance. For each of the properties in the given\nobject, check if this component hasOwnProperty that config; if not then it's inheriting a default value from its\nprototype and we should apply the default value.
\nThe defaults to apply to the object.
\nSet the label of this field.
\nThe new label. The labelSeparator will be automatically appended to the label\nstring.
\nGet the reference to the class from which this object was instantiated. Note that unlike self,\nthis.statics() is scope-independent and it always returns the class from which it was called, regardless of what\nthis points to during run-time
Ext.define('My.Cat', {\n statics: {\n totalCreated: 0,\n speciesName: 'Cat' // My.Cat.speciesName = 'Cat'\n },\n\n constructor: function() {\n var statics = this.statics();\n\n alert(statics.speciesName); // always equals to 'Cat' no matter what 'this' refers to\n // equivalent to: My.Cat.speciesName\n\n alert(this.self.speciesName); // dependent on 'this'\n\n statics.totalCreated++;\n },\n\n clone: function() {\n var cloned = new this.self; // dependent on 'this'\n\n cloned.groupName = this.statics().speciesName; // equivalent to: My.Cat.speciesName\n\n return cloned;\n }\n});\n\n\nExt.define('My.SnowLeopard', {\n extend: 'My.Cat',\n\n statics: {\n speciesName: 'Snow Leopard' // My.SnowLeopard.speciesName = 'Snow Leopard'\n },\n\n constructor: function() {\n this.callParent();\n }\n});\n\nvar cat = new My.Cat(); // alerts 'Cat', then alerts 'Cat'\n\nvar snowLeopard = new My.SnowLeopard(); // alerts 'Cat', then alerts 'Snow Leopard'\n\nvar clone = snowLeopard.clone();\nalert(Ext.getClassName(clone)); // alerts 'My.SnowLeopard'\nalert(clone.groupName); // alerts 'Cat'\n\nalert(My.Cat.totalCreated); // alerts 3\nReturns the trimmed label by slicing off the label separator character. Can be overridden.
\nThe trimmed field label, or empty string if not defined
\nClears the active error message(s). Note that this only clears the error message element's text and attributes,\nyou'll have to call doComponentLayout to actually update the field's layout to match. If the field extends Ext.form.field.Base you should call clearInvalid instead.
\nAdd methods / properties to the prototype of this class.
\n\nExt.define('My.awesome.Cat', {\n constructor: function() {\n ...\n }\n});\n\n My.awesome.Cat.addMembers({\n meow: function() {\n alert('Meowww...');\n }\n });\n\n var kitty = new My.awesome.Cat;\n kitty.meow();\nAdd / override static properties of this class.
\n\nExt.define('My.cool.Class', {\n ...\n});\n\nMy.cool.Class.addStatics({\n someProperty: 'someValue', // My.cool.Class.someProperty = 'someValue'\n method1: function() { ... }, // My.cool.Class.method1 = function() { ... };\n method2: function() { ... } // My.cool.Class.method2 = function() { ... };\n});\nthis
\nBorrow another class' members to the prototype of this class.
\n\nExt.define('Bank', {\n money: '$$$',\n printMoney: function() {\n alert('$$$$$$$');\n }\n});\n\nExt.define('Thief', {\n ...\n});\n\nThief.borrow(Bank, ['money', 'printMoney']);\n\nvar steve = new Thief();\n\nalert(steve.money); // alerts '$$$'\nsteve.printMoney(); // alerts '$$$$$$$'\nThe class to borrow members from
\nThe names of the members to borrow
\nthis
\nCreate a new instance of this Class.
\n\nExt.define('My.cool.Class', {\n ...\n});\n\nMy.cool.Class.create({\n someConfig: true\n});\nAll parameters are passed to the constructor of the class.
\nthe created instance.
\nCreate aliases for existing prototype methods. Example:
\n\nExt.define('My.cool.Class', {\n method1: function() { ... },\n method2: function() { ... }\n});\n\nvar test = new My.cool.Class();\n\nMy.cool.Class.createAlias({\n method3: 'method1',\n method4: 'method2'\n});\n\ntest.method3(); // test.method1()\n\nMy.cool.Class.createAlias('method5', 'method3');\n\ntest.method5(); // test.method3() -> test.method1()\nThe new method name, or an object to set multiple aliases. See\nflexSetter
\nThe original method name
\nGet the current class' name in string format.
\n\nExt.define('My.cool.Class', {\n constructor: function() {\n alert(this.self.getName()); // alerts 'My.cool.Class'\n }\n});\n\nMy.cool.Class.getName(); // 'My.cool.Class'\nclassName
\nAdds members to class.
\nThis method has been deprecated since 4.1
\nUse addMembers instead.
\n\nOverride members of this class. Overridden methods can be invoked via\ncallParent.
\n\nExt.define('My.Cat', {\n constructor: function() {\n alert(\"I'm a cat!\");\n }\n});\n\nMy.Cat.override({\n constructor: function() {\n alert(\"I'm going to be a cat!\");\n\n this.callParent(arguments);\n\n alert(\"Meeeeoooowwww\");\n }\n});\n\nvar kitty = new My.Cat(); // alerts \"I'm going to be a cat!\"\n // alerts \"I'm a cat!\"\n // alerts \"Meeeeoooowwww\"\nAs of 4.1, direct use of this method is deprecated. Use Ext.define\ninstead:
\n\nExt.define('My.CatOverride', {\n override: 'My.Cat',\n constructor: function() {\n alert(\"I'm going to be a cat!\");\n\n this.callParent(arguments);\n\n alert(\"Meeeeoooowwww\");\n }\n});\nThe above accomplishes the same result but can be managed by the Ext.Loader\nwhich can properly order the override and its target class and the build process\ncan determine whether the override is needed based on the required state of the\ntarget class (My.Cat).
\nThis method has been deprecated since 4.1.0
\nUse Ext.define instead
\n\nThe properties to add to this class. This should be\nspecified as an object literal containing one or more properties.
\nthis class
\nFires when the active error message is changed via setActiveError.
\nThe active error message
\nThe options object passed to Ext.util.Observable.addListener.
\n\n\n\nHeight for form error icons.
\nDefaults to: 16px
Margin for error icons that are aligned to the side of the field
\nDefaults to: 0 1px
Width for form error icons.
\nDefaults to: 16px
The text color of form error messages
\nDefaults to: $form-field-invalid-border-color
The font-family of form error messages
\nDefaults to: $font-family
The font-size of form error messages
\nDefaults to: $font-size
The font-weight of form error messages
\nDefaults to: normal
The line-height of form error messages
\nDefaults to: $form-error-icon-height
The space between the icon and the message for errors that display under the field
\nDefaults to: 4px
The padding on errors that display under the form field
\nDefaults to: 2px 2px 2px 0
The bottom margin to apply to form items when in auto, anchor, vbox, or table layout
\nDefaults to: 5px
The text color of form field labels
\nDefaults to: $color
The font-family of form field labels
\nDefaults to: $font-family
The font-size of form field labels
\nDefaults to: $font-size
The font-weight of form field labels
\nDefaults to: normal
The line-height of form field labels
\nDefaults to: round ( $form-label-font-size * 1.15 )
The text color of toolbar field labels
\nDefaults to: $color
The font-family of toolbar field labels
\nDefaults to: $font-family
The font-size of toolbar field labels
\nDefaults to: $font-size
The font-weight of toolbar field labels
\nDefaults to: normal
The line-height of toolbar field labels
\nDefaults to: round ( $form-toolbar-label-font-size * 1.15 )