Recent change/regression in `{click: selector=...}` behavior – element is selected/focused but not actually clicked

Questions and Help
1

Hi everyone,

I have been using Text Blaze Autopilot snippets with {click: selector=...} commands for repetitive browser form workflows.

These snippets were working normally until recently. Less than a week ago, I noticed a change in behavior: the {click: selector=...} command seems to find the correct element and may focus or select it visually, but it does not behave like a real mouse click anymore. In other words, the page does not always register the action, and the expected JavaScript event/change in the form is not triggered.

Example:

{key: tab}{key: tab}{key: tab}{key: tab}{key: tab}{key: tab}{key: tab}{key: tab}{key: tab}{key: tab}{key: tab}{key: tab}{key: tab}

{click: selector=#MainContent_rdColoSim-boxLabelEl}

Expected behavior:

The command should click the element in the same way as a real user click, triggering the form behavior associated with that element.

Current behavior:

The element appears to be selected/focused, but the form does not reliably register the click. The same snippet was working before, and the issue started less than one week ago.

This affects workflows that depend on clicking radio buttons, labels, custom select fields, and form elements by CSS selector.

I would like to know:

  1. Was there any recent change to the Autopilot {click: selector=...} behavior?
  2. Is this a known regression?
  3. Is there a recommended workaround to force a real click event, not just focus/select the element?
  4. Should we now use a different click syntax for elements that require JavaScript event handlers?

Thanks.

2

Hi @ColunaES - in which app are you running this snippet?

3

Hi Dan,

Thank you for your generosity in taking the time to look into this.

I’m using Google Chrome on a Mac. I also tested it on another freshly formatted Mac, also with an updated version of Chrome, and the same issue happened on both machines.

The snippet was working normally on Monday, 06/08/2026. Yesterday, Friday, 06/12/2026, it was no longer working correctly.

So it does not seem to be related to a specific Mac installation or an outdated Chrome version.

The page is an internal browser-based work form that I have used with the same Text Blaze snippets for a long time. The behavior changed recently: the {click: selector=...} command appears to find/focus/select the element, but it does not trigger the same action as a real mouse click anymore.

Example:

{click: selector=#MainContent_rdColoSim-boxLabelEl}

A manual mouse click on the same element still works normally.

4

Hi @ColunaES Welcome to the forum! :slight_smile: Thanks for your detailed report, and I apologize for the inconvenience.

I have reviewed our recent updates. I am not able to see why the {click} command would have this issue.

I have emailed you to gather further details on this.