search

C-Nedelcu / talk-to-chatgpt

Talk to ChatGPT AI using your voice and listen to its answers through a voice
GNU Affero General Public License v3.0
1.97k stars 333 forks source link

Issue with AIPRM Extension's "Continue" Button Interfering with TalkToChatGPT Messaging. #75

Open techwithanirudh opened 1 year ago

techwithanirudh commented 1 year ago

I think AIPRM is an amazing extension for GPT. It allows me to control the language, tone, and writing style of ChatGPT's output. However, it has a "continue" button that interferes with TalkToChatGPT's voice and automatic messaging. When I try to send a message, the "continue" button pops up, and a Chrome prompt appears, asking me if I want to discard the prompt. This is causing a big problem for me. I need help fixing this issue.

I am using Chrome, so please fix this issue.

C-Nedelcu commented 1 year ago

That looks like a cool extension. Could you provide more details such as a video or screenshots of the problem? What if you decided not to use both extensions simultaneously? It seems to me that the Continue button is something that AIPRM injects, so I am not sure if it's possible to control from my side. You might be better off asking the AIPRM developers to make the Continue button optional or something

techwithanirudh commented 1 year ago

image

C-Nedelcu commented 1 year ago

Hello, Thank you for your screenshot, I can see now that this is a standard prompt: https://www.w3schools.com/jsref/met_win_prompt.asp Which means it isn't part of the document itself (not part of the DOM) which means my extension can not control it / hide it / remove it. Unfortunately, only the AIPRM authors can make this go away. They would need to get rid of the prompt themselves.

techwithanirudh commented 1 year ago

The extension is clicking on the continue button instead of the submit button, it is not the problem with aiprm but a problem with your extension's querySelector code

C-Nedelcu commented 1 year ago

ah, I see. Then I will try installing the extension and see if I can fix it. Thanks for looking into it! I'll label this as bug in progress