Enabling interactivity

Event listeners

Event listener functions can be assigned to virtual nodes in the same way as specifying any other property when instantiating the node. When outputting VNodes, naming of event listeners in VNodeProperties mirrors the equivalent events on HTMLElement. Authors of custom widgets can name their events however they choose, but typically also follow a similar onEventName naming convention.

Function properties such as event handlers are automatically bound to the this context of the widget that instantiated the virtual node. However, if an already-bound function is given as a property value, this will not be bound again.

Handling focus

When outputting VNodes, widgets can use VNodeProperties‘s focus property to control whether the resulting DOM element should receive focus when rendering. This is a special property that accepts either a boolean or a function that returns a boolean.

When passing true directly, the element will only receive focus when the previous value was something other than true (similar to regular property change detection). When passing a function, the element will receive focus when true is returned, regardless of what the previous return value was.

For example:

Given element ordering, the following ‘firstFocus’ input will receive focus on the initial render, whereas the ‘subsequentFocus’ input will receive focus for all future renders as it uses a function for its focus property.

src/widgets/FocusExample.tsx

Function-based variant:

  1. import { create, tsx, invalidator } from '@dojo/framework/core/vdom';
  3. const factory = create({ invalidator });
  5. export default factory(function FocusExample({ middleware: { invalidator } }) {
  6.     return (
  7.         <div>
  8.             <input key="subsequentFocus" type="text" focus={() => true} />
  9.             <input key="firstFocus" type="text" focus={true} />
  10.             <button onclick={() => invalidator()}>Re-render</button>
  11.         </div>
  12.     );
  13. });

Class-based variant:

  1. import WidgetBase from '@dojo/framework/core/WidgetBase';
  2. import { tsx } from '@dojo/framework/core/vdom';
  4. export default class FocusExample extends WidgetBase {
  5.     protected render() {
  6.         return (
  7.             <div>
  8.                 <input key="subsequentFocus" type="text" focus={() => true} />
  9.                 <input key="firstFocus" type="text" focus={true} />
  10.                 <button onclick={() => this.invalidate()}>Re-render</button>
  11.             </div>
  12.         );
  13.     }
  14. }

Delegating focus

Function-based widgets can use the focus middleware to provide focus to their children or to accept focus from a parent widget. Class-based widgets can use the FocusMixin (from @dojo/framework/core/mixins/Focus) to delegate focus in a similar way.

FocusMixin adds a this.shouldFocus() method to a widget’s class, whereas function-based widgets use the focus.shouldFocus() middleware method for the same purpose. This method checks if the widget is in a state to perform a focus action and will only return true for a single invocation, until the widget’s this.focus() method has been called again (function-based widgets use the focus.focus() middleware equivalent).

FocusMixin or the focus middleware also add a focus function property to a widget’s API. The framework uses the boolean result from this property to determine if the widget (or one of its children) should receive focus when rendering. Typically, widgets pass the shouldFocus method to a specific child widget or an output node via their focus property, allowing parent widgets to delegate focus to their children.

See the focus middleware delegation example in the Dojo middleware reference guide for an example for function-based widgets.

The following shows an example of delegating and controlling focus across a class-based widget hierarchy and output VNodes:

src/widgets/FocusableWidget.tsx

  1. import WidgetBase from '@dojo/framework/core/WidgetBase';
  2. import { tsx } from '@dojo/framework/core/vdom';
  3. import Focus from '@dojo/framework/core/mixins/Focus';
  5. interface FocusInputChildProperties {
  6.     onFocus: () => void;
  7. }
  9. class FocusInputChild extends Focus(WidgetBase)<FocusInputChildProperties> {
  10.     protected render() {
  11.         /*
  12.             The child widget's `this.shouldFocus()` method is assigned directly to the
  13.             input node's `focus` property, allowing focus to be delegated from a higher
  14.             level containing parent widget.
  16.             The input's `onfocus()` event handler is also assigned to a method passed
  17.             in from a parent widget, allowing user-driven focus changes to propagate back
  18.             into the application.
  19.         */
  20.         return <input onfocus={this.properties.onFocus} focus={this.shouldFocus} />;
  21.     }
  22. }
  24. export default class FocusableWidget extends Focus(WidgetBase) {
  25.     private currentlyFocusedKey = 0;
  26.     private childCount = 5;
  28.     private onFocus(key: number) {
  29.         this.currentlyFocusedKey = key;
  30.         this.invalidate();
  31.     }
  33.     /*
  34.         Calling `this.focus()` resets the widget so that `this.shouldFocus()` will return true when it is next invoked.
  35.     */
  36.     private focusPreviousChild() {
  37.         --this.currentlyFocusedKey;
  38.         if (this.currentlyFocusedKey < 0) {
  39.             this.currentlyFocusedKey = this.childCount - 1;
  40.         }
  41.         this.focus();
  42.     }
  44.     private focusNextChild() {
  45.         ++this.currentlyFocusedKey;
  46.         if (this.currentlyFocusedKey === this.childCount) {
  47.             this.currentlyFocusedKey = 0;
  48.         }
  49.         this.focus();
  50.     }
  52.     protected render() {
  53.         /*
  54.             The parent widget's `this.shouldFocus()` method is passed to the relevant child element
  55.             that requires focus, based on the simple previous/next widget selection logic.
  57.             This allows focus to be delegated to a specific child node based on higher-level logic in
  58.             a container/parent widget.
  59.         */
  60.         return (
  61.             <div>
  62.                 <button onclick={this.focusPreviousChild}>Previous</button>
  63.                 <button onclick={this.focusNextChild}>Next</button>
  64.                 <FocusInputChild
  65.                     key={0}
  66.                     focus={this.currentlyFocusedKey === 0 ? this.shouldFocus : undefined}
  67.                     onFocus={() => this.onFocus(0)}
  68.                 />
  69.                 <FocusInputChild
  70.                     key={1}
  71.                     focus={this.currentlyFocusedKey === 1 ? this.shouldFocus : undefined}
  72.                     onFocus={() => this.onFocus(1)}
  73.                 />
  74.                 <FocusInputChild
  75.                     key={2}
  76.                     focus={this.currentlyFocusedKey === 2 ? this.shouldFocus : undefined}
  77.                     onFocus={() => this.onFocus(2)}
  78.                 />
  79.                 <FocusInputChild
  80.                     key={3}
  81.                     focus={this.currentlyFocusedKey === 3 ? this.shouldFocus : undefined}
  82.                     onFocus={() => this.onFocus(3)}
  83.                 />
  84.                 <FocusInputChild
  85.                     key={4}
  86.                     focus={this.currentlyFocusedKey === 4 ? this.shouldFocus : undefined}
  87.                     onFocus={() => this.onFocus(4)}
  88.                 />
  89.             </div>
  90.         );
  91.     }
  92. }