Documentation versions (currently viewingVaadin 24)

Keyboard Shortcuts

Creating keyboard shortcuts to components for a better user experience.

Shortcuts allow you to assign keyboard shortcuts to your components to improve end-user experience. You can add available shortcuts, create your own custom shortcuts, and configure the reaction when a shortcut is triggered.

A shortcut key combination consists of one primary key, and zero to four key modifiers (i.e., Alt, Ctrl, Meta, Shift).

Adding Click Shortcuts

Click shortcuts define alternatives to the click action in components that implement the ClickNotifier interface. You can add a click shortcut using the addClickShortcut() method.

The example below uses the addClickShortcut() method to add a click shortcut to a Button component:

TextField userName = new TextField("User name");
PasswordField password = new PasswordField("Password");

Button login = new Button("Login");
login.addClickListener(event -> this.login());

Instead of clicking the button, the user can use the Enter key to perform the action tied to the button click.

Adding Focus Shortcuts

Focus shortcuts place the focus on a Focusable component, like an input field. You can add a focus shortcut using the addFocusShortcut() method.

The example here is using the addFocusShortcut() method to add a focus shortcut to a TextTield:

TextField textField = new TextField("Label");
textField.addFocusShortcut(Key.KEY_F, KeyModifier.ALT);

The user can focus on the Label text field using the Alt+F keyboard shortcut.

Adding Custom Shortcuts

You can use the addShortcutListener() method to add a shortcut that executes custom code when the shortcut is triggered.

Assume you have a custom method, public void openCustomerCreation(), that opens an input form in which users can enter new customer information.

The following example is using the addShortcutListener() method to add a custom shortcut that executes the openCustomerCreation() method:

        this::openCustomerCreation, Key.KEY_N,
        KeyModifier.CONTROL, KeyModifier.ALT);

When the user presses Ctrl+Alt+N, the form opens. The user can then input the new customer information.

You can configure a shortcut to run any code that complies with the Command functional interface. This interface has a single method called execute(), which accepts zero arguments.

This example is using the addShortcutListener() method to show a notification:

        () ->"Shortcut triggered"),
All methods that allow you to add shortcuts return an instance of ShortcutRegistration, which provides a fluent API that you can use to further configure your shortcuts.

Configuring Active Scope

By default, shortcuts are registered to the global scope. This means that the shortcut is triggered when the user presses the correct keys, regardless of the location of their cursor, or which element is in focus on the screen.

You can configure the availability of a shortcut (e.g., only when the user focuses on an element) using the addShortcutListener() method made available by the fluent ShortcutRegistration API.

The example here is using the addShortcutListener() method to define the component to which the listener attaches:

public class Scope extends Div {
    public Scope() {
        TextField firstName = new TextField();
        TextField lastName = new TextField();

        add(firstName, lastName);

        Command command = () -> {
        // first parameter is the lifecycle owner
        // of the shortcut and it is discussed later.
                    command, Key.ESCAPE)
                // defines the component onto which
                // the shortcuts listener is attached:

The shortcut is tied to the parent component (Scope) of the input components. If the user types input into either TextField and then presses Esc, both input fields are cleared and focus is returned to the first field. This is useful when the same action should be triggered by a shortcut configured on all fields contained inside the same scope, but not outside of the enveloping component.

The shortcut is created using the factory class Shortcuts, which offers the most generic method for creating shortcuts. See Shortcut Lifecycle Owners below for more.

Removing Shortcuts

You can remove a registered shortcut using the Registration.remove() method. A method that adds or registers a shortcut returns either a Registration or ShortcutRegistration object.

This example is using the Registration.remove() method to remove a shortcut:

TextField textField = new TextField("Label");
ShortcutRegistration registration =

// something happens here

registration.remove(); // shortcut removed!

Shortcut Lifecycle Owners

Shortcuts have a lifecycle that’s controlled by an associated Component, called the lifecycleOwner component. When the component acting as a lifecycleOwner is both attached and visible, the shortcut is active. If these conditions aren’t both met, the shortcut can’t be triggered.

For focus and click shortcuts, the lifecycle owner is the component itself. It only makes sense for the click shortcut to be active when the button or input field is both in the layout and visible.

For shortcuts registered through UI, the lifecycle owner is the UI. This means that the shortcut only stops functioning when it’s removed.

You can use the Shortcuts.addShortcutListener(…​) method to create a shortcut with a lifecycle bound to a specific component.

Binding a shortcut to the lifecycle of the Paragraph component using the Shortcuts.addShortcutListener(…​) method can be done like this:

Paragraph paragraph =
        new Paragraph("When you see me, try Alt+G!");

        () ->"Well done!"),
        Key.KEY_G, KeyModifier.ALT);


The first parameter of the Shortcuts.addShortcutListener(Component, Command, Key, KeyModifier…​) method is the lifecycleOwner component. This code binds the Alt+G shortcut to the lifecycle of paragraph and is only active when the component is both attached and visible.

