Did you install the tagged release 0.1.40 or just the code on main?

I ask because we pushed a bunch of fixes for element detection about ~10hr ago right around when you opened this. If you think you might have used the older code, can you re-test with the latest code on main? Thanks!

I'm experiencing the same issue, so followed the suggestion of testing the code directly on main. However it appears to be buggy as it's now clicking on random links embedded within iframes on the page. For instance the site we are testing includes the Stripe SDK, as well as YouTube videos. Browser-use is somehow randomly clicking links within the Stripe iframe that the SDK loads (which is not even visible) and randomly opening tabs to https://m.stripe.network/. It also randomly opened a tab directly to a YouTube video that was being embedded. This errant behavior does not exist in release 0.1.40

Thank you for reporting, I recently added beta support for cross-origin iframes and it appears it's causing these issues. I will revert my change for now until the feature is improved to ignore invisible iframes.

Ah I see. OK happy to test again when the changes have been reverted.

Appreciate the incredibly quick response. Thank you!

It is reverted @djwealthblock #1161

Great, thanks. I can confirm that the iframe issue no longer exists. In addition, the main branch does have significantly more coverage of clickable elements, which also resolves my initial issue.

oh whoops closed too fast, @Noam5 is your issue still present on the latest main branch?

After investigating, I was able to solve this problem by modifying the buildDomTree.js code to ensure all input elements are properly handled.

The issue was occurring because Angular-generated form controls weren't passing all the visibility and element position checks in the DOM extraction pipeline. The fix was to add special handling for input elements right after the nodeData object is initialized in the buildDomTree function:

// After nodeData is defined in buildDomTree function:
if (node.nodeType === Node.ELEMENT_NODE && node.tagName.toLowerCase() === 'input') {
  // Special handling for input elements - ensure they're always interactive
  nodeData.isVisible = true;
  nodeData.isTopElement = true;
  nodeData.isInteractive = true;
  nodeData.isInViewport = true;
  nodeData.highlightIndex = highlightIndex++;

  // Handle highlighting if enabled
  if (doHighlightElements) {
    if (focusHighlightIndex >= 0) {
      if (focusHighlightIndex === nodeData.highlightIndex) {
        highlightElement(node, nodeData.highlightIndex, parentIframe);
      }
    } else {
      highlightElement(node, nodeData.highlightIndex, parentIframe);
    }
  }
}

This approach ensures that all input elements (including checkboxes) are always treated as visible, interactive elements regardless of their CSS properties, position in the DOM, or framework-specific attributes.

oh whoops closed too fast, @Noam5 is your issue still present on the latest main branch?

Actually when using the latest main branch the problem seems to be solved