Event Handling

Events that fire on a page with a Webix-based application fall into three groups:

  • inner events of Webix components ("onAfterSelect", "onChange", "onItemClick", etc);
  • global Webix events connected with its application flow;
  • native DOM events (can be handled in Webix way as well).

The main part of the article below concerns the inner events of Webix components, while the details of the other two groups can be checked by the related links in the list above.

Attaching Handlers to Inner Component Events

Common inner events for all UI components are mouse events (onItemClick, onBeforeContextMenu, onMouseMoving, onMouseOut, etc.) since all the components can be clicked (and right-clicked) and respond to a mouse pointer.

Other inner events depend on the component functionality and are provided in API references for each component.

A handler can be attached to a component in different ways:

1. The most common way is to use any event of the component (check its API reference) within:

2. Depending on the component nature, you can attach a handler to some specific events defined by component properties:

Now let's study each possibility in detail.

Using the attachEvent() method

The attachEvent() method takes the name of the component's inner event and the function it fires (handler) as parameters. The syntax is:

$$("element_id").attachEvent("onSomeEvent", some_function(){/* ... */});

Event names are case-insensitive.

A button to collapse the all tree nodes

var myEvent = $$("button_id").attachEvent("onItemClick", function(){

Later on, you can easily detach this event from the component with the help of the opposite method:


Attaching a function in the component constructor

You can also define event handlers right in the component constructor within either of the following properties:

  • on - specifies the function that fires when the stated event happens;
  • ready - specifies the function that fires when the component is ready to use (has been initialized and loaded data, if any);
  • click - specifies the function that fires when the component is clicked. Works for some form controls like simple buttons and inputs. The function receives two parameters:
    • id (string, number) - the ID of the control,
    • event (object) - MouseEvent.
            click:function(){ }
            data:[ ],
            ready:function(){ }

Related sample:  Attaching Functions in the Constructor

When attaching an event you can specify only the name of a function to attach and declare it outside the webix.ui() constructor with the help of the on property:

function select_first(){
        "onItemClick": select_first

Related sample:  Creating a Custom Table

For buttons you can make it more compact by using the click property:

function close_tree(){/* ... */}; 
{view:"button", id:"sample_button", value:"Close", width:100, click:close_tree }

Attaching DataStore and TreeStore events

While data components inherit methods from DataStore and TreeStore, events aren't inherited. That's why they should be attached through the data object:"onParse", function(driver, data){
   // some code

There are also two alternative ways of attaching such events:

  • using the "data->" prefix in the handler:
datatable.attachEvent("data->onParse", function(driver, data){
    // some code 
  • using the "data->" prefix within the component's on property:
    "data->onParse", function(){
        // some code

Attaching events in the data scheme

Data scheme allows changing the default pattern of data handling within the component.

For instance, the function specified in its $init key will run each time when data are loaded/reloaded to the component and when the add method is called.

        $init:function(obj){/* ... */},
        $update:function(obj){/* ... */}

Related sample:  Horizontal List

More possibilities of the data scheme are described separately.

Using specific properties for mouse events

Such properties come in pairs and include:

  • onClick and on_click handlers for clicking;
  • onContext and on_context handlers for right-clicking;
  • onDblClick and on_dblclick handlers for double-clicking;
  • onMouseMove and on_mouse_move handlers for setting a mouse pointer over the component (item).

All these properties allow attaching the corresponding behavior (clicking, double-clicking, etc.) for the items of a component with a specified CSS class, thus redefining the default behavior.

Let's have a look at the examples that show how the onClick and on_click handlers can be used.

1. With on_click, redefining can be done only after the component initialization.

The on_click handler:

grid = webix.ui({
        { id:"", template:"<input type='button' class='delbtn' value='Delete'>"},
        { id:"title", /* ... */}
        "onItemClick":function(){/* ... */} // the default click behavior
grid.on_click.delbtn = function(e, id, trg){
    webix.message("Delete row: "+id);
    return false; // blocks the default onclick event

Related sample:  Datatable: Custom Handler

One of the columns features an HTML template with a button styled with the 'delbtn' CSS class. All cells including the one with this button will react on the default click behavior. When you click the button itself rather than on its cell area, the default behavior will be overridden with the function attached to the the 'delbtn' CSS class.

2. The onClick handler allows redefining the current click behavior right in the component constructor.

    template:"#votes# <span class='info'>Details</span>",
        info:function(e, id){
            return false; // blocks the default onclick event

When you click list item styled with info CSS class, the item won't be selected and a custom message will appear.

Note that returning false from the onClick handler blocks all further click-related events: onBeforeSelect, onAfterSelect, onSelectChange, onItemClick. To check the full stack of the blocked events, you should enable the debug version of the Webix library.

Related sample:  List: Event Handlers

The same pattern is true for other pairs of properties.

Routing Events from One Component to Another

Event Mapping helps to get rid of repetitions in code when one and the same event should be attached to different components. If you have already attached an event to the component and described the function that this event triggers, you can route this event to another component in your app.

For these needs, use the mapEvent method and pass a map into it, where the map is an event-object correspondence:

        { view:"list", id:"list1", data:list_data, on:{
        { view:"list", id:"list2", data:list_data}
// here event name should be in the lower case

As a result, when the second list is clicked, the function that was initially attached only to the first one, will be executed for it as well:

function getItemValue(id){
    var obj = this.$eventSource || this;
    var value = obj.getItem(id).value;
    webix.message("List: "", clicked: "+id);         

Note that if you need to access the object for which the handler is called at the moment, you can do it via the $eventSource property while this will always point to the object for which the handler is attached initially.

Event Handling with Component Items

Inner events make it possible to work with component items provided that the ID of an item you click, select, etc. is passed to the attached function.

For instance, you need an event that fires each time you click an item in the list and performs an action that manipulates its data.


Related sample:  Sizing and Events

Blockable Events

Events can be divided into two groups:

  • events that don't affect the app's work by their result;
  • events that affect the app's work depending with their result. If an event title contains the word "before", the continuation of the current action depends on whether the function returns true or false.

The function returns false, selection is blocked

$$("my_list").attachEvent("onBeforeSelect", function(){ return false; })

You can also temporarily block all events associated with the component by using the blockEvent() method. To re-enable event triggering use the unblockEvent() method.


Delayed Events

The default value for response to events is 500 ms. With such events as onMouseMove and onMouseOut, you can delay the server response for as much time (in milliseconds) as you need:


Keyboard Events

Components that are in focus at the moment automatically receive the ability to respond to keyboard actions and can take keyboard events, namely

  • onKeyPress - to respond to keys specified by dedicated key codes;
  • onEditKeyPress - the same, but with an editor opened;
  • onTimedKeyPress - to trigger actions after typing has been finished.

Look how the onTimedKeyPress event works with a text field to filter data in view list:

    var value = this.getValue().toLowerCase();
        return obj.title.toLowerCase().indexOf(value)==0;
// "list_input" id the ID of the dedicated "text" input control

Related sample:  List: Filtering

More information about key codes and hot keys is to be found in the UI Manager article.

Global Webix Events

Webix global events are not connected with any specific component and can be used to control general application issues (clicks, touch movements, server-side requests, etc). Some of them repeat native DOM events.

All such events are attached to the webix object:

webix.attachEvent("onRotate", function(mode){
    // logic

Events connected with Webix components functionality

  • onDataTable(config, obj) - fires the moment before a Webix datatable is rendered on the page;
  • onEditEnd - fires when a popup data editor (date, color, richselect) is closed in any of the components on the page. See Data Editors article for details;
  • onLiveValidation(editor, result, obj, value) - fires when editing starts in the component with live validation enabled;
  • onSyncUnknown(obj, source, filter) - fires when a component tries to sync its data with a non-Webix collection;
  • onReconstruct(obj) - fires when application layout is reconstructed (view is removed, added, replaced). See Dynamic UI Modifications article for details;
  • onLayoutResize(cells) - fires when application layout is resized (not window).

General page events

  • onClick(e) - fires when a click/double click happens in any application part;
  • onFocusChange(newf, oldf) -fires when focus is changed in the application. Its parameters are Webix objects, the one in focus and the one previously focused, or null if non-Webix object is focused;
  • onReady - fires at the same time with window onload event;
  • unload - fires at the same time with window onunload event.

Page events in touch environment

  • onRotate(orientation) - fires when screen is rotated;
  • onAfterScroll(pos) - fires when some webix view has been scrolled;
  • onTouchStart(context) - fires on touch start;
  • onLongTouch(context) - fires on long touch;
  • onTouchEnd(start_context, current_context) - fires on touch end;
  • onTouchMove(start_context, current_context) - fires on touch movement;
  • onSwipeX(start_context, current_context) - fires when a horizontal swipe is detected;
  • onSwipeY(start_context, current_context) -fires when a vertical swipe is detected.

The details on Touch Events are given in the related part of API reference.

Events connected with server-side requests from the page

  • onBeforeAjax(mode, url, data, request, headers, files, promise) - fires when an Ajax request is issued.
  • onAjaxError(xhr) - fires when any Ajax request results in an error;
  • onLoadError(xhr, view) - fires when an error has happened during loading the data into a component. See Management of Loading Errors article for details.

Note that these events will fire only for Ajax requests issued by Webix. It can be a custom request created with Webix Ajax interface or an automatic one (issued by a data component during data loading or saving);

Drag-n-Drop Events

Handling of Native DOM Events

Native DOM events can be handled with the help of the Webix event() and eventRemove() functions that are called from the webix object:

var eventId = webix.event("divId", "click", function(e){


  • divID - the ID of an HTML node you want to attach an event to;
  • click - the event name (note that they are used here without the on prefix);
  • handler - a function to run (its e argument points to the native event object);
  • context - (optional) additional settings:
    • bind - (object) an object that the this keyword refers to;
    • capture - (boolean) a flag that indicates on which stage (capture or bubble) event should be captured. false by default;
    • id - (string) the event handler ID (if not set, will be generated automatically).
Back to top