Sometimes clicks don't land where they should, like when an overlay quietly covers up a target element. Previously, mabl always fell back to a JavaScript click in these scenarios. With the new Allow JavaScript fallback clicks setting, you can now choose the behavior that best suits your application:
- On (default for existing applications) - mabl uses a JavaScript fallback click so the step completes. Best for setup steps where the page state matters more than user interaction.
- Off (default for new applications) - the step fails with a clear error. Best when verifying that a real user can physically click on the target.
How it works
mabl uses a JavaScript click as a fallback in two situations:
- the element is covered by a popup mabl couldn't dismiss, or isn't visible
- the browser didn't deliver the click to the target element
With Allow JavaScript fallback clicks on, mabl performs the JavaScript click, the step continues, and the run log records why:
The click did not reach the target element (the browser delivered it to another frame or overlay); falling back to a JavaScript click
With the setting off, the step fails instead, and the error states why mabl couldn't click the element directly.
Setup
JavaScript fallback clicks are managed at the application level. To maintain consistency in test behavior, existing applications keep the fallback setting on. New applications start with Allow JavaScript fallback clicks disabled. Here's how to change JavaScript click settings for an application:
- Open the application you want to configure and edit its settings.
- Find the JavaScript fallback clicks section.
- Turn Allow JavaScript fallback clicks on or off.
The setting applies at execution time to every click step in the application, including steps you authored earlier, so no re-authoring is needed. There is no per-step version of this setting. That behavior differs from actionability checks, where the application setting is a default for new click steps, each step carries its own value, and you can change that value in the mabl Trainer.
Cloud runs already include the delivery check. For local runs, use the latest version of the mabl Desktop App or mabl CLI.