Many classes have shortcut names used when creating (instantiating) a class with a
configuration object. The shortcut name is referred to as an alias (or xtype if the
class extends Ext.Component). The alias/xtype is listed next to the class name of
applicable classes for quick reference.
Framework classes or their members may be specified as private or protected. Else,
the class / member is public. Public, protected, and private are access
descriptors used to convey how and when the class or class member should be used.
Public classes and class members are available for use by any other class or application code and may be relied upon as a stable and persistent within major product versions. Public classes and members may safely be extended via a subclass.
Protected class members are stable public members intended to be used by the
owning class or its subclasses. Protected members may safely be extended via a subclass.
Private classes and class members are used internally by the framework and are not intended to be used by application developers. Private classes and members may change or be omitted from the framework at any time without notice and should not be relied upon in application logic.
static label next to the
method name. *See Static below.Below is an example class member that we can disect to show the syntax of a class member (the lookupComponent method as viewed from the Ext.button.Button class in this case).
Let's look at each part of the member row:
lookupComponent in this example)( item ) in this example)Ext.Component in this case). This may be omitted for methods that do not
return anything other than undefined or may display as multiple possible values
separated by a forward slash / signifying that what is returned may depend on the
results of the method call (i.e. a method may return a Component if a get method calls is
successful or false if unsuccessful which would be displayed as
Ext.Component/Boolean).PROTECTED in
this example - see the Flags section below)Ext.container.Container in this example). The source
class will be displayed as a blue link if the member originates from the current class
and gray if it is inherited from an ancestor or mixed-in class.view source in the example)item : Object in the example).undefined a "Returns" section
will note the type of class or object returned and a description (Ext.Component in the
example)Available since 3.4.0 - not pictured in
the example) just after the member descriptionDefaults to: false)The API documentation uses a number of flags to further commnicate the class member's function and intent. The label may be represented by a text label, an abbreviation, or an icon.
classInstance.method1().method2().etc();false is returned from
an event handler- Indicates a framework class
- A singleton framework class. *See the singleton flag for more information
- A component-type framework class (any class within the Ext JS framework that extends Ext.Component)
- Indicates that the class, member, or guide is new in the currently viewed version
- Indicates a class member of type config
- Indicates a class member of type property
- Indicates a class member of type
method
- Indicates a class member of type event
- Indicates a class member of type
theme variable
- Indicates a class member of type
theme mixin
- Indicates that the class, member, or guide is new in the currently viewed version
Just below the class name on an API doc page is a row of buttons corresponding to the types of members owned by the current class. Each button shows a count of members by type (this count is updated as filters are applied). Clicking the button will navigate you to that member section. Hovering over the member-type button will reveal a popup menu of all members of that type for quick navigation.
Getting and setter methods that correlate to a class config option will show up in the methods section as well as in the configs section of both the API doc and the member-type menus just beneath the config they work with. The getter and setter method documentation will be found in the config row for easy reference.
Your page history is kept in localstorage and displayed (using the available real estate) just below the top title bar. By default, the only search results shown are the pages matching the product / version you're currently viewing. You can expand what is displayed by clicking on the button on the right-hand side of the history bar and choosing the "All" radio option. This will show all recent pages in the history bar for all products / versions.
Within the history config menu you will also see a listing of your recent page visits. The results are filtered by the "Current Product / Version" and "All" radio options. Clicking on the button will clear the history bar as well as the history kept in local storage.
If "All" is selected in the history config menu the checkbox option for "Show product details in the history bar" will be enabled. When checked, the product/version for each historic page will show alongside the page name in the history bar. Hovering the cursor over the page names in the history bar will also show the product/version as a tooltip.
Both API docs and guides can be searched for using the search field at the top of the page.
On API doc pages there is also a filter input field that filters the member rows using the filter string. In addition to filtering by string you can filter the class members by access level, inheritance, and read only. This is done using the checkboxes at the top of the page.
The checkbox at the bottom of the API class navigation tree filters the class list to include or exclude private classes.
Clicking on an empty search field will show your last 10 searches for quick navigation.
Each API doc page (with the exception of Javascript primitives pages) has a menu view of metadata relating to that class. This metadata view will have one or more of the following:
Ext.button.Button class has an alternate class name of Ext.Button). Alternate class
names are commonly maintained for backward compatibility.Runnable examples (Fiddles) are expanded on a page by default. You can collapse and expand example code blocks individually using the arrow on the top-left of the code block. You can also toggle the collapse state of all examples using the toggle button on the top-right of the page. The toggle-all state will be remembered between page loads.
Class members are collapsed on a page by default. You can expand and collapse members using the arrow icon on the left of the member row or globally using the expand / collapse all toggle button top-right.
Viewing the docs on narrower screens or browsers will result in a view optimized for a smaller form factor. The primary differences between the desktop and "mobile" view are:
The class source can be viewed by clicking on the class name at the top of an API doc page. The source for class members can be viewed by clicking on the "view source" link on the right-hand side of the member row.
Ext.Mixin
Ext.mixin.Accessible
Ext.mixin.Bindable
Ext.mixin.Bufferable
Ext.mixin.ComponentDelegation
Ext.mixin.ConfigProxy
Ext.mixin.Container
Ext.mixin.Factoryable
Ext.mixin.Focusable
Ext.mixin.FocusableContainer
Ext.mixin.Identifiable
Ext.mixin.Inheritable
Ext.mixin.ItemRippler
Ext.mixin.Keyboard
Ext.mixin.Observable
Ext.mixin.Pluggable
Ext.mixin.Queryable
Ext.state.Stateful
Ext.TitleBar
Ext.grid.NavigationModel
Ext.grid.Row
Ext.grid.column.Column
Ext.grid.column.Date
Ext.grid.column.Template
Ext.grid.menu.*
Ext.grid.HeaderContainer
Ext.grid.selection.*
Ext.grid.plugin.ColumnResizing
Ext.grid.plugin.HeaderReorder
Grids are an excellent way of showing large amounts of tabular data on the client side.
Essentially a supercharged <table>, Grid makes it easy to fetch, sort and filter large
amounts of data.
Grids are composed of two main pieces - a Ext.data.Store full of data and a set of columns to render.
var store = Ext.create('Ext.data.Store', {
fields: ['name', 'email', 'phone'],
data: [
{ 'name': 'Lisa', "email":"[email protected]", "phone":"555-111-1224" },
{ 'name': 'Bart', "email":"[email protected]", "phone":"555-222-1234" },
{ 'name': 'Homer', "email":"[email protected]", "phone":"555-222-1244" },
{ 'name': 'Marge', "email":"[email protected]", "phone":"555-222-1254" }
]
});
Ext.create('Ext.grid.Grid', {
title: 'Simpsons',
store: store,
columns: [
{ text: 'Name', dataIndex: 'name', width: 200 },
{ text: 'Email', dataIndex: 'email', width: 250 },
{ text: 'Phone', dataIndex: 'phone', width: 120 }
],
height: 200,
layout: 'fit',
fullscreen: true
});
The code above produces a simple grid with three columns. We specified a Store which will load JSON data inline. In most apps we would be placing the grid inside another container and wouldn't need to provide the height, width and cfg-fullscreen options but they are included here to for demonstration.
The grid we created above will contain a header bar with a title ('Simpsons'), a row of column headers directly underneath and finally the grid rows under the headers.
By default, each Ext.grid.column.Column is sortable and toggles between ascending and descending sorting when you click on its header. There are several basic configs that can be applied to columns to change these behaviors. For example:
columns: [
{
text: 'Name',
dataIndex: 'name',
sortable: false, // column cannot be sorted
width: 250
},
{
text: 'Email',
dataIndex: 'email',
hidden: true // column is initially hidden
},
{
text: 'Phone',
dataIndex: 'phone',
width: 100
}
]
We turned off sorting on the 'Name' column so clicking its header now has no effect. We also made the Email column hidden by default (it can be shown again by using the Ext.grid.plugin.ViewOptions plugin). See the Ext.grid.column.Column for more details.
A top-level column definition may contain a columns configuration. This means that the
resulting header will be a group header, and will contain the child columns.
Grid extends the Ext.dataview.List component and connects records in the
store to Ext.grid.Row for the list's items. The Row component
utilizes the configs of the grid's Ext.grid.column.Column to create the
appropriate type of Ext.grid.cell.Base. Essentially, a Row is a container
for Ext.Widget.
For the most part, configuring a grid is about configuring the columns and their cells. There are several built-in column types to display specific types of data:
These columns specify (via their cell config) one of these basic cell widget types:
In addition to the above basic cell types, there are two other useful cell types to know about:
widget config. The most
important part of this config is the xtype of the child item to create.One technique to controll cell content and styling is to use data binding to target cell configs like Ext.grid.cell.Base#cls and Ext.grid.cell.Base#bodyCls. This is done by assigning a Ext.app.ViewModel to each Row like so:
itemConfig: {
viewModel: true // create default ViewModel for each item (i.e., Row)
}
Now that each Row has a ViewModel, cells can bind to the fields of the associated record like so:
columns: [{
...
cell: {
bind: {
cls: '{record.someCls}'
}
}
}]
The "record" property in the ViewModel is managed by the Row. As Row instances are recycled due to buffered rendering, the associated record instance simply changes over time.
When using Ext.grid.cell.Widget, the contained widgets can also use binding to configure themsleves using properties of the associated record.
columns: [{
...
cell: {
xtype: 'widgetcell',
widget: {
xtype: 'button',
bind: {
text: 'Update {record.firstName}'
}
}
}
}]
In some cases a custom ViewModel could be useful, for example to provide useful values via formulas.
itemConfig: {
viewModel: {
type: 'rowViewModel'
}
}
Columns provide two other mechanisms to format their cell content:
These column configs are processed by the default cell type for a column. These configs have some downsides compared to data binding but are provided for compatibility with previous releases.
Every grid is attached to a Ext.data.Store, which provides multi-sort and filtering capabilities. It's easy to set up a grid to be sorted from the start:
var myGrid = Ext.create('Ext.grid.Panel', {
store: {
fields: ['name', 'email', 'phone'],
sorters: ['name', 'phone']
},
columns: [
{ text: 'Name', dataIndex: 'name' },
{ text: 'Email', dataIndex: 'email' }
]
});
Sorting at run time is easily accomplished by simply clicking each column header. If you need to perform sorting on more than one field at run time it's easy to do so by adding new sorters to the store:
myGrid.store.sort([
{ property: 'name', direction: 'ASC' },
{ property: 'email', direction: 'DESC' }
]);
See Ext.data.Store for examples of filtering.
Grid supports addition of extra functionality through plugins:
Ext.grid.plugin.ViewOptions - adds the ability to show/hide columns and reorder them.
Ext.grid.plugin.ColumnResizing - allows for the ability to resize columns.
Ext.grid.plugin.Editable - editing grid contents one row at a time.
Ext.grid.plugin.RowOperations - selecting and performing tasks on severalrows at a time (e.g. deleting them).
Ext.grid.plugin.PagingToolbar - adds a toolbar at the bottom of the grid that allows you to quickly navigate to another page of data.
SummaryRow - adds and pins an additional row to the top of the grid that enables you to display summary data.
An array of column definition objects which define all columns that appear in this grid. Each column definition provides the header text for the column, and a definition of where the data for that column comes from.
This can also be a configuration object for a {Ext.grid.header.Container HeaderContainer} which may override certain default configurations if necessary. For example, the special layout may be overridden to use a simpler layout, or one can set default values shared by all columns:
columns: {
items: [
{
text: "Column A"
dataIndex: "field_A",
width: 200
},{
text: "Column B",
dataIndex: "field_B",
width: 150
},
...
]
}
Defaults to:
null
Get columns using a selector to filter which columns to return.
selector : String/Function
If the selector is a String, columns will be found using
Ext.ComponentQuery. If the selector is a Function,
Ext.Array#filter will be used to filter the columns.
If no selector is provided, all columns will be returned.
Can be either a Store instance or a configuration object that will be turned into a Store. The Store is used to populate the set of items that will be rendered in the DataView. See the DataView intro documentation for more information about the relationship between Store and DataView.
Defaults to:
undefined
DOM tabIndex attribute to set on the active Focusable child of this container when using the "Roaming tabindex" technique.
Defaults to:
0
The item from the cfg-items collection that will be active first. This is usually only meaningful in a Ext.layout.Card, where only one item can be active at a time. If passed a string, it will be assumed to be a Ext.ComponentQuery selector. A number will reference an index or a Ext.Component instance may be passed as well. An object config will be created as a new component.
Defaults to:
0
Returns the value of activeItem
Ext.Component / Object / String / Number
Sets the value of activeItem
activeItem : Ext.Component / Object / String / Number
Set this to true
to enable focusing disabled child items via keyboard.
Defaults to:
false
A flag indicating that this component should be above its floated siblings.
This may be a positive number to prioritize the ordering of multiple visible always on top components.
This may be set to a negative number to prioritize a component to the bottom of the z-index stack.
Defaults to:
false
Available since: 6.2.0
An object containing ARIA attributes to be set
on this Component's ARIA element. Use this to set the attributes that cannot be
determined by the Component's state, such as aria-live, aria-flowto, etc.
Note that this config is only meaningful at the Component rendering time, and setting it after that will do nothing.
Defaults to:
null
Sets the value of ariaAttributes
ariaAttributes : Object
DOM selector for a child element that is to be used
as description for this Component, set in aria-describedby attribute.
The selector works the same way as ariaLabelledBy.
ARIA label for this Component. It is best to use
ariaLabelledBy option instead, because screen readers prefer
aria-labelledby attribute to aria-label. ariaLabel and
ariaLabelledBy config options are mutually exclusive.
DOM selector for a child element that is to be used
as label for this Component, set in aria-labelledby attribute.
If the selector is by id, the label element can be any existing element,
not necessarily a child of the main Component element.
ariaLabelledBy and ariaLabel config options are
mutually exclusive, and ariaLabelledBy has the higher precedence.
Set this config to false to limit rendering data to just the record's data
or to an object to describe the desired associated data. This data is used to
satisfy the itemTpl. The default of true will gather all associated data
that is currently loaded. This can be expensive. If only a small amount of the
available data is needed, this config can speed up the rendering process.
For example, if an OrderItem needs the Item data but not its parent Order,
this config can be set like so:
associatedData: {
item: true
}
Given the above, only the item association (to the Item record) will be
gathered into the render data.
For more details, see getData.
Defaults to:
true
Available since: 6.5.0
If true, child items will be destroyed as soon as they are
removed from this container.
Defaults to:
true
May be set to false for improved layout performance if auto-sizing is not required.
Some versions of Safari, both desktop and mobile, have very slow performance if the application has deeply nested containers due to the following WebKit bug: https://bugs.webkit.org/show_bug.cgi?id=150445
Applications that experience performance issues in the affected versions of
Safari may need to turn off autoSizing globally for all Ext.Container instances
by placing the following override in the application's "overrides" directory:
Ext.define('MyApp.overrides.Container', {
override: 'Ext.Container',
config: {
autoSize: false
}
});
Once auto-sizing support has turned off by default, it can be selectively
turned back on only on those container instances that explicitly need auto-sizing
behavior by setting autoSize to true.
This option can also be used to allow items to be sized in percentage units as a workaround for the following browser bug: https://bugs.webkit.org/show_bug.cgi?id=137730
To illustrate, the following example should render a 200px by 200px green box
(the container) with a yellow box inside of it (the child item). The child
item's height and width are both set to '50%' so the child should render
exactly 100px by 100px in size.
Ext.create({
xtype: 'container',
renderTo: Ext.getBody(),
height: 200,
width: 200,
style: 'background: green',
items: [{
xtype: 'component',
style: 'background: yellow',
height: '50%',
width: '50%'
}]
});
All browsers except for Safari render the previous example correctly, but
Safari does not assign a height to the component. To make percentage-sized
items work in Safari, simply set autoSize to false on the container.
Since the underlying implementation works by absolutely positioning the container's
body element, this option can only be used when the container is not
"shrink wrapping" the content in either direction. When autoSize is
set to false, shrink wrapped dimension(s) will collapse to 0.
Defaults to:
null
If true, then, when showBy or alignTo fallback on
constraint violation only takes place along the major align axis.
That is, if alignment "l-r" is being used, and axisLock: true is used,
then if constraints fail, only fallback to "r-l" is considered.
Defaults to:
null
Setting this config option adds or removes data bindings for other configs.
For example, to bind the title config:
var panel = Ext.create({
xtype: 'panel',
bind: {
title: 'Hello {user.name}'
}
});
To dynamically add bindings:
panel.setBind({
title: 'Greetings {user.name}!'
});
To remove bindings:
panel.setBind({
title: null
});
The bind expressions are presented to Ext.app.ViewModel#bind. The
ViewModel instance is determined by lookupViewModel.
Note: If bind is passed as a string, it will use the Ext.Component#property-defaultBindProperty for the binding.
Defaults to:
null
The CSS class to add to this container's body element.
Defaults to:
null
Available since: 7.0
Enables or disables bordering on this component. The following values are accepted:
null or `true (default): Do nothing and allow the border to be specified
by the theme.false: suppress the default border provided by the theme.Please note that enabling bordering via this config will not add a border-color
or border-style CSS property to the component; you provide the border-color
and border-style via CSS rule or style configuration
(if not already provide by the theme).
Ext.Viewport.add({
centered: true,
width: 100,
height: 100,
style: 'border: 1px solid blue;'
// ...
});
Ext.Viewport.add({
centered: true,
width: 100,
height: 100,
cls: 'my-component'
// ...
});
And your CSS file:
.my-component {
border: 1px solid red;
}
Defaults to:
null
The absolute bottom position of this Component; must be a valid CSS length value,
e.g: 300, 100px, 30%, etc. Explicitly setting this value will make this Component
become 'positioned', which means it will no longer participate in the layout of the
Container that it resides in.
Defaults to:
null
The number of items an infinite list will render beyond those immediately
visible.
To prevent the rendering of items while scrolling, these extra items are
rendered out of view. When the scroller approaches within minimumBufferSize
of the end of the rendered range, the extra items trailing the scroll will be
repositioned (and reconfigured) ahead of the scroll.
Defaults to:
20
Animation to be used during transitions of cards.
This method has been REMOVED since 2.0.0
Configure this as true to have this Component centered within its Container.
Setting this value to true will make this Component become 'positioned', which means
it will no longer participate in the layout of the Container that it resides in.
Defaults to:
false
The CSS class to add to this widget's element, in addition to the baseCls. In many cases, this property will be specified by the derived widget class. See userCls for adding additional CSS classes to widget instances (such as items in a Ext.Container).
Defaults to:
null
This config object supplies default for the collapsible config. When that
config is simply true, this is the complete config object for the group
collapser.
NOTE: This config cannot be changed after instantiation. Instead, change the
collapsible config.
Defaults to:
{
xclass: 'Ext.dataview.ListCollapser'
}
Available since: 7.0
Returns the value of collapseDefaults
Sets the value of collapseDefaults
collapseDefaults : Ext.dataview.ListCollapser / Object
This object configures group collapse. It is only applicable when grouped.
Set to false to disable group collapsibility. The default value of true
uses the collapseDefaults config for the final collapser configuration
object. If this config is an object, it is merged with collapseDefaults
giving this object's properties priority over the defaults.
Defaults to:
true
Available since: 7.0
Returns the value of collapsible
Sets the value of collapsible
collapsible : Ext.dataview.ListCollapser / Object / Boolean
This is a config object which is used by columns in this grid to create their header menus.
The default column menu contains the following items.
These items have weight of -100, -90 and -80 respectively to
place them at the start of the menu.
This can be configured as null to prevent columns from showing a column menu.
Defaults to:
{
xtype: 'menu',
weighted: true,
align: 'tl-bl?',
hideOnParentHide: false,
// Persists when owning Column is hidden
items: {
sortAsc: {
xtype: 'gridsortascmenuitem',
group: 'sortDir',
weight: -100
},
// Wants to be the first
sortDesc: {
xtype: 'gridsortdescmenuitem',
group: 'sortDir',
weight: -90
},
// Wants to be the second
//---------------------------------
// Columns menu is inserted here
//---------------------------------
groupByThis: {
xtype: 'gridgroupbythismenuitem',
handler: 'column.onGroupByThis',
separator: true,
weight: -50
},
showInGroups: {
xtype: 'gridshowingroupsmenuitem',
handler: 'column.onToggleShowInGroups',
weight: -40
}
}
}
The config object for the grid's column hide/show menu
Defaults to:
{
xtype: 'gridcolumnsmenu',
weight: -80,
separator: true
}
Sets the value of columnsMenuItem
columnsMenuItem : Ext.grid.menu.Columns
A specification of the constraint to apply when showBy or alignTo is called to align a floated or positioned component.
Defaults to the parent container for positioned components (components which have their top, right, bottom or left set to move them out of their container's layout flow).
Defaults to the viewport for floated components.
May be a Ext.ComponentQuery selector to find an ancestor component to constrain within.
May be false to specify that constraining is not applied.
You may also specify an element, or a Ext.util.Region
Defaults to:
null
Returns the value of constrainAlign
Sets the value of constrainAlign
constrainAlign : String / Ext.util.Region / Ext.dom.Element
The configured element will automatically be added as the content of this component. When you pass a string, we expect it to be an element id. If the content element is hidden, we will automatically show it.
Defaults to:
null
Returns the value of contentEl
Ext.dom.Element / HTMLElement / String
Sets the value of contentEl
contentEl : Ext.dom.Element / HTMLElement / String
Enables you to easily control Components inside this Container by listening to their events and taking some action. For example, if we had a container with a nested Disable button, and we wanted to hide the Container when the Disable button is tapped, we could do this:
Ext.create({
xtype: 'container',
control: {
'button[text=Disable]': {
tap: 'hideMe'
}
},
hideMe: function() {
this.hide();
}
});
We used a Ext.ComponentQuery selector to listen to the tap
event on any Ext.Button anywhere inside the Container that has the
text 'Disable'. Whenever a Component matching that selector
fires the tap event our hideMe function is called. hideMe is called with scope:
this (e.g. this is the Container instance).
Defaults to:
null
A string alias, a configuration object or an instance of a ViewController for
this container. Sample usage:
Ext.define('MyApp.UserController', {
alias: 'controller.user'
});
Ext.define('UserContainer', {
extend: 'Ext.container.container',
controller: 'user'
});
// Or
Ext.define('UserContainer', {
extend: 'Ext.container.container',
controller: {
type: 'user',
someConfig: true
}
});
// Can also instance at runtime
var ctrl = new MyApp.UserController();
var view = new UserContainer({
controller: ctrl
});
Defaults to:
null
Returns the Ext.app.ViewController instance associated with this component via the controller config or setController method.
Returns this component's ViewController or null if one was not configured
Sets the value of controller
controller : String / Object / Ext.app.ViewController
The initial set of data to apply to the tpl to
update the content area of the Component.
Note: Data will be appended to any existing data.
Defaults to:
null
Specifies a child Component to receive focus when this Container's method-focus method is called. Should be a valid Ext.ComponentQuery selector.
Defaults to:
null
If true, this component will be the default scope (this pointer) for events
specified with string names so that the scope can be dynamically resolved. The
component will automatically become the defaultListenerScope if a
controller is specified.
See the introductory docs for Ext.container.Container for some sample usages.
NOTE: This value can only be reliably set at construction time. Setting it after that time may not correctly rewire all of the potentially effected listeners.
Defaults to:
false
Sets the value of defaultListenerScope
defaultListenerScope : Boolean
A set of default configurations to apply to all child Components in this Container. It's often useful to specify defaults when creating more than one items with similar configurations. For example here we can specify that each child is a panel and avoid repeating the xtype declaration for each one:
Ext.create({
xtype: 'container',
defaults: {
xtype: 'panel'
},
items: [
{
html: 'Panel 1'
},
{
html: 'Panel 2'
}
]
});
Defaults to:
null
As a Ext.Container, this config controls the default type of items that are added.
Non-data items can also be added to this container, and these will pick up this
default. This config will only apply to data items if itemConfig does not contain
an xtype property (which it does by default). This means that data items will
not be affected by this config unless an itemConfig is set that nulls out the
xtype (not recommended).
Sets the value of defaultType
defaultType : Ext.enums.Widget
Set to false to not defer emptyText being applied until the store's first
load.
Defaults to:
true
Sets the value of deferEmptyText
deferEmptyText : Boolean
When set to true, tapping on the DataView's background (i.e. not on an item in the DataView) will deselect any currently selected items.
Defaults to:
true
Sets the value of deselectOnContainerClick
deselectOnContainerClick : Boolean
Set to true to disable selection styling. This only affects the presentation
of the selection not the internal selection state.
Defaults to:
false
Sets the value of disableSelection
disableSelection : Boolean
A property to check on each record to display the disclosure on a per record basis. This property must be false to prevent the disclosure from being displayed on the item.
Defaults to:
'disclosure'
Sets the value of disclosureProperty
disclosureProperty : String
Set to true to call show and false to call hide. Unlike the hidden
config, changing this config will potentially involve animations to show or
hide the component.
Defaults to:
null
Available since: 6.5.0
The dock position of this component in its container. Can be left, top, right or
bottom.
Notes
You must use a HTML5 doctype for docked bottom to work. To do this, simply
add the following code to the HTML file:
<!doctype html>
So your index.html file should look a little like this:
<!doctype html>
<html>
<head>
<title>MY application title</title>
...
Defaults to:
null
Set to true to allow this component to be dragged. This can also be the config
object for the Ext.drag.Source that will manage the drag.
Defaults to:
null
Sets the value of draggable
draggable : Boolean / Object / Ext.drag.Source
The text to render when the rendering of the item via itemTpl produces no
text.
Defaults to:
'\xa0'
The text to display in the view when there is no data to display.
Set this to true to display the default message.
Defaults to:
null
This component config object is used to create the emptyText component.
Defaults to:
{
xtype: 'emptytext'
}
Available since: 6.5.0
Sets the value of emptyTextDefaults
emptyTextDefaults : Object / Ext.Component
The config to set on the emptyText component to contain the desired text.
Defaults to:
'html'
Available since: 6.5.0
Set to false to disable column reorder.
Note: if gridviewoptions plugin is enabled on grids gets
precedence over enableColumnMove for touch supported device.
Defaults to:
true
Sets the value of enableColumnMove
enableColumnMove : Boolean
True to enable text selection inside this view.
Defaults to:
null
Deprecated since version 6.5.1
Use Ext.Component#userSelectable instead.
Sets the value of enableTextSelection
enableTextSelection : Boolean
Animation effect to apply when the Component is being shown. Typically you want to use an inbound animation type such as 'fadeIn' or 'slideIn'.
Defaults to:
null
Deprecated since version 2.0.0
Please use showAnimation instead.
Sets the value of enterAnimation
enterAnimation : String / Mixed
A map of event type to the corresponding handler method name. This is used internally by native event handling mechanism.
Defaults to:
{
focus: 'handleFocusEvent',
blur: 'handleBlurEvent'
}
Deprecated since version 6.6.0
Inline event handlers are deprecated
Animation effect to apply when the Component is being hidden.
Defaults to:
null
Deprecated since version 2.0.0
Please use hideAnimation instead. Typically you want to use
an outbound animation type such as 'fadeOut' or 'slideOut'.
Sets the value of exitAnimation
exitAnimation : String / Mixed
The flex of this item if this item item is inside a Ext.layout.HBox or Ext.layout.VBox layout.
You can also update the flex of a component dynamically using the Ext.layout.FlexBox#setItemFlex method.
When supplied as a string or number this option supports the same syntax as CSS flex. For example:
flex: '1 2 auto'
sets flex-grow property to 0, flex-shrink to 2 and flex-basis to
'auto'.
The default flex-shrink value for box layout items is set to 0 in the
stylesheet, which is different from the browser's default flex-shrink value
of 1. This accommodates the majority use case for applications since where
non-flexed components are typically not expected to shrink smaller than their
default size.
For convenience when only a single number is supplied it is used as the value
for both flex-grow and flex-shrink, for example flex: 3 is the same as
flex: '3 3'
An object form is also accepted:
flex: {
grow: 1,
shrink: 2,
basis: 'auto'
}
When the object form is supplied shrink always defaults to 0 regardless
of the value of grow.
Although 'auto' is the default value for flex-basis, flex-basis defaults to 0%
when flex is supplied as a single numeric or string value (e.g. flex: 1). If
this behavior is not desired either explicitly set flex-basis to 'auto' or use
the object form to set only grow and/or shrink:
flex: {
grow: 2
}
Defaults to:
null
A Component may be floated above all other components in the application. This means that the component is absolutely positioned, and will move to the front and occlude other sibling floated component if clicked.
A Floated component may have floated descendants. It will bring these decendants to the front with it when brought to the front of its sibling floated components.
By default, descendant floated components are all positioned using the viewport
coordinate system. To make a floating component a positioning parent for descendants,
and have the ancestors positioned relatively, configure the parent floated component
with cfg-relative: true.
Defaults to:
false
Available since: 6.2.0
Enable or disable navigation with arrow keys for this FocusableContainer. This option may be useful with nested FocusableContainers, when only the root container should handle keyboard events.
Defaults to:
false
CSS class that will be added to focused component's focusClsEl, and removed when component blurs.
Defaults to:
'x-focused'
Force the component to take up 100% width and height available, by adding it to Ext.Viewport.
Set to false turn off all grouping.
This setting is only meaningful if the underlying store has a grouper.
Defaults to:
true
This config is used to configure a header to display above each group in a grouped list. One of the more common uses of this config is to set the tpl.
groupHeader: {
tpl: 'Group: {name}'
}
Defaults to:
{
xtype: 'rowheader'
}
Sets the value of groupHeader
groupHeader : Object / Ext.dataview.ItemHeader
This config provides defaults for the placeholder items rendered for collapsed groups.
Defaults to:
{
xtype: 'listitemplaceholder'
}
Available since: 7.0
Returns the value of groupPlaceholder
Sets the value of groupPlaceholder
groupPlaceholder : Object / Ext.dataview.ListItemPlaceholder
The height of this Component; must be a valid CSS length value, e.g: 300, 100px,
30%, etc. By default, if this is not explicitly set, this Component's element will
simply have its own natural size. If set to auto, it will set the width to null
meaning it will have its own natural size.
Defaults to:
null
Animation effect to apply when the Component is being hidden. Typically you want to use an outbound animation type such as 'fadeOut' or 'slideOut'. For more animations, check the Ext.fx.Animation#type config.
Defaults to:
null
Sets the value of hideAnimation
hideAnimation : String / Mixed
true to hide the grid column headers.
Defaults to:
false
Available since: 6.0.1
A String which specifies how this component's DOM element will be hidden. The accepted values are any of these:
'clip' : Hide using clip.'display' : Hide using display.'offsets' : Hide using positioning offsets.'opacity' : Hide using opacity.'visibility' : Hide using visibility.Hiding using display results in having no dimensions as well as resetting
scroll positions to 0.
The other modes overcome this but may have different trade-offs in certain circumstances.
Defaults to:
'display'
Available since: 6.5.0
Returns the value of hideMode
'clip' / 'display' / 'offsets' / 'opacity' / 'visibility'
Sets the value of hideMode
hideMode : 'clip' / 'display' / 'offsets' / 'opacity' / 'visibility'
When using a modal Component, setting this to true will hide
the modal mask and the Container when the mask is tapped on.
Defaults to:
null
Defaults to:
null
Available since: 6.5.0
Sets the value of horizontalOverflow
horizontalOverflow : Object
Optional HTML content to render inside this Component, or a reference to an existing element on the page.
Defaults to:
null
Returns the value of html
String / Ext.dom.Element / HTMLElement
The unique id of this component instance.
It should not be necessary to use this configuration except for singleton objects in your application. Components created with an id may be accessed globally using Ext.getCmp.
Instead of using assigned ids, use the itemId config, and Ext.ComponentQuery which provides selector-based searching for Sencha Components analogous to DOM querying. The Ext.Container class contains shortcut methods to query its descendant Components by selector.
Note that this id will also be used as the element id for the containing HTML element that is rendered to the page for this component. This allows you to write id-based CSS rules to style the specific instance of this component uniquely, and also to select sub-elements using this component's id as the parent.
Note: to avoid complications imposed by a unique id also see itemId.
Defaults to an auto-assigned id.
Retrieves the id. This method Will auto-generate an id if one has not already
been configured.
id
DOM tabIndex attribute to set on inactive Focusable children of this container when using the "Roaming tabindex" technique. This value rarely needs to be changed from its default.
Defaults to:
-1
Set to true to render an alphabet IndexBar docked on the right. This can also
be a config object for the Ext.dataview.IndexBar component.
Defaults to:
null
Sets the value of indexBar
indexBar : Boolean / Object / Ext.dataview.IndexBar
Set to true to if this list should anticipate too many rows to render to the
DOM at one time. When set to true, only a fixed number of rows is rendered at
once, depending on the height or maxHeight of the list.
When using this mode in an auto-height situation (where the list should be
the height of its items), a maxHeight setting is required. This is due to
the fact that the rendered items are absolutely positioned. As such they do not
directly contribute to the list's height.
When maxHeight is set, however, an infinite list uses that setting to decide
how many items to render and will set an appropriate height on its innermost
element, thereby allowing the list to achieve the proper height.
Note that this configuration can not be dynamically changed after the list has instantiated.
Defaults to:
true
When set to true the items within the DataView will have their display set to
inline-block and be arranged horizontally. By default the items will wrap to
the width of the DataView. Passing an object with { wrap: false } will turn
off this wrapping behavior and overflowed items will need to be scrolled to
horizontally.
Defaults to:
null
A string to add to the immediate parent element of the inner items of this
container. That is, items that are not docked, positioned or floated. In
some containers, positioned items may be in this same element.
Defaults to:
null
Available since: 6.5.0
An extra CSS class or classes to augment the classCls on an individual instance
Defaults to:
null
Available since: 6.5.0
True to cause items to act like buttons for interaction styling. in ButtonMode items will maintain pressed state whenever pressed down. they will not remove this state for tap distance cancellation or mouse out.
Defaults to:
false
Sets the value of itemButtonMode
itemButtonMode : Boolean
The object is used to configure the Ext.grid.Row.
See the body and expandedField configs on the class to easily add extra content to grid rows.
Be aware that if you specify a row body, you must
configure the owning grid with variableHeights: true.
Defaults to:
{
xtype: 'gridrow'
}
Sets the value of itemConfig
itemConfig : Object / Ext.grid.Row
A class to add to the element that immediate wraps the item content produced
by the itemTpl (the "inner-html" element).
Defaults to:
null
Available since: 6.5.0
Sets the value of itemContentCls
itemContentCls : String
This object allows you to map Ext.data.Model fields to specific configs on component items.
The itemDataMap object's keys describe the target objects to receive data
from the associated record. These keys are either '#'
(for the item itself) or a reference to
a component contained in the item.
For each target listed in itemDataMap, the value is another map describing
the config name (in the key) and the data field name (as the value).
For example:
itemDataMap: {
'#': {
title: 'fullName'
},
text: {
html: 'name'
}
}
The above is equivalent to:
item.setTitle(item.getRecord().get('fullName'));
item.lookup('text').setHtml(item.getRecord().get('name'));
For more complex mapping of data to item, you should use the data binding as described in the class documentation.
Defaults to:
null
Available since: 6.5.0
An itemId can be used as an alternative way to get a reference to a component when no
object reference is available. Instead of using an id with Ext#getCmp,
use itemId with Ext.Container#getComponent which will retrieve itemId's or
id's. Since itemId's are an index to the container's internal MixedCollection,
the itemId is scoped locally to the container - avoiding potential conflicts with
Ext.ComponentManager which requires a unique id.
Also see id, Ext.Container#query, Ext.Container#down and Ext.Container#child.
Defaults to:
undefined
A class to add to the inner element of items.
Defaults to:
null
Available since: 6.5.0
Defaults to:
null
Available since: 6.5.0
color : String
The background color of the ripple. Default ripple Ext.Widget#ripple settings for each item in the data view
For complex items, individual elements can suppress ripples by adding the
x-no-ripple class to disable rippling for a tree of elements.
The child items to add to this Container. This is usually an array of Component configurations or instances, for example:
Ext.create({
xtype: 'container',
items: [{
xtype: 'panel',
html: 'This is an item'
}]
});
This may also be specified as an object, the property names of which are itemIds, and
the property values are child Component config objects, for example:
Ext.create({
xtype: 'tabpanel',
items: {
panel1: {
xtype: 'panel',
title: 'First panel'
},
panel2: {
xtype: 'panel',
title: 'Second panel'
}
}
});
Defaults to:
null
The tpl to use for each of the items displayed in this DataView. This template
produces HTML and can use the follow CSS class names to influence the response
to tapping/clicking child elements:
x-no-ripple - Disables itemRipple (primarily for theme-material)x-item-no-select - Disables item selectionx-item-no-tap - Disables all click or tap processingFor example:
itemTpl: '<div>' +
'...' +
'<div class="x-item-no-select x-fa fa-gear"></div>' +
'...' +
'</div>'
Because this template produces HTML from record data it can expose applications to security issues if user-provided data is not properly encoded. For example, in previous releases this template was:
itemTpl: '<div>{text}</div>'
If the 'text' field contained HTML scripts, these would be evaluated into
the application. The itemTpl in version 6.5 is now:
itemTpl: '<div>{text:htmlEncode}</div>'
Defaults to:
'<div>{text:htmlEncode}</div>'
Sets the value of itemTpl
itemTpl : String / String[] / Ext.XTemplate
An object containing handlers for keyboard events. The property names of this object are the key name and any modifiers. The values of the properties are the descriptors of how to handle each event.
The handler descriptor can be simply the handler function(either the literal function or the method name), or it can be an object with these properties:
handler: The function or its name to call to handle the event.scope: The this pointer context (can be "this" or "controller").event: An optional override of the key event to which to listen.Important: Calls to setKeyMap do not replace the entire keyMap but
instead update the provided mappings. That is, unless null is passed as the
value of the keyMap which will clear the keyMap of all entries.
Defaults to:
null
scope : String
The default scope to apply to key handlers
which do not specify a scope. This is processed the same way as the scope of
cfg-listeners. It defaults to the "controller", but using 'this'
means that an instance method will be used.
Enables or disables processing keys in the keyMap. This value starts as
null and if it is null when initKeyMap is called, it will automatically
be set to true. Since initKeyMap is called by Ext.Component at the
proper time, this is not something application code normally handles.
Defaults to:
null
The name of the member that should be used to listen for keydown/keypress events. This is intended to be controlled at the class level not per instance.
Defaults to:
'el'
Configuration for this Container's layout. Example:
Ext.create({
xtype: 'container',
layout: {
type: 'hbox',
align: 'middle'
},
items: [{
xtype: 'panel',
flex: 1,
bodyStyle: {
background: "#000",
color:"#fff"
}
}, {
xtype: 'panel',
flex: 2,
bodyStyle: {
background: "#f00",
color:"#fff"
}
}]
});
Defaults to:
'auto'
The absolute left position of this Component; must be a valid CSS length value,
e.g: 300, 100px, 30%, etc. Explicitly setting this value will make this Component
become 'positioned', which means it will no longer participate in the layout of the
Container that it resides in.
Defaults to:
null
A config object containing one or more event handlers to be added to this object during initialization. This should be a valid listeners config object as specified in the addListener example for attaching multiple handlers at once.
DOM events from Ext JS Ext.Component
While some Ext JS Component classes export selected DOM events (e.g. "click",
"mouseover" etc), this is usually only done when extra value can be added. For example
the DataView's itemclick
event passing the node clicked on. To access DOM events directly from a child element
of a Component, we need to specify the element option to identify the Component
property to add a DOM listener to:
new Ext.panel.Panel({
width: 400,
height: 200,
dockedItems: [{
xtype: 'toolbar'
}],
listeners: {
click: {
element: 'el', //bind to the underlying el property on the panel
fn: function(){ console.log('click el'); }
},
dblclick: {
element: 'body', //bind to the underlying body property on the panel
fn: function(){ console.log('dblclick body'); }
}
}
});
An alias for addListener. In versions prior to 5.1, listeners had a generated setter which could be called to add listeners. In 5.1 the listeners config is not processed using the config system and has no generated setter, so this method is provided for backward compatibility. The preferred way of adding listeners is to use the on method.
listeners : Object
The listeners
If specified, gives an explicit height for a floated data view when it is showing the loadingText, if that is specified. This is useful to prevent the view's height from collapsing to zero when the loading mask is applied and there are no other contents in the data view.
Defaults to:
null
A string to display during data load operations. This text will be displayed in a loading div and the view's contents will be cleared while loading, otherwise the view's contents will continue to display normally until the new data is loaded and the contents are replaced.
Note: For virtual stores, the load mask will be shown frequently as the user scrolls. To inhibit that, set loadingText to the empty string.
Defaults to:
'Loading...'
Set to true to maintain the order of rendered items in the DOM childNodes. In
an infinite list this is not normally done for performance reasons but this can
create accessibility issues.
Defaults to:
false
Available since: 6.5.0
true to enable border management of docked items. When enabled, borders of docked
items will collapse where they meet to avoid duplicated borders.
Defaults to:
false
The margin to use on this Component. Can be specified as a number (in which case all edges get the same margin) or a CSS string like '5 10 10 10'
Defaults to:
null
true to mark items as dirty when the underlying record has been modified.
By default there is no special styling for dirty items in data views and
Ext.dataview.List. When this config is set to true each item's
element will have a CSS class name of x-mark-dirty added to it. When the
underlying record for an item has been modified the item will have the x-dirty
CSS class.
Ext.grid.Grid style "dirty" cells using a red triangle icon in the corner of the cell. See $gridcell-dirty-icon
Defaults to:
false
Available since: 6.5.1
A configuration to allow you to mask this container.
If the value is a string, it will be used as the message config for an Ext.LoadMask.
For more precise control over the mask, you can optionally pass an object block with
and xtype of loadmask, and an optional message value to display a loading mask.
Please refer to the Ext.LoadMask component to see other configurations.
Ext.create({
xtype: 'container',
fullscreen: true,
html: 'Hello World',
masked: {
xtype: 'loadmask',
message: 'My Message'
}
});
Alternatively, you can just call the setter at any time with true/false to show/hide
the mask:
setMasked(true); //show the mask
setMasked(false); //hides the mask
There are also two convenient methods, method-mask and unmask, to allow you to mask and unmask this container at any time.
Remember, the Ext.Viewport is always a container, so if you want to mask your whole application at anytime, can call:
Ext.Viewport.setMasked({
xtype: 'loadmask',
message: 'Hello'
});
Defaults to:
null
The maximum height of this Component; must be a valid CSS length value,
e.g: 300, 100px, 30%, etc. If set to auto, it will set the width to null
meaning it will have its own natural size. Note that this config will not apply if the
Component is 'positioned' (absolutely positioned or centered)
Defaults to:
null
The number of components to cache when no longer needed (as opposed to calling
destroy on them).
Defaults to:
20
The maximum width of this Component; must be a valid CSS length value,
e.g: 300, 100px, 30%, etc. If set to auto, it will set the width to null
meaning it will have its own natural size. Note that this config will not apply if the
Component is 'positioned' (absolutely positioned or centered)
Defaults to:
null
The minimum height of this Component; must be a valid CSS length value,
e.g: 300, 100px, 30%, etc. If set to auto, it will set the width to null
meaning it will have its own natural size.
Defaults to:
null
The minimum number of items beyond the visible area of an infinite list to
allow before repositioning items on the opposite side to balance the visible
area inside the rendered range.
Defaults to:
5
Sets the value of minimumBufferDistance
minimumBufferDistance : Number
The minimum width of this Component; must be a valid CSS length value,
e.g: 300, 100px, 30%, etc. If set to auto, it will set the width to null
meaning it will have its own natural size.
Defaults to:
null
true to make this Component modal. This will create a mask underneath the
Component that covers its parent and does not allow the user to interact with
any other Components until this Component is dismissed.
Defaults to:
null
This config enables binding to your Ext.data.Model#validators. This
is only processed by form fields (e.g., Ext.field.*) at present, however, this
setting is inherited and so can be set on a parent container.
When set to true by a component (or by an ancestor container), the validators
of for any {@Ext.data.Model record} fields will be used wherever the value is
bound to such data fields.
While this config can be set arbitrarily high in the component hierarchy, doing
so can create a lot overhead if most of your form fields do not actually rely on
validators in your data model.
Using this setting for a form that is bound to an Ext.data.Model might look
like this:
{
xtype: 'panel',
modelValidation: true,
items: [{
xtype: 'textfield',
bind: '{theUser.firstName}'
},{
xtype: 'textfield',
bind: '{theUser.lastName}'
},{
xtype: 'textfield',
bind: '{theUser.phoneNumber}'
},{
xtype: 'textfield',
bind: '{theUser.email}'
}]
}
Defaults to:
null
Available since: 6.5.0
Configure as true to have columns retain their sorted state after other
columns have been clicked upon to sort.
As subsequent columns are clicked upon, they become the new primary sort key.
Clicking on an already sorted column which is not the primary sort key does not toggle its direction. Analogous to bringing a window to the top by clicking it, this makes that column's field the primary sort key. Subsequent clicks then toggle it.
Clicking on a primary key column toggles ASC -> DESC -> no sorter.
The column sorting menu items may be used to toggle the direction without affecting the sorter priority.
The maximum number of sorters allowed in a Store is configurable via its underlying data collection. See Ext.util.Collection#multiSortLimit
Defaults to:
false
Sets the value of multiColumnSort
multiColumnSort : Boolean
Set to true for this component's name property to be tracked by its containing
nameHolder.
Defaults to:
false
When true child components are tracked by their name property and can be
retrieved using the lookupName method.
Defaults to:
false
Set to true to display a disclosure icon on each list item. The list will
then fire the disclose event, and the event can be stopped before childtap.
By setting this config to a function, the function passed will be called when
the disclosure is tapped. This can be either a function object or the name of
a Ext.app.ViewController method.
Finally you can specify an object with a scope and handler property defined.
This will also be bound to the tap event listener and is useful when you want
to change the scope of the handler.
Defaults to:
null
Returns the value of onItemDisclosure
The padding to use on this Component. Can be specified as a number (in which case all edges get the same padding) or a CSS string like '5 10 10 10'
Defaults to:
null
Whether or not to pin headers on top of item groups
while scrolling. Only applicable for infinite lists.
Defaults to:
true
A config object for the pinned header. Only applicable when pinHeaders
and grouped are true.
Defaults to:
{
xtype: 'rowheader'
}
Defaults to:
null
Available since: 6.5.0
Sets the value of pinnedHeaderHeight
pinnedHeaderHeight : Object
This config describes one or more plugin config objects used to create plugin instances for this component.
Plugins are a way to bundle and reuse custom functionality. Plugins should extend
Ext.plugin.Abstract but technically the only requirement for a valid plugin
is that it contain an init method that accepts a reference to its owner. Once
a plugin is created, the owner will call the init method, passing a reference
to itself. Each plugin can then call methods or respond to events on its owner
as needed to provide its functionality.
This config's value can take several different forms.
The value can be a single string with the plugin's Ext.enums.Plugin:
var list = Ext.create({
xtype: 'list',
itemTpl: '<div class="item">{title}</div>',
store: 'Items',
plugins: 'listpaging'
});
In the above examples, the string "listpaging" is the type alias for
Ext.dataview.plugin.ListPaging. The full alias includes the "plugin." prefix
(i.e., 'plugin.listpaging').
The preferred form for multiple plugins or to configure plugins is the keyed-object form (new in version 6.5):
var list = Ext.create({
xtype: 'list',
itemTpl: '<div class="item">{title}</div>',
store: 'Items',
plugins: {
pullrefresh: true,
listpaging: {
autoPaging: true,
weight: 10
}
}
});
The object keys are the id's as well as the default type alias. This form
allows the value of the plugins to be merged from base class to derived class
and finally with the instance configuration. This allows classes to define a
set of plugins that derived classes or instantiators can further configure or
disable. This merge behavior is a feature of the
config.
The plugins config can also be an array of plugin aliases (arrays are not
merged so this form does not respect plugins defined by the class author):
var list = Ext.create({
xtype: 'list',
itemTpl: '<div class="item">{title}</div>',
store: 'Items',
plugins: ['listpaging', 'pullrefresh']
});
An array can also contain elements that are config objects with a type
property holding the type alias:
var list = Ext.create({
xtype: 'list',
itemTpl: '<div class="item">{title}</div>',
store: 'Items',
plugins: ['pullrefresh', {
type: 'listpaging',
autoPaging: true
}]
});
Defaults to:
null
Returns the value of plugins
Sets the value of plugins
plugins : Array / Ext.enums.Plugin / Object / Ext.plugin.Abstract
The amount of delay between the tapstart and adding the pressedCls.
Defaults to:
100
When true item selection is prevented when the user taps a disclose icon.
Defaults to:
true
Sets the value of preventSelectionOnDisclose
preventSelectionOnDisclose : Boolean
When true item selection is prevented when the user taps on a tool. This
can be overridden on specific tools by placing the preventSelection property
on the tool:
tools: [{
type: 'gear',
preventSelection: false
}]
Defaults to:
true
Available since: 6.5.0
Sets the value of preventSelectionOnTool
preventSelectionOnTool : Boolean
One or more names of config properties that this component should publish to its ViewModel. Generally speaking, only properties defined in a class config block (including ancestor config blocks and mixins) are eligible for publishing to the viewModel. Some components override this and publish their most useful configs by default.
Note: We'll discuss publishing properties not found in the config block below.
Values determined to be invalid by component (often form fields and model validations) will not be published to the ViewModel.
This config uses the cfg-reference to determine the name of the data
object to place in the ViewModel. If reference is not set then this config
is ignored.
By using this config and cfg-reference you can bind configs between
components. For example:
...
items: [{
xtype: 'textfield',
reference: 'somefield', // component's name in the ViewModel
publishes: 'value' // value is not published by default
},{
...
},{
xtype: 'displayfield',
bind: 'You have entered "{somefield.value}"'
}]
...
Classes must provide this config as an Object:
Ext.define('App.foo.Bar', {
publishes: {
foo: true,
bar: true
}
});
This is required for the config system to properly merge values from derived classes.
For instances this value can be specified as a value as show above or an array or object as follows:
{
xtype: 'textfield',
reference: 'somefield',
publishes: [
'value',
'rawValue',
'dirty'
]
}
// This achieves the same result as the above array form.
{
xtype: 'textfield',
reference: 'somefield',
publishes: {
value: true,
rawValue: true,
dirty: true
}
}
In some cases, users may want to publish a property to the viewModel that is not found in a class config block. In these situations, you may utilize publishState if the property has a setter method. Let's use setFieldLabel as an example:
setFieldLabel: function(fieldLabel) {
this.callParent(arguments);
this.publishState('fieldLabel', fieldLabel);
}
With the above chunk of code, fieldLabel may now be published to the viewModel.
Defaults to:
{
selection: 1
}
A model instance which updates the Component's html based on it's tpl. Similar to the data configuration, but tied to to a record to make allow dynamic updates. This must be a model instance and not a configuration of one.
Defaults to:
null
Specifies a name for this component inside its component hierarchy. This name must be unique within its view or its Ext.app.ViewController. See the documentation in Ext.container.Container for more information about references.
Note: Valid identifiers start with a letter or underscore and are followed by zero or more additional letters, underscores or digits. References are case sensitive.
Defaults to:
null
If true, this container will be marked as being a point in the hierarchy where
references to items with a specified reference config will be held. The container
will automatically become a referenceHolder if a controller is specified.
See the introductory docs for Ext.container.Container for more information about references & reference holders.
Defaults to:
false
Only valid when a component is cfg-floated
Configure this as true if you require descendant floated components to be positioned
relative to this component's coordinate space, not the viewport's coordinate space.
Note: The coordinate space is this Component's encapsulating element's area. Not that of the inner element in which static child items are rendered by the layout.
Defaults to:
false
Available since: 6.2.0
Optional element to render this Component to. Not required if this component is an item of a Container of a Container.
Defaults to:
null
only meaningful on platforms which has space-consuming scroll bars
Configure as true to leave space for a scrollbar to appear even if the
content does not overflow.
This is useful for trees which may expand and collapse causing visual flickering when scrollbars appear or disappear.
Defaults to:
false
When true, FocusableContainer
will reset last focused position whenever focus leaves the container.
Subsequent tabbing into the container will always focus the first eligible
child item.
When false, subsequent tabbing into the container will focus the child
item that was last focused before.
Defaults to:
false
The absolute right position of this Component; must be a valid CSS length value,
e.g: 300, 100px, 30%, etc. Explicitly setting this value will make this Component
become 'positioned', which means it will no longer participate in the layout of the
Container that it resides in.
Defaults to:
null
Set to truthy, Color or Object value for the ripple.
Defaults to:
null
Available since: 6.5.0
color : String
The background color of the ripple.
position : Array
Position for the ripple to start at [x,y]. Determines if a Ripple effect should happen whenever this element is pressed.
For example: { ripple: true }
Or:
{
ripple: {
color: 'red'
}
}
For complex components, individual elements can suppress ripples by adding the
x-no-ripple class to disable rippling for a tree of elements.
Set this to false to suppress the borders in between the items in this list.
By default the presence of borders between items is determined by the stylesheet.
Defaults to:
true
Configure as true to a Ext.grid.column.RowNumberer
column which gravitates to the start of the grid.
May be a Ext.grid.column.RowNumberer configuration object. For instance to set the column title use:
rowNumbers: {
text: 'Index'
}
Defaults to:
false
Configuration options to make this Component scrollable. Acceptable values are:
true to enable auto scrolling.false (or null) to disable scrolling - this is the default.x or horizontal to enable horizontal scrolling onlyy or vertical to enable vertical scrolling onlyAlso accepts a configuration object for a Ext.scroll.Scroller if
if advanced configuration is needed.
The getter for this config returns the Ext.scroll.Scroller instance. You can use the Scroller API to read or manipulate the scroll position:
// scrolls the component to 5 on the x axis and 10 on the y axis
component.getScrollable().scrollTo(5, 10);
Defaults to:
true
This property is placed on the child items added to this container. The value placed on the child items determines the position of that item with respect to the data items.
Ext.Viewport.add({
xtype: 'dataview',
itemTpl: '{firstName}',
data: [
{ firstName: 'Peter'},
{ firstName: 'Raymond'},
{ firstName: 'Egon'},
{ firstName: 'Winston'}
],
items: [{
xtype: 'component',
html: 'Always At End!',
scrollDock: 'end'
}]
});
Note, a value of 'top' is equivalent to 'start' while 'bottom' is
equivalent to 'end'. The 'top' and 'bottom' values originated from the
Ext.dataview.List class.
Scroll the DataView to the top when the DataView is refreshed.
Defaults to:
false
Sets the value of scrollToTopOnRefresh
scrollToTopOnRefresh : Boolean
A configuration object which allows passing of configuration options to create or reconfigure a Ext.grid.selection.Model.
The following options control what can be selected:
These options control how selections can be made:
Sets the value of selectable
selectable : Ext.grid.selection.Model
The selected record.
Returns the grid's selection if mode is single
returns selected record if selectable is rows
If provided this creates a new Session instance for this component. If this
is a Container, this will then be inherited by all child components.
To create a new session you can specify true:
Ext.create({
xtype: 'viewport',
session: true,
items: [{
...
}]
});
Alternatively, a config object can be provided:
Ext.create({
xtype: 'viewport',
session: {
...
},
items: [{
...
}]
});
Defaults to:
null
Sets the value of session
session : Boolean / Object / Ext.data.Session
Configure as true for the component to have a drop shadow. 'false' will suppress any
default shadow. By default the theme will determine the presence of a shadow.
Defaults to:
null
Available since: 6.2.0
Only valid when a component is cfg-floated
Configure as true for the component to use an <iframe> as an underlay to ensure
certain non-standard browser plugins are occluded by this component.
Defaults to:
false
Available since: 6.2.0
Animation effect to apply when the Component is being shown. Typically you want to use an inbound animation type such as 'fadeIn' or 'slideIn'. For more animations, check the Ext.fx.Animation#type config.
Defaults to:
null
Sets the value of showAnimation
showAnimation : String / Mixed
Configure as false to disable column sorting via clicking the header and via
the Sorting menu items.
Defaults to:
true
This config specifies the config properties that will be persisted using the
Ext.state.Provider. If this config is set to true, the
configs specified by statefulDefaults will be assumed.
stateful: true
Otherwise, this config can be an array of strings of the properties to save:
stateful: [
'width',
'height',
'collapsed'
]
The above is equivalent to:
stateful: {
width: true,
height: true,
collapsed: true
}
Note: To be truly stateful, an id or stateId must also be assigned.
A stateful object will save its state when any of these config properties change value.
Defaults to:
false
The default set of stateful properties. The form of this config is the same as stateful except this config cannot be a Boolean.
This config is intended for classes to specify so that instances can simply
enable statefulness using stateful: true.
Defaults to:
null
The unique id for this object to use for state management purposes.
Defaults to:
null
Set this to true if you want the items in this DataView to be zebra striped.
alternating their background color.
Only applicable if the stylesheet provides styling for alternate items.
By default the stylesheet does not provide styling for DataView items, but it
can be enabled by setting the ui to 'basic'.
Lists and Grids provide default styling for striped items
Defaults to:
true
Additional CSS styles that will be rendered into an inline style attribute when the widget is rendered.
You can pass either a string syntax:
style: 'background:red'
Or by using an object:
style: {
background: 'red'
}
When using the object syntax, you can define CSS Properties by using a string:
style: {
'border-left': '1px solid red'
}
Although the object syntax is much easier to read, we suggest you to use the string syntax for better performance.
Defaults to:
null
DOM tabIndex attribute for this component's focusEl.
Defaults to:
0
Return the actual tabIndex for this Focusable.
tabIndex attribute value
Set the tabIndex property for this Focusable. If the focusEl is available, set tabIndex attribute on it, too.
newTabIndex : Number
new tabIndex to set
The title that will be displayed in the TitleBar at the top of this Grid.
Defaults to:
''
True to automatically call toFront when a cfg-floated Component is shown.
Defaults to:
true
The tooltip for this component - can be a string to be used as innerHTML (html tags are accepted) or Ext.tip.ToolTip config object.
The default behavior is to use a shared tip instance. The tooltip configuration is registered with the Ext.tip.Manager. To enable this, your application can set the Ext.app.Application#quickTips config, or an instance of the Ext.tip.Manager may be created manually.
To force a unique tooltip instance to be created, specify autoCreate: true on this
configuration.
Configuring this with autoHide: false implies autoCreate: true so that the desired
persistent behavior can be obtained with other targets still showing the singleton
instance.
Defaults to:
null
The absolute top position of this Component; must be a valid CSS length value,
e.g: 300, 100px, 30%, etc. Explicitly setting this value will make this Component
become 'positioned', which means it will no longer participate in the layout of the
Container that it resides in.
Defaults to:
null
Defaults to:
null
Available since: 6.5.0
Sets the value of topRenderedIndex
topRenderedIndex : Object
Emulates the behavior of the CSS touch-action property in a cross-browser compatible manner.
Keys in this object are touch action names, and values are false to disable
a touch action or true to enable it. Accepted keys are:
panXpanYpinchZoomdoubleTapZoomAll touch actions are enabled (true) by default, so it is usually only necessary
to specify which touch actions to disable. For example, the following disables
only horizontal scrolling and pinch-to-zoom on the component's main element:
touchAction: {
panX: false,
pinchZoom: false
}
Touch actions can be specified on reference elements using the reference element name, for example:
// disables horizontal scrolling on the main element, and double-tap-zoom
// on the child element named "body"
touchAction: {
panY: false
body: {
doubleTapZoom: false
}
}
The primary motivation for setting the touch-action of an element is to prevent the browser's default handling of a gesture such as pinch-to-zoom, or drag-to-scroll, so that the application can implement its own handling of that gesture on the element. Suppose, for example, a component has a custom drag handler on its element and wishes to prevent horizontal scrolling of its container while it is being dragged:
Ext.create('Ext.Widget', {
touchAction: {
panX: false
},
listeners: {
drag: function(e) {
// implement drag logic
}
}
});
Defaults to:
null
A String, Ext.Template, Ext.XTemplate or an Array of strings to form an Ext.XTemplate. Used in conjunction with the data and tplWriteMode configurations.
Note The data configuration must be set for any content to be shown in the component when using this configuration.
Defaults to:
null
Sets the value of tpl
tpl : String / String[] / Ext.Template / Ext.XTemplate[]
The Ext.(X)Template method to use when updating the content area of the Component.
Valid modes are:
Defaults to:
'overwrite'
Determines what type of touch event is recognized as a touch on the container.
Defaults to:
'tap'
Returns the value of triggerCtEvent
'tap' / 'singletap'
Sets the value of triggerCtEvent
triggerCtEvent : 'tap' / 'singletap'
Determines what type of touch event causes an item to be selected.
Defaults to:
'childtap'
Returns the value of triggerEvent
'childtap' / 'childsingletap' / 'childdoubletap' / 'childswipe' / 'childtaphold' / 'childlongpress'
Sets the value of triggerEvent
triggerEvent : 'childtap' / 'childsingletap' / 'childdoubletap' / 'childswipe' / 'childtaphold' / 'childlongpress'
This object holds a map of config properties that will update their binding
as they are modified. For example, value is a key added by form fields. The
form of this config is the same as publishes.
This config is defined so that updaters are not created and added for all bound properties since most cannot be modified by the end-user and hence are not appropriate for two-way binding.
Defaults to:
{
selection: 1
}
The ui or uis to be used on this Component
When a ui is configured, CSS class names are added to the element, created by appending the ui name(s) to each classCls and/or baseCls.
Defaults to:
null
One or more CSS classes to add to the component's primary element. This config is intended solely for use by the component instantiator (the "user"), not by derived classes.
For example:
items: [{
xtype: 'button',
userCls: 'my-button'
...
}]
Defaults to:
null
Set to true to allow users to select text within this component.
Can also be any valid value for the CSS3 user-select property.
A value of true implies auto, while false implies none.
May also be an object keyed by child element name.
By default, the user cannot click+drag+select text/elements of the UI. Applications may want to enable user selection for specific DOM elements, such as the bodyElement of a component used as a tab panel. The tab and tab text would not be user selectable in this example, but the content area when the tab is selected would.
userSelectable: {
element: true, // allow the element to be user selectable
bodyElement: true // allow the component's body element to be user selectable
}
Defaults to:
false
Available since: 6.5.1
Setting this to false changes the xtype of the itemConfig to the more
flexible Ext.dataview.ListItem instead of the more efficient
setting of Ext.dataview.SimpleListItem.
Defaults to:
true
Deprecated since version 6.5.0
Set the xtype of itemConfig instead.
Sets the value of useSimpleItems
useSimpleItems : Boolean
Set to true if the items in this list do not all have the same height. This
is false by default to avoid measure each row to determine its height.
Defaults to:
false
Available since: 6.5.0
Sets the value of variableHeights
variableHeights : Boolean
This config is set to true when an infinite list has vertical overflow.
Defaults to:
null
Available since: 6.5.0
Sets the value of verticalOverflow
verticalOverflow : Boolean
The ViewModel is a data provider for this component and its children. The
data contained in the ViewModel is typically used by adding bind configs
to the components that want present or edit this data.
When set, the ViewModel is created and links to any inherited viewModel
instance from an ancestor container as the "parent". The ViewModel hierarchy,
once established, only supports creation or destruction of children. The
parent of a ViewModel cannot be changed on the fly.
If this is a root-level ViewModel, the data model connection is made to this
component's associated Ext.data.Session. This is
determined by calling getInheritedSession.
Defaults to:
null
Sets the value of viewModel
viewModel : String / Object / Ext.app.ViewModel
The height of the container in pixels. This is a config to simplify processing changes in container height.
Defaults to:
null
Available since: 6.5.0
The top-most visible pixel coordinate. This is the same as the y value of
the Scroller but is a config to simplify processing scrolling changes.
Defaults to:
null
Available since: 6.5.0
This value controls this item's order in a weighted Ext.Container (see parent).
Lower values gravitate towards the start of the container - the top in vertical layouts, the locale start side in horizontal layouts.
Defaults to:
0
If set to true, then child items may be specified as a object,
with each property name specifying an itemId, and the property
value being the child item configuration object.
When using this scheme, each child item may contain a weight configuration value which affects its order in this container. Lower weights are towards the start, higher weights towards the end.
Defaults to:
false
The width of this Component; must be a valid CSS length value, e.g: 300, 100px,
30%, etc. By default, if this is not explicitly set, this Component's element will
simply have its own natural size. If set to auto, it will set the width to null
meaning it will have its own natural size.
Defaults to:
null
Only valid when a component is cfg-floated
The x position at which to position this component. This is usually viewport-relative.
But if there is a relative: true ancestor, it will be relative to that.
Defaults to:
0
The xtype configuration option can be used to optimize Component creation and rendering.
It serves as a shortcut to the full component name. For example, the component
Ext.button.Button has an xtype of button.
You can define your own xtype on a custom Ext.Component like so:
Ext.define('PressMeButton', {
extend: 'Ext.button.Button',
xtype: 'pressmebutton',
text: 'Press Me'
});
Any Component can be created implicitly as an object config with an xtype specified, allowing it to be declared and passed into the rendering pipeline without actually being instantiated as an object. Not only is rendering deferred, but the actual creation of the object itself is also deferred, saving memory and resources until they are actually needed. In complex, nested layouts containing many Components, this can make a noticeable improvement in performance.
// Explicit creation of contained Components:
var panel = new Ext.Panel({
// ...
items: [
Ext.create('Ext.button.Button', {
text: 'OK'
})
]
});
// Implicit creation using xtype:
var panel = new Ext.Panel({
// ...
items: [{
xtype: 'button',
text: 'OK'
}]
});
In the first example, the button will always be created immediately during the panel's initialization. With many added Components, this approach could potentially slow the rendering of the page. In the second example, the button will not be created or rendered until the panel is actually displayed in the browser. If the panel is never displayed (for example, if it is a tab that remains hidden) then the button will never be created and will never consume any resources whatsoever.
Only valid when a component is cfg-floated
The x position at which to position this component. This is usually viewport-relative.
But if there is a relative: true ancestor, it will be relative to that.
Defaults to:
0
The z-index to give this Component when it is rendered.
Not valid for cfg-floated Components. The Z ordering of cfg-floated Components is managed by ordering of the DOM elements.
Defaults to:
null
The value true causes config values to be stored on instances using a
property name prefixed with an underscore ("_") character. A value of false
stores config values as properties using their exact name (no prefix).
Defaults to:
true
Available since: 5.0.0
The value true instructs the initConfig method to only honor values for
properties declared in the config block of a class. When false, properties
that are not declared in a config block will be placed on the instance.
Defaults to:
true
Available since: 5.0.0
A prototype-chained object storing transform method names and priorities stored on the class prototype. On first instantiation, this object is converted into an array that is sorted by priority and stored on the constructor.
Defaults to:
{}
Matches options property names within a listeners specification object - property names which are never used as event names.
Defaults to:
{
scope: 1,
delay: 1,
buffer: 1,
onFrame: 1,
single: 1,
args: 1,
destroyable: 1,
priority: 1,
order: 1
}
We don't want the base destructor to clear the prototype because our destroyObservable handler must be called the very last. It will take care of the prototype after completing Observable destruction sequence.
Defaults to:
true
The name of the Component property that holds a reference to the Element that serves as that Component's ARIA element. This property will be replaced with the actual Element reference after rendering.
Most of the simple Components will have their main element as ariaEl.
Defaults to:
'el'
Available since: 6.0.0
Instance specific ARIA attributes to render into Component's ariaEl. This object is only used during rendering, and is discarded afterwards.
ARIA role for this Component, defaults to no role. With no role, no other ARIA attributes are set.
true indicates an id was auto-generated rather than provided by configuration.
Defaults to:
false
Available since: 6.7.0
The base CSS class to apply to this widget's element.
Used as the prefix for ui-specific class names.
Defaults to the value of classCls or (x- + the xtype) of the widget
if classCls is null
Defaults to:
null
A CSS class to apply to the main element that will be inherited down the class hierarchy. Subclasses may override this property on their prototype to add their own CSS class in addition to the CSS classes inherited from ancestor classes via the prototype chain. For example
Ext.define('Foo', {
extend: 'Ext.Widget',
classCls: 'foo'
});
Ext.define('Bar', {
extend: 'Foo',
classCls: 'bar'
});
var bar = new Bar();
console.log(bar.element.className); // outputs 'foo bar'
Defaults to:
Ext.baseCSSPrefix + 'grid'
When set to true during widget class definition, that class will be the "root" for
classCls inheritance. Derived classes may set this to true to avoid
inheriting a classCls from their superclass.
Defaults to:
true
Setting this property to false will prevent nulling object references
on a Class instance after destruction. Setting this to "async" will delay
the clearing for approx 50ms.
Defaults to:
true
Available since: 6.2.0
Setting this property to true will result in setting the object's
prototype to null after the destruction sequence is fully completed.
After that, most attempts at calling methods on the object instance
will result in "method not defined" exception. This can be very helpful
with tracking down otherwise hard to find bugs like runaway Ajax requests,
timed functions not cleared on destruction, etc.
Note that this option can only work in browsers that support Object.setPrototypeOf
method, and is only available in debugging mode.
Defaults to:
false
Available since: 6.2.0
true if this currently focused element
is within this Component's or Container's hierarchy. This property is set separately
from hasFocus, and can be true when hasFocus is false.
Examples:
Text field with input element focused would be: focusable: true, hasFocus: true, containsFocus: true
Date field with drop-down picker currently focused would be: focusable: true, hasFocus: false, containsFocus: true
Form Panel with a child input field currently focused would be: focusable: false, hasFocus: false, containsFocus: true
See also hasFocus.
Defaults to:
false
The array of data items. This array is maintained in store order. The type of objects in this array depend on the type of this dataview. Further, infinite lists only put the actually rendered portion of the store in this array.
NOTE: This is not the same thing as the items maintained by this Container
since there could be items in the container that are not associated to any
record in the store.
Defaults to:
[]
This property is used to determine the property of a bind config that is just
the value. For example, if defaultBindProperty="value", then this shorthand
bind config:
bind: '{name}'
Is equivalent to this object form:
bind: {
value: '{name}'
}
The defaultBindProperty is set to "value" for form fields and to "store" for
grids and trees.
Defaults to:
'store'
This property is set to true after the destroy method is called.
Defaults to:
false
A configuration object for Ext.Element.create() that is used to create the Element template. Subclasses should avoid overriding this property and instead add elements using template.
Supports all the standard options of a Ext.Element.create() config and adds 3 additional options:
reference - this option specifies a name for Element references. These
references names become properties of the Widget instance and refer to Ext.Element
instances that were created using the template:
element: {
reference: 'element',
children: [{
reference: 'innerElement'
}]
}
After construction of a widget the reference elements are accessible as follows:
var foo = new FooWidget(),
innerEl = foo.innerElement; // an Ext.Element that wraps the innerElement
The reference attribute is optional, but all Widgets must have a 'element'
reference on some element within the template (usually the outermost one).
listeners - a standard listeners object as specified by Ext.mixin.Observable.
element: {
reference: 'element',
listeners: {
click: 'onClick'
},
children: [{
reference: 'innerElement',
listeners: {
click: 'onInnerClick'
}
}]
}
Since listeners cannot be attached without an Ext.Element reference the reference
property MUST be specified in order to use listeners.
The Widget instance is used as the scope for all listeners specified in this way,
so it is invalid to use the scope option in the listeners config since it will
always be overwritten using this.
uiCls - a suffix to be appended to the ui-specific CSS class for each ui
for this widget. These ui classes are constructed by appending the ui to each
classCls or baseCls for the widget. As such, uiCls should
never be used on the main element reference, as its uiCls is computed automatically.For example, assume a widget is defined with a ui of 'alt action' and a
uiCls of 'inner-el' on its innerElement reference element:
Ext.define('Doodad', {
extend: 'Ext.Widget',
xtype: 'doodad',
classCls: 'x-doodad',
ui: 'alt action',
element: {
reference: 'element',
children: [{
reference: 'innerElement',
cls: 'x-inner-el',
uiCls: 'inner-el'
}]
}
});
This would result in the following markup when rendered:
<div class="x-doodad x-doodad-alt x-doodad-action">
<div class="x-inner-el x-doodad-inner-el x-doodad-alt-inner-el x-doodad-action-inner-el"></div>
</div>
These additional classes can be used to style the reference element for a particular
ui; however, use of uiCls is not typically necessary or recommended. Reference
elements should usually be styled using simple descendant selectors:
.x-doodad-alt .x-inner-el {
color: red;
}
When there is a possibility that widgets can be nested it is best to use direct child selectors to avoid the possibility of selecting all descendants instead of just the reference element for the intended widget:
.x-doodad-alt > .x-inner-el {
color: red;
}
Only use uiCls when there is a possibility of nesting, AND there may be a variable
number of elements between the main element and the reference element in question.
For example, Ext.Container with docked items has a different number of elements
in between its element and its bodyElement than a Container without docked items
because of the wrapping elements that are dynamically added to support docking.
To ensure it does not style all descendants it must use a uiCls to style its
bodyElement:
.x-container-alt-body-el {
background: #fff;
}
Note that when uiCls is specified it also adds a class name that does not contain
the ui using just the classCls and/or baseCls as the prefix. This class name
can be used for base-level styling that does not relate to any particular UI:
.x-container-body-el {
position: relative;
}
Defaults to:
{
reference: 'element'
}
Initial suspended call count. Incremented when suspendEvents is called, decremented when resumeEvents is called.
Defaults to:
0
If this property is specified by the target class of this mixin its properties are
used to configure the created Ext.Factory.
The CSS class to add to this component when it is floated at the viewport level.
Defaults to:
Ext.baseCSSPrefix + 'floating'
The CSS class to add to this component's floatWrap when it's created.
Defaults to:
"x-float-wrap"
true for keyboard interactive Components or Widgets, false otherwise.
For Containers, this property reflects interactiveness of the
Container itself, not its children. See isFocusable.
Note: It is not enough to set this property to true to make
a component keyboard interactive. You also need to make sure that
the component's focusEl is reachable via Tab key (tabbable).
See also tabIndex.
Defaults to:
true
The name of the element that FocusableContainer should bind its keyboard handler to. Similar to ariaEl, this name is resolved to the Ext.dom.Element instance after rendering.
Defaults to:
"el"
The element that will have the focusCls applied when component's focusEl is focused.
The element that will be focused when focus method is called on this component. Usually this is the same element that receives focus via mouse clicks, taps, and pressing Tab key.
Defaults to:
'el'
true if this component's focusEl is focused.
See also containsFocus.
Defaults to:
false
This object holds a key for any event that has a listener. The listener may be set directly on the instance, or on its class or a super class (via observe) or on the Ext.app.EventBus. The values of this object are truthy (a non-zero number) and falsy (0 or undefined). They do not represent an exact count of listeners. The value for an event is truthy if the event must be fired and is falsy if there is no need to fire the event.
The intended use of this property is to avoid the expense of fireEvent calls when there are no listeners. This can be particularly helpful when one would otherwise have to call fireEvent hundreds or thousands of times. It is used like this:
if (this.hasListeners.foo) {
this.fireEvent('foo', this, arg1);
}
Set to true on widgets that should inherit ui from their parent container.
This property is typically set on the class body, but can be set on an instance as long
as it is set prior to the instance being added to its container. This property is
inspected at the moment a widget is added to a container, and any UIs on the container
are added to the widget at that time. Inherited UIs are in addition to the widget's
own ui, and are updated when the container's UI changes.
Defaults to:
false
Template method to do any Focusable related initialization that does not involve event listeners creation.
Defaults to:
Ext.emptyFn
This property is set to true during the call to initConfig.
Defaults to:
false
Available since: 5.0.0
true in this class to identify an object as an instantiated Container, or subclass thereof.
Defaults to:
true
true in this class to identify an object this type, or subclass thereof.
Defaults to:
true
This property is set to true if this instance is the first of its class.
Defaults to:
false
Available since: 5.0.0
This value is true and is used to identify plain objects from instances of
a defined class.
Defaults to:
true
true in this class to identify an object as an instantiated Observable, or subclass
thereof.
Defaults to:
true
The array of component items previously created for this view but not in
current use. This array will contain no more then maxItemCache items.
Defaults to:
{
max: 0,
unused: []
}
The last key event processed is cached on the component for use in subsequent event handlers.
Available since: 6.6.0
The CSS class to add to this component should not have a border.
Defaults to:
Ext.baseCSSPrefix + 'noborder-trbl'
The rendered flag is set when a widget is inserted into the document for the first time.
Note that this is a one-way operation. The first time a widget is inserted into the document, this flag is set, and it is never unset.
This object tracks coordinate and index information for the rendered
range of records for an infinite list.
Defaults to:
{
//
// : ... : indexTop ( = 100)
// : :
// +---------------+ <-- top (approx indexTop * rowHeight)
// | item 100 | \
// +---------------+ \
// | item 101 | > height
// +---------------+ /
// | item 102 | /
// +---------------+ <-- bottom ( = top + height)
// : :
// : ... : count - indexBottom ( = 103)
//
atBegin: false,
atEnd: false,
bottom: 0,
height: 0,
top: 0,
indexBottom: 0,
indexTop: 0
}
atBegin : Number
Set to true if the rendered range
is at the beginning of the store (indexTop is 0).
atEnd : Number
Set to true if the rendered range
is at the end of the store (indexBottom === store.getCount()).
top : Number
The y coordinate of the top-most
row in the rendered range.
bottom : Number
The y coordinate just beyond
the bottom of the rendered range.
height : Number
The height of the rendered range.
indexTop : Number
The store index of the top-most record in the rendered range.
indexBottom : Number
The store index one beyond
the last record in the rendered range. This ensures that subtracting
indexBottom - indexTop is the number of records in the rendered range.
By default, using the TAB key to reenter a grid restores focus to the cell which was last focused.
Setting this to false means that TAB from above focuses the first rendered
cell and TAB from below focuses the last rendered cell.
Be aware that due to buffered rendering, the last row of a 1,000,000 row grid may not be available to receive immediate focus.
Defaults to:
true
The height of rows in the list. If variableHeights is true this is the minimum
row height.
Defaults to:
0
The selection model type to create. Defaults to 'grid' for grids.
Defaults to:
grid
Get the reference to the current class from which this object was instantiated. Unlike
Ext.Base#statics, this.self is scope-dependent and it's meant to be used
for dynamic inheritance. See Ext.Base#statics for a detailed comparison
Ext.define('My.Cat', {
statics: {
speciesName: 'Cat' // My.Cat.speciesName = 'Cat'
},
constructor: function() {
alert(this.self.speciesName); // dependent on 'this'
},
clone: function() {
return new this.self();
}
});
Ext.define('My.SnowLeopard', {
extend: 'My.Cat',
statics: {
speciesName: 'Snow Leopard' // My.SnowLeopard.speciesName = 'Snow Leopard'
}
});
var cat = new My.Cat(); // alerts 'Cat'
var snowLeopard = new My.SnowLeopard(); // alerts 'Snow Leopard'
var clone = snowLeopard.clone();
alert(Ext.getClassName(clone)); // alerts 'My.SnowLeopard'
Defaults to:
Base
The CSS class to add to this component when it has a shadow.
Defaults to:
Ext.baseCSSPrefix + 'shadow'
The CSS class to add to this component's shim element if enabled.
Defaults to:
"x-shim"
An array of child elements to use as the children of the main element in the element template. Only used if "children" are not specified explicitly in the element template.
Defaults to:
[
{
reference: 'bodyElement',
cls: Ext.baseCSSPrefix + 'body-el',
uiCls: 'body-el',
children: [
{
// This el is width:100% and flex:1 (for full height)
reference: 'outerCt',
className: Ext.baseCSSPrefix + 'list-outer-ct',
children: [
{
// This el is just width:100% or explicitly sized of hscroll
reference: 'innerCt',
className: Ext.baseCSSPrefix + 'list-inner-ct'
}
]
}
]
}
]
A map that tracks all reference elements configured with a uiCls.
Contains the element reference by default since the element always gets
non-suffixed ui-specific CSS class names added to it (see syncUiCls)
Defaults to:
{
"true": Ext.baseCSSPrefix + 'user-selectable-auto',
"false": Ext.baseCSSPrefix + 'user-selectable-none',
all: Ext.baseCSSPrefix + 'user-selectable-all',
auto: Ext.baseCSSPrefix + 'user-selectable-auto',
text: Ext.baseCSSPrefix + 'user-selectable-text',
none: Ext.baseCSSPrefix + 'user-selectable-none'
}
Regular expression used for validating reference values.
Defaults to:
/^[a-z_][a-z0-9_]*$/i
Adds declarative listeners as nested arrays of listener objects.
listeners : Array
true if any listeners were added
This method is called before destroy to ensure that this instance's stateful
properties are saved to persistent storage. Since this object is about to be
destroyed, this cannot be delayed.
Creates a particular plugin type if defined in the plugins configuration.
Available since: 6.2.0
type : String
The type of the plugin.
The plugin that was created.
Adds one or more Components to this Container. Example:
var myPanel = Ext.create({
xtype: 'panel',
html : 'This will be added to a Container'
});
var items = myContainer.add([myPanel]); // Array returned
var item = myContainer.add(myPanel); // One item is returned
newItems : Object/Object[]/Ext.Component/Ext.Component[]
The new item(s) to add to the Container. Note that if an array of items to add was passed in, an array of added items will be returned as well even if there was only one item.
The Component(s) that were added.
Adds a CSS class (or classes) to this Component's rendered element.
cls : String/String[]
The CSS class(es) to add.
prefix : String (optional)
Optional prefix to add to each class.
Defaults to: ""
suffix : String (optional)
Optional suffix to add to each class.
Defaults to: ""
Adds a listeners with the "delegate" event option. Users should not invoke this method directly. Use the "delegate" event option of addListener instead.
eventName : Object
fn : Object
scope : Object
options : Object
order : Object
caller : Object
manager : Object
This method applies a versioned, deprecation declaration to this class. This
is typically called by the deprecated config.
deprecations : Object
Adds an element reference to this Widget instance.
name : String
The name of the reference
domNode : HTMLElement
Reduces instantiation time for a Widget by lazily instantiating Ext.Element references the first time they are used. This optimization only works for elements with no listeners specified.
name : String
The name of the reference
domNode : HTMLElement
The on method is shorthand for addListener.
Appends an event handler to this object. For example:
myGridPanel.on("itemclick", this.onItemClick, this);
The method also allows for a single argument to be passed which is a config object containing properties which specify multiple events. For example:
myGridPanel.on({
cellclick: this.onCellClick,
select: this.onSelect,
viewready: this.onViewReady,
scope: this // Important. Ensure "this" is correct during handler execution
});
One can also specify options for each event handler separately:
myGridPanel.on({
cellclick: {fn: this.onCellClick, scope: this, single: true},
viewready: {fn: panel.onViewReady, scope: panel}
});
Names of methods in a specified scope may also be used:
myGridPanel.on({
cellclick: {fn: 'onCellClick', scope: this, single: true},
viewready: {fn: 'onViewReady', scope: panel}
});
eventName : String/Object
The name of the event to listen for. May also be an object who's property names are event names.
fn : Function/String (optional)
The method the event invokes or the name of
the method within the specified scope. Will be called with arguments
given to Ext.util.Observable#fireEvent plus the options parameter described
below.
scope : Object (optional)
The scope (this reference) in which the handler function is
executed. If omitted, defaults to the object which fired the event.
options : Object (optional)
An object containing handler configuration.
Note: The options object will also be passed as the last argument to every event handler.
This object may contain any of the following properties:
scope : Object
The scope (this reference) in which the handler function is executed. If omitted,
defaults to the object which fired the event.
delay : Number
The number of milliseconds to delay the invocation of the handler after the event fires.
single : Boolean
True to add a handler to handle just the next firing of the event, and then remove itself.
buffer : Number
Causes the handler to be scheduled to run in an Ext.util.DelayedTask delayed by the specified number of milliseconds. If the event fires again within that time, the original handler is not invoked, but the new handler is scheduled in its place.
onFrame : Number
Causes the handler to be scheduled to run at the next animation frame event. If the event fires again before that time, the handler is not rescheduled - the handler will only be called once when the next animation frame is fired, with the last set of arguments passed.
target : Ext.util.Observable
Only call the handler if the event was fired on the target Observable, not if the event was bubbled up from a child Observable.
element : String
This option is only valid for listeners bound to Ext.Component. The name of a Component property which references an Ext.dom.Element to add a listener to.
This option is useful during Component construction to add DOM event listeners to elements of Ext.Component which will exist only after the Component is rendered.
For example, to add a click listener to a Panel's body:
var panel = new Ext.panel.Panel({
title: 'The title',
listeners: {
click: this.handlePanelClick,
element: 'body'
}
});
In order to remove listeners attached using the element, you'll need to reference the element itself as seen below.
panel.body.un(...)
delegate : String (optional)
A simple selector to filter the event target or look for a descendant of the target.
The "delegate" option is only available on Ext.dom.Element instances (or when attaching a listener to a Ext.dom.Element via a Component using the element option).
See the delegate example below.
capture : Boolean (optional)
When set to true, the listener is fired in the capture phase of the event propagation
sequence, instead of the default bubble phase.
The capture option is only available on Ext.dom.Element instances (or
when attaching a listener to a Ext.dom.Element via a Component using the
element option).
stopPropagation : Boolean (optional)
This option is only valid for listeners bound to Ext.dom.Element.
true to call stopPropagation on the event
object before firing the handler.
preventDefault : Boolean (optional)
This option is only valid for listeners bound to Ext.dom.Element.
true to call preventDefault on the event
object before firing the handler.
stopEvent : Boolean (optional)
This option is only valid for listeners bound to Ext.dom.Element.
true to call stopEvent on the event object
before firing the handler.
args : Array (optional)
Optional set of arguments to pass to the handler function before the actual
fired event arguments. For example, if args is set to ['foo', 42],
the event handler function will be called with an arguments list like this:
handler('foo', 42, <actual event arguments>...);
destroyable : Boolean (optional)
When specified as true, the function returns a destroyable object. An object
which implements the destroy method which removes all listeners added in this call.
This syntax can be a helpful shortcut to using un; particularly when
removing multiple listeners. NOTE - not compatible when using the element
option. See un for the proper syntax for removing listeners added using the
element config.
Defaults to:
false
priority : Number (optional)
An optional numeric priority that determines the order in which event handlers are run. Event handlers with no priority will be run as if they had a priority of 0. Handlers with a higher priority will be prioritized to run sooner than those with a lower priority. Negative numbers can be used to set a priority lower than the default. Internally, the framework uses a range of 1000 or greater, and -1000 or lesser for handlers that are intended to run before or after all others, so it is recommended to stay within the range of -999 to 999 when setting the priority of event handlers in application-level code. A priority must be an integer to be valid. Fractional values are reserved for internal framework use.
order : String (optional)
A legacy option that is provided for backward compatibility.
It is recommended to use the priority option instead. Available options are:
'before': equal to a priority of 100'current': equal to a priority of 0 or default priority'after': equal to a priority of -100Defaults to:
'current'
order : String (optional)
A shortcut for the order event option. Provided for backward compatibility.
Please use the priority event option instead.
Defaults to: 'current'
Only when the destroyable option is specified.
A Destroyable object. An object which implements the destroy method which removes
all listeners added in this call. For example:
this.btnListeners = = myButton.on({
destroyable: true
mouseover: function() { console.log('mouseover'); },
mouseout: function() { console.log('mouseout'); },
click: function() { console.log('click'); }
});
And when those listeners need to be removed:
Ext.destroy(this.btnListeners);
or
this.btnListeners.destroy();
The addManagedListener method is used when some object (call it "A") is listening to an event on another observable object ("B") and you want to remove that listener from "B" when "A" is destroyed. This is not an issue when "B" is destroyed because all of its listeners will be removed at that time.
Example:
Ext.define('Foo', {
extend: 'Ext.Component',
initComponent: function () {
this.addManagedListener(MyApp.SomeSharedMenu, 'show', this.doSomething);
this.callParent();
}
});
As you can see, when an instance of Foo is destroyed, it ensures that the 'show'
listener on the menu (MyApp.SomeGlobalSharedMenu) is also removed.
As of version 5.1 it is no longer necessary to use this method in most cases because
listeners are automatically managed if the scope object provided to
addListener is an Observable instance.
However, if the observable instance and scope are not the same object you
still need to use mon or addManagedListener if you want the listener to be
managed.
item : Ext.util.Observable/Ext.dom.Element
The item to which to add a listener/listeners.
ename : Object/String
The event name, or an object containing event name properties.
fn : Function/String (optional)
If the ename parameter was an event
name, this is the handler function or the name of a method on the specified
scope.
scope : Object (optional)
If the ename parameter was an event name, this is
the scope (this reference) in which the handler function is executed.
options : Object (optional)
If the ename parameter was an event name, this is
the addListener options.
Only when the destroyable option is specified.
A Destroyable object. An object which implements the destroy method which removes
all listeners added in this call. For example:
this.btnListeners = myButton.mon({
destroyable: true
mouseover: function() { console.log('mouseover'); },
mouseout: function() { console.log('mouseout'); },
click: function() { console.log('click'); }
});
And when those listeners need to be removed:
Ext.destroy(this.btnListeners);
or
this.btnListeners.destroy();
Adds a plugin. For example:
list.addPlugin('pullrefresh');
Or:
list.addPlugin({
type: 'pullrefresh',
pullRefreshText: 'Pull to refresh...'
});
Available since: 6.2.0
plugin : Object/String/Ext.plugin.Abstract
The plugin or config object or alias to add.
This method is called after the component is initially added to the DOM. If this
component Ext.Container other components, the afterRender method
for child components is called before the parent's afterRender.
Implementations of this method should avoid reading from the DOM but are free to write to the DOM as needed. To read the DOM, consider implementing onRender instead.
This method is not generally needed because components always have their own DOM element and these are maintained by config property updaters prior to insertion in the DOM. In general, it is always best to manipulate the component's elements outside the DOM where there is no associated reflow or layout cost. This method is useful for situations where the component's elements must be in the DOM in order to be manipulated correctly.
Available since: 6.5.0
This is a template method. a hook into the functionality of this class. Feel free to override it in child classes.
component : Object
alignment : Object
options : Object
Animates to the supplied activeItem with a specified animation. Currently this only works
with a Card layout. This passed animation will override any default animations on the
container, for a single card switch. The animation will be destroyed when complete.
activeItem : Object/Number
The item or item index to make active.
animation : Object/Ext.layout.card.fx.Abstract
Card animation configuration or instance.
activeItem : Object
currentActiveItem : Object
Available since: 5.0.0
binds : String/Object
currentBindings : Object
Applies the container's defaults onto a child item. The item can be a config object or an instance but has to be an inner item.
item : Object/Ext.Component
The item to apply the defaults to.
The item that was passed in
Changes the masked configuration when its setter is called, which will convert the value into a proper object/instance of Ext.Mask/Ext.LoadMask. If a mask already exists, it will use that instead.
masked : Boolean/Object/String/Ext.Mask/Ext.LoadMask
Applier for the plugins config property.
plugins : String[]/Object[]/Ext.plugin.Abstract[]
The new plugins to use.
oldPlugins : Ext.plugin.Abstract[]
The existing plugins in use.
Transforms a Session config to a proper instance.
Available since: 5.0.0
session : Object
Transforms a ViewModel config to a proper instance.
Available since: 5.0.0
viewModel : String/Object/Ext.app.ViewModel
Sets up a component name reference.
component : Ext.Component
The component to reference.
Sets up a component reference.
component : Ext.Component
The component to reference.
Bubbles up the getRefOwner hierarchy, calling the specified function
with each component. The scope (this reference) of the function call will be the
scope provided or the current component. The arguments to the function will
be the args provided or the current component. If the function returns false at any
point, the bubble is stopped.
fn : Function
The function to call
scope : Object (optional)
The scope of the function. Defaults to current node.
args : Array (optional)
The args to call the function with. Defaults to passing the current component.
Call the original method that was previously overridden with Ext.Base#override
Ext.define('My.Cat', {
constructor: function() {
alert("I'm a cat!");
}
});
My.Cat.override({
constructor: function() {
alert("I'm going to be a cat!");
this.callOverridden();
alert("Meeeeoooowwww");
}
});
var kitty = new My.Cat(); // alerts "I'm going to be a cat!"
// alerts "I'm a cat!"
// alerts "Meeeeoooowwww"
args : Array/Arguments
The arguments, either an array or the arguments object
from the current method, for example: this.callOverridden(arguments)
Returns the result of calling the overridden method
Deprecated since version 4.1.0
Use method-callParent instead.
Call the "parent" method of the current method. That is the method previously overridden by derivation or by an override (see Ext#define).
Ext.define('My.Base', {
constructor: function(x) {
this.x = x;
},
statics: {
method: function(x) {
return x;
}
}
});
Ext.define('My.Derived', {
extend: 'My.Base',
constructor: function() {
this.callParent([21]);
}
});
var obj = new My.Derived();
alert(obj.x); // alerts 21
This can be used with an override as follows:
Ext.define('My.DerivedOverride', {
override: 'My.Derived',
constructor: function(x) {
this.callParent([x*2]); // calls original My.Derived constructor
}
});
var obj = new My.Derived();
alert(obj.x); // now alerts 42
This also works with static and private methods.
Ext.define('My.Derived2', {
extend: 'My.Base',
// privates: {
statics: {
method: function(x) {
return this.callParent([x*2]); // calls My.Base.method
}
}
});
alert(My.Base.method(10)); // alerts 10
alert(My.Derived2.method(10)); // alerts 20
Lastly, it also works with overridden static methods.
Ext.define('My.Derived2Override', {
override: 'My.Derived2',
// privates: {
statics: {
method: function(x) {
return this.callParent([x*2]); // calls My.Derived2.method
}
}
});
alert(My.Derived2.method(10); // now alerts 40
To override a method and replace it and also call the superclass method, use method-callSuper. This is often done to patch a method to fix a bug.
args : Array/Arguments
The arguments, either an array or the arguments object
from the current method, for example: this.callParent(arguments)
Returns the result of calling the parent method
This method is used by an override to call the superclass method but bypass any overridden method. This is often done to "patch" a method that contains a bug but for whatever reason cannot be fixed directly.
Consider:
Ext.define('Ext.some.Class', {
method: function() {
console.log('Good');
}
});
Ext.define('Ext.some.DerivedClass', {
extend: 'Ext.some.Class',
method: function() {
console.log('Bad');
// ... logic but with a bug ...
this.callParent();
}
});
To patch the bug in Ext.some.DerivedClass.method, the typical solution is to create an
override:
Ext.define('App.patches.DerivedClass', {
override: 'Ext.some.DerivedClass',
method: function() {
console.log('Fixed');
// ... logic but with bug fixed ...
this.callSuper();
}
});
The patch method cannot use method-callParent to call the superclass
method since that would call the overridden method containing the bug. In
other words, the above patch would only produce "Fixed" then "Good" in the
console log, whereas, using callParent would produce "Fixed" then "Bad"
then "Good".
args : Array/Arguments
The arguments, either an array or the arguments object
from the current method, for example: this.callSuper(arguments)
Returns the result of calling the superclass method
Cancel a specific pending bufferableMethod call on this object.
Available since: 6.5.0
name : String
The name of the buffered method to cancel.
Returns true if a cancellation occurred.
Center this cfg-floated or positioned Component in its parent.
this
This method changes the record bound to the specified item.
itemIndex : Number
The index of the item in dataItems. Negative
numbers are used to index backwards such that -1 is the last item.
recordIndex : Number
The record's index in the store.
Retrieves the first direct child of this container which matches the passed selector or component. The passed in selector must comply with an Ext.ComponentQuery selector, or it can be an actual Ext.Component.
selector : String/Ext.Component (optional)
An Ext.ComponentQuery selector. If no selector is specified, the first child will be returned.
The matching child Ext.Component (or null if no match was found).
Clears all listeners that were attached using the "delegate" event option. Users should not invoke this method directly. It is called automatically as part of normal clearListeners processing.
Creates new Component.
config : Object
The standard configuration object.
Converts the provided type or config object into a plugin instance.
config : String/Object/Ext.plugin.Abstract
The plugin type, config object or instance.
Creates an event handling function which re-fires the event from this object as the passed event name.
newName : String
The name under which to re-fire the passed parameters.
beginEnd : Array (optional)
The caller can specify on which indices to slice.
Destroys the Widget. This method should not be overridden in custom Widgets, because it sets the flags and does final cleanup that must go last. Instead, override doDestroy method to add functionality at destruction time.
Destroys member properties by name.
If a property name is the name of a config, the getter is not invoked, so if the config has not been initialized, nothing will be done.
The property will be destroyed, and the corrected name (if the property is a config
and config names are prefixed) will set to null in this object's dictionary.
args : String...
One or more names of the properties to destroy and remove from the object.
Removes and destroys a plugin.
Note: Not all plugins are designed to be removable. Consult the documentation for the specific plugin in question to be sure.
Available since: 6.2.0
plugin : String/Ext.plugin.Abstract
The plugin or its id to remove.
plugin instance or null if not found.
name : Object
fn : Object
scope : Object
options : Object
order : Object
caller : Object
manager : Object
Perform the actual destruction sequence. This is the method to override in your subclasses to add steps specific to the destruction of custom Component.
If the Component is currently added to a Container it will first be removed from that Container. All Ext.Element references are also deleted and the Component is de-registered from Ext.ComponentManager.
As a rule of thumb, subclasses should destroy their child Components, Elements, and/or other objects before calling parent method. Any object references will be nulled after this method has finished, to prevent the possibility of memory leaks.
Available since: 6.2.0
Fires a delegated event. Users should not invoke this method directly. It is called automatically by the framework as needed (see the "delegate" event option of addListener for more details.
eventName : Object
args : Object
Continue to fire event.
eventName : String
args : Array
bubbles : Boolean
index : Number
item : Ext.Component
instanced : Boolean
Retrieves the first descendant of this container which matches the passed selector. The passed in selector must comply with an Ext.ComponentQuery selector, or it can be an actual Ext.Component.
selector : String/Ext.Component (optional)
An Ext.ComponentQuery selector or Ext.Component. If no selector is specified, the first child will be returned.
The matching descendant Ext.Component (or null if no match
was found).
Enables events fired by this Observable to bubble up an owner hierarchy by calling
this.getBubbleTarget() if present. There is no implementation in the Observable
base class.
This is commonly used by Ext.Components to bubble events to owner Containers. See Ext.Component#getBubbleTarget. The default implementation in Ext.Component returns the Component's immediate owner. But if a known target is required, this can be overridden to access the required target more quickly.
Example:
Ext.define('Ext.overrides.form.field.Base', {
override: 'Ext.form.field.Base',
// Add functionality to Field's initComponent to enable
// the change event to bubble
initComponent: function () {
this.callParent();
this.enableBubble('change');
}
});
var myForm = Ext.create('Ext.form.Panel', {
title: 'User Details',
items: [{
...
}],
listeners: {
change: function() {
// Title goes red if form has been modified.
myForm.header.setStyle('color', 'red');
}
}
});
eventNames : String/String[]
The event name to bubble, or an Array of event names.
Scrolls the specified record into view.
record : Number/Ext.data.Model (optional)
The record or the 0-based position
to which to scroll. If this parameter is not passed, the options argument must
be passed and contain either record or recordIndex.
options : Object (optional)
An object containing options to modify the operation.
animation : Boolean (optional)
Pass true to animate the row into view.
focus : Boolean (optional)
Pass as true to focus the specified row.
highlight : Boolean (optional)
Pass true to highlight the row with a glow
animation when it is in view.
record : Ext.data.Model (optional)
The record to which to scroll.
recordIndex : Number (optional)
The 0-based position to which to scroll.
select : Boolean (optional)
Pass as true to select the specified row.
This method builds up a plan object with flags and a pop-off "steps" array of method names to be called in order to fullfil the passed options of an ensureVisible call.
record : Number/Ext.data.Model (optional)
The record or the 0-based position
to which to scroll. If this parameter is not passed, the options argument must
be passed and contain either record or recordIndex.
plan : Object (optional)
An object containing options to modify the operation.
animation : Boolean (optional)
Pass true to animate the row into view.
focus : Boolean (optional)
Pass as true to focus the specified row.
highlight : Boolean (optional)
Pass true to highlight the row with a glow
animation when it is in view.
record : Ext.data.Model (optional)
The record to which to scroll.
recordIndex : Number (optional)
The 0-based position to which to scroll.
select : Boolean (optional)
Pass as true to select the specified row.
Called when an item is added to this container either during initialization of the cfg-items config, or when new items are {@link #method!add added), or inserted.
If the passed object is not an instanced component, it converts the passed object into an instanced child component.
It applies cfg-defaults applied for contained child items - that is items which are not positiond using left, top, bottom, right, centered or docked.
Derived classes can override this method to process context appropriate short-hands such as Ext.Toolbar and "->" to insert a spacer.
item : Mixed
The item being added. May be a raw config object or an instanced Component or some other short-hand understood by the container.
The component to be added.
The method finds this floated component's floatParent. That means a DOM positioning container which acts as a root element for sibling floated components, and allows allows floated components to be absolutely positioned, and their encapsulating elements to be reordered to produce a visual stacking effect.
This component's element is appended to its floatParent.
There is a global floatParent element, created on demand when the first top level
floated component is shown. This may be an item child of a container configured with
cfg-floated: true, or a free floated component which is programatically
shown.
Child items of components inside a floated component may also be configured floated.
These are give a floatParent which is created on demand wrapping the nearest floated
ancestor. This means that when that ancestor's element is brought to the top of the
stack (by moving its element to the end of its own floatParent), the descendant elements
will automatically remain above.
needsShow : Object
Finds an alternate Component to focus if this Component is disabled while focused, or focused while disabled, or otherwise unable to focus.
In both cases, focus must not be lost to document.body, but must move to an intuitively connectible Component, either a sibling, or uncle or nephew.
This is both for the convenience of keyboard users, and also for when focus is tracked within a Component tree such as for ComboBoxes and their dropdowns.
For example, a ComboBox with a PagingToolbar in is BoundList. If the "Next Page" button is hit, the LoadMask shows and focuses, the next page is the last page, so the "Next Page" button is disabled. When the LoadMask hides, it attempt to focus the last focused Component which is the disabled "Next Page" button. In this situation, focus should move to a sibling within the PagingToolbar.
A closely related focusable Component to which focus can move.
Retrieves plugin by its type alias. For example:
var list = Ext.create({
xtype: 'list',
itemTpl: '<div class="item">{title}</div>',
store: 'Items',
plugins: ['listpaging', 'pullrefresh']
});
list.findPlugin('pullrefresh').setPullRefreshText('Pull to refresh...');
Note: See also getPlugin.
Available since: 6.2.0
type : String
The Plugin's type as specified by the class's
alias configuration.
plugin instance or null if not found.
Fires the specified event with the passed parameters and executes a function (action).
By default, the action function will be executed after any "before" event handlers
(as specified using the order option of
addListener), but before any other
handlers are fired. This gives the "before" handlers an opportunity to
cancel the event by returning false, and prevent the action function from
being called.
The action can also be configured to run after normal handlers, but before any "after"
handlers (as specified using the order event option) by passing 'after'
as the order parameter. This configuration gives any event handlers except
for "after" handlers the opportunity to cancel the event and prevent the action
function from being called.
eventName : String
The name of the event to fire.
args : Array
Arguments to pass to handlers and to the action function.
fn : Function
The action function.
scope : Object (optional)
The scope (this reference) in which the handler function is
executed. If omitted, defaults to the object which fired the event.
options : Object (optional)
Event options for the action function. Accepts any
of the options of addListener
order : String (optional)
The order to call the action function relative
too the event handlers ('before' or 'after'). Note that this option is
simply used to sort the action function relative to the event handlers by "priority".
An order of 'before' is equivalent to a priority of 99.5, while an order of
'after' is equivalent to a priority of -99.5. See the priority option
of addListener for more details.
Defaults to: 'before'
Deprecated since version 5.5
Use fireEventedAction instead.
Fires the specified event with the passed parameters (minus the event name, plus
the options object passed to addListener).
An event may be set to bubble up an Observable parent hierarchy (See Ext.Component#getBubbleTarget) by calling enableBubble.
eventName : String
The name of the event to fire.
args : Object...
Variable number of parameters are passed to handlers.
returns false if any of the handlers return false otherwise it returns true.
Fires the specified event with the passed parameter list.
An event may be set to bubble up an Observable parent hierarchy (See Ext.Component#getBubbleTarget) by calling enableBubble.
eventName : String
The name of the event to fire.
args : Object[]
An array of parameters which are passed to handlers.
returns false if any of the handlers return false otherwise it returns true.
Fires the specified event with the passed parameters and executes a function (action). Evented Actions will automatically dispatch a 'before' event passing. This event will be given a special controller that allows for pausing/resuming of the event flow.
By pausing the controller the updater and events will not run until resumed. Pausing, however, will not stop the processing of any other before events.
eventName : String
The name of the event to fire.
args : Array
Arguments to pass to handlers and to the action function.
fn : Function/String
The action function.
scope : Object (optional)
The scope (this reference) in which the handler function is
executed. If omitted, defaults to the object which fired the event.
fnArgs : Array/Boolean (optional)
Optional arguments for the action fn. If not
given, the normal args will be used to call fn. If false is passed, the
args are used but if the first argument is this instance it will be removed
from the args passed to the action function.
Flushes a specific pending bufferableMethod call on this object if one is
pending.
Available since: 6.5.0
name : String
The name of the buffered method to cancel.
Returns true if a flush occurred.
Try to focus this component.
If this component is disabled or otherwise not focusable, a close relation will be targeted for focus instead to keep focus localized for keyboard users.
selectText : Boolean/Number[] (optional)
If applicable, true to also select all the text
in this component, or an array consisting of start and end (defaults to start)
position of selection.
true if focus target was found and focusing was attempted,
false if no focusing attempt was made.
We MUST use our own cells as delegates for grid-based events. Cell events will not work without this. The event system would not carry cell information if we don't delegate onto our cells.
component : Object
alignment : Object
options : Object
Prepares information on aligning this to component using alignment. Also checks to see if this is already aligned to component according to alignment.
component : Object
alignment : Object
Find component(s) that label or describe this component, and return the id(s) of their ariaEl elements.
reference : Function/String/String[] (optional)
Component reference, or array of component references, or a function that should return the proper attribute string. The function will be called in the context of the labelled component.
Element id string, or null
Returns the Component for a given index in the Container's items.
index : Number
The index of the Component to return.
The item at the specified index, if found.
Gets the bubbling parent for an Observable
The bubble parent. null is returned if no bubble target exists
Examines this container's items property
and gets a direct child component of this container.
component : String/Number
This parameter may be any of the following:
itemId
or id of the child component.items property.For additional information see Ext.util.MixedCollection#get.
The component (if found).
Returns a specified config property value. If the name parameter is not passed, all current configuration options will be returned as key value pairs.
name : String (optional)
The name of the config property to get.
peek : Boolean (optional)
true to peek at the raw value without calling the getter.
Defaults to: false
ifInitialized : Boolean (optional)
true to only return the initialized property
value, not the raw config value, and not to trigger initialization. Returns
undefined if the property has not yet been initialized.
Defaults to: false
The config property value.
Finds a docked item of this container using a reference, idor an index of its location
in getDockedItems.
component : String/Number
The id or index of the component to find.
The docked component, if found.
Returns all the Ext.Component#docked items in this container.
The docked items of this container.