You can also use the bindLifecycleTo() method to reconfigure the lifecycleOwner component of shortcuts.

Binding the lifecycle of a click shortcut to another component using the bindLifecycleTo() method would look like this:

Grid<User> usersList = new Grid<>();
Button newUserButton = new Button("Add user", event -> {
        // show new user form
newUserButton.addClickShortcut(Key.KEY_N, KeyModifier.CONTROL)

The keyboard shortcut for clicking the “Add user” button is active when the usersList component is visible on the page. Once the usersList component is detached or it becomes invisible, the shortcut is no longer active.

Listening for Shortcut Events

The addShortcutListener() method has an overload method that accepts a ShortcutEventListener instead of the Command parameter. When the shortcut is detected, the event listener receives a ShortcutEvent that contains the Key, KeyModifiers, and both listenOn and lifecycleOwner components.

Registering a ShortcutEventListener and using it with the addShortcutListener() overload method is done like so:

// handles multiple shortcuts
ShortcutEventListener listener = event -> {
   if (event.matches(Key.KEY_G, KeyModifier.ALT)) {
       // do something G-related
   else if (event.matches(Key.KEY_J, KeyModifier.ALT)) {
       // do something J-related

        Key.KEY_G, KeyModifier.ALT);
        Key.KEY_J, KeyModifier.ALT);

The listener handles events triggered by multiple shortcuts; both Alt+G and Alt+J invoke the listener. The ShortcutEvent provides the matches(Key, KeyModifier…​) method to determine which shortcut triggered the event.

For additional comparisons, you can use getSource(), which returns the listenOn component. You can also use getLifecycleOwner(), which returns the lifecycleOwner component.

Shorthands for Shortcut Modifiers

ShortcutRegistration includes shorthands for assigning key modifiers to a shortcut.

The example here is using the withAlt() and withShift() key modifiers with the addFocusShortcut() method:

Input input = new Input();

The focus shortcut here is triggered with Alt+Shift+F.

ShortcutRegistration also has the withModifiers(KeyModifiers…​modifiers) method, which can be used to configure simultaneously all modifiers — or to remove all modifiers. Calling withModifiers(…​) without parameters removes all modifiers from the shortcut.

Shortcut Event Behavior on Client Side

ShortcutRegistration provides methods to define the behavior of events on the client side. With browser DOM events, you can control whether an event should propagate upwards in the DOM tree (i.e., component hierarchy), and whether it should allow default browser behavior.

By default, shortcuts consume the event. This means that events don’t propagate upwards in the DOM tree (component hierarchy). Also, the default browser behavior is prevented. For example, the characters used in the shortcut aren’t inserted into the input field, or clicking on a link prevents the browser from following the URL. See Event.preventDefault() for more information.

As an exception, click shortcuts created with the ClickNotifier::addClickShortcut(Key, KeyModifier…​) method allows default browser behavior.

You can change the default behavior using the allowEventPropagation() (fluent), allowBrowserDefault() (fluent), setEventPropagationAllowed(boolean), and setBrowserDefaultAllowed(boolean) methods.

The example that follows is using the allowBrowserDefault() method to change the default behavior of a focus shortcut:

Input input = new Input();
        // the character 'f' is entered
        // into the input, if it's focused

This next example is using the allowEventPropagation() method to react to a shortcut event and change the styles of a form:

TextField name = new TextField("Name");
TextField address = new TextField("Address");
VerticalLayout form = new VerticalLayout(name, address);

name.addFocusShortcut(Key.KEY_N, KeyModifier.CONTROL)
        // the shortcut event is propagated from the text field to the
        // form and higher in the hierarchy

// the listener attached to the view (this) can now catch the
// shortcut event and change the form styles
        () -> form.setClassName("red-border"),
        Key.KEY_N, KeyModifier.CONTROL)

Once the "Name" field has focus and the shortcut is activated, the event is propagated higher in the component hierarchy and caught by the view component.

Submitting Change Events Before Shortcut Activation

ShortcutRegistration has a resetFocusOnActiveElement() and setResetFocusOnActiveElement(boolean) to make the active focused element lose focus (i.e., it’s blurred) and receive focus again before a shortcut is triggered. This ensures any pending input value change events for that focused element are submitted before a shortcut is activated.

The following example adds a keyboard shortcut for the Save button. The resetFocusOnActiveElement() method is used to ensure that any changes made to the description field are submitted to the server before the keyboard shortcut is handled.

TextField description = new TextField("Description");
// ON_CHANGE is the default mode, but we explicitly set it here for clarity

Button save = new Button("Save");
save.addClickListener(event ->;
save.addClickShortcut(Key.ENTER, KeyModifier.CONTROL).resetFocusOnActiveElement();

Checking Shortcut States

ShortcutRegistration offers a variety of methods to check the internal state of a shortcut, as well as all configurable values that have corresponding getter methods.

Additionally, you can use the boolean isShortcutActive() method to check whether the shortcut is enabled on the client side.