When Cursor uses Browser’s tool browser_type to fill a text in a Input Field, most of the time the submit button stays disabled and Cursor is unable to move.
If I manually type something in the field, it works. It must be something related to React state.
We don’t have a browser_run_local_js that would make our lives easier and possibly overcome this. Anyway, we should think on a way to solve that. Browser Use is essential.
Steps to Reproduce
Ask Cursor to test a CRUD app with React
Expected Behavior
The typing to change the field state
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Hey, thanks for the report. This is a known limitation with how the browser_type tool interacts with React’s synthetic event system - it doesn’t trigger onChange, which controlled inputs rely on to update state.
You’re absolutely right that a browser_run_local_js tool would help work around this. I’m escalating this to the engineering team since it’s blocking agent-based testing for React apps.
Temporary workaround:
Manually type into the fields to validate behavior
Or temporarily use uncontrolled components with refs for agent testing scenarios
Could you share a Request ID from one of the failed attempts? (Chat context menu → Copy Request ID) This will help engineering investigate.
Hi I am desperately waiting for this to be fixed as well. Same issue as described. I have done a failed attempt with this to help with debugging if you still need. Here is the requestId: 329aac0e-afc7-4040-9fe2-94aa60ce229b
It seems there have been multiple updates, including multiple updates on the intab browser, and yet this basic functionality is still broken? Can this not be made a higher priority? All these browser features are cool and all, but is useless for all my projects, and probably for majority of people who try to use it, as inputted fields never get registered, making the intab browser useless.
Please get back to me, as I noticed no one replied to my previous question either.. Thanks.
