Keyboard shortcuts have been a natural part of desktop applications since… well, forever. For web applications it’s really in the last few years that they’ve started to become commonplace enough for users to actually remember to use them. Not to be confused with your browsers built-in shortcut keys of course.
Bubble doesn’t at the time of writing have a built-in support for keyboard shortcuts, but you can get there with a plugin.
Setting up the keyboard shortcuts
Install the plugin as usual from Bubble’s plugin store, and then go to the page where you want to use this. This plugin requires that you place an element on the page. You’ll find it under the same name as the plugin:
Place the element anywhere on the page – don’t worry, it won’t be visible to your users. You need to make sure that it’s not invisible on page load, so make sure you don’t place it inside of a hidden group inadvertently as it won’t work.
Open up the element settings to set up the keyboard shortcuts. Note that you’ll need one element per shortcut that you want to set up.
The available keys that you can listen to are as follows:
|Shift, ctrl, alt, or meta (use mod to cover both ctrl on PC and cmd on Mac)
|Backspace, tab, enter, return, capslock, esc, escape, space, pageup, pagedown, end, home, left, up, right, down, ins, del, and plus
|Reference their normal buttons, like: a, /, $, *, or =.
Combination vs sequence
You can set up the plugin to both listen to combinations of keys, or keys that are entered in sequence (no less than one second apart), and even combine the two.
- To set up a combination use the + sign to combine the two keys: mod+enter
- To set up a sequence use space to combine the two keys: mod enter
- To use a both, use both signs: mod mod+enter
The allow globally setting
Allow globally means that the keyboard shortcut will trigger even if you are focused on a field where you may not want it to. For example, if you set up a keyboard shortcut for the enter key, you may not want it to run while you are editing multi-line text.
Conflict with browser shortcuts
If you set up a shortcut that is in conflict with already existing browser shortcuts, both will run in most cases. But note that the plugin doesn’t override the browser. Setting up a keyboard shortcut for cmd+q on a Mac is probably not going to give you the result you were hoping for.