SingularityLabs-ai / bard-on-chatgpt-extension

Access bard results alongside chatgpt results from chat.openai.com itself
https://chrome.google.com/webstore/detail/bardonchatgpt-bard-inside/adegllojomfnieceeanfoblmlfcdpoab
MIT License
2 stars 2 forks source link

Bug Report - Shift+Enter Activating Bard Extension on Windows 10, Edge #2

Open jman3000c opened 9 months ago

jman3000c commented 9 months ago

Bug Description:

When using the Shift+Enter keyboard shortcut in the ChatGPT 3.5 editor on the Windows 10 platform with the Edge browser, unexpected behavior occurs. Instead of functioning as a line break or a new paragraph, it seems to trigger an unintended action by activating the Bard extension within the editor.

Steps to Reproduce:

Access ChatGPT 3.5 in the Edge browser on a Windows 10 machine. Start typing some text in the editor. Press Shift+Enter to create a new line or paragraph. Expected Behavior:

The Shift+Enter combination should insert a line break or a new paragraph without activating the Bard extension within the ChatGPT 3.5 editor.

Actual Behavior:

Upon pressing Shift+Enter, the Bard extension is unexpectedly activated in the ChatGPT 3.5 editor on Windows 10, Edge. This behavior is inconsistent with standard text editing practices and disrupts the intended use of the Shift+Enter shortcut.

Browser/Platform: Edge on Windows 10

ishandutta2007 commented 9 months ago

@jman3000c This extension's primary purpose is to run Bard within the ChatGPT so that you don't have to move back and forth between the two websites, so I am not sure I understand the ticket. What exactly do you mean by "activating", it is always supposed to be active.

ishandutta2007 commented 9 months ago

@jman3000c Ok now I think I got your point, yes you wont be able to use newline in prompt (unless you copy-pase from elsewhere). Since "enter" has been overridden, any hotkey with enter would "activate" a bard query. I will keep this issue open but won't be a priority as of now since inserting newline while typing prompt is not that popular use-case. The code is opensource, so if you have any ideas of how to differentiate "enter" from "shift+enter" feel free to send a pull request. Here are the discussed lines1 lines2 Maybe we would have to try ideas like this