Docs Help

Terms, Icons, and Labels

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.

Access Levels

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.

Member Types

Member Syntax

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).

lookupComponent ( item ) : Ext.Component

Called when a raw config object is added to this container either during initialization of the items config, or when new items are added), or {@link #insert inserted.

This method converts the passed object into an instanced child component.

This may be overridden in subclasses when special processing needs to be applied to child creation.


item :  Object

The config object being added.


The component to be added.

Let's look at each part of the member row:

Member Flags

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.

Class Icons

- 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

Member Icons

- 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

Class Member Quick-Nav Menu

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.

Getter and Setter Methods

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.

History Bar

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.

Search and Filters

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.

API Doc Class Metadata

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:

Expanding and Collapsing Examples and Class Members

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.

Desktop -vs- Mobile View

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:

Viewing the Class Source

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.



Run Control

A Fiddle can be authored and run with or without first saving the fiddle. There are three ways to run a fiddle.

  • Click on the "Run" button in the left-hand toolbar

  • With an editor tab focused press Ctrl-Enter (Command-Enter)

  • Say "run code"

    • Requires a voice control compliant browser, microphone, and browser microphone access permission authorization

    • Requires the fiddle tab / window to be focused

    • Must be enabled in Fiddle personal preferences

By default, your fiddle will run in a Preview Panel to the right of the editor panel. The Preview Panel is collapsible and is collapsed / hidden initially and will be expanded / shown on the first run.

Open in a New Tab / Window

In the top-right of the Preview Panel is an expand control that opens the Preview Pane as its own tab / window making it easier for editing / previewing in split panel or multi-monitor setups. Closing the dedicated Preview tab will return run control to the Preview Panel in your fiddle tab.

Sharing Only the Preview

To share a fiddle you can share the fiddle URL in the browser window. However, at times you may only wish to share just the preview. To share the preview of the fiddle only you’ll share the fiddle URL / fiddle ID / file name (e.g.

Run Preferences

To manage how Fiddle runs / previews a fiddle first open your user preferences by:

  • Signing into fiddle

  • Click on your username

  • From the context menu choose "Edit my settings"

From the settings window, you can prevent saved fiddles from running on load by unchecking "Run on fiddle load".

The default run mode is to show the running fiddle in a Preview Panel to the right of the editor panel. To open fiddles in a dedicated tab / window by default choose "External (new tab / window)" in the Run Mode drop down. When “External (new tab / window)” is selected, you have the additional option to focus that window when the fiddle is run which will bring the window to the front.

Note: Chrome dev tools allows device emulation only in a tab. They disabled emulation for new windows.

To allow fiddles to be run by speaking "run code" check the “Enable Voice Commands” checkbox.

Password Restricted

Fiddles by default can be opened and run by anyone. To password protect a saved fiddle, first you need to open the Fiddle Details window:

  • Double-click on the title in the top toolbar


  • Click on the Admin button in the left-hand toolbar

  • Click on the Details option in the context menu

Then, to set a password you will need to expand the "Advanced Options" fieldset. Within this fieldset, you can enter a password in the “Password” field. Next time the fiddle is saved, the password will be set.

Fiddles protected with a password will present a prompt to enter the fiddle’s password when loaded. The user who created the fiddle will not be prompted.