fix(browser): use full mouse event sequence for send button #30
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using Oracle in browser mode, prompts would be correctly injected into ChatGPT's textarea—you could see the text appear—but then nothing would happen. Oracle would hang indefinitely, waiting for a response that never came because the send button was never actually triggered.
The root cause: ChatGPT's React-based UI doesn't respond to simple
.click()calls. React's synthetic event system requires the full pointer/mouse event sequence (pointerdown → mousedown → pointerup → mouseup → click) to properly trigger event handlers. The codebase already uses this pattern for the "Answer now" button, butattemptSendButtonwas still using.click().Changes:
attemptSendButtonto dispatch the full mouse event sequence