Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhancement: allow regular "new tab"-click on chat history (left menu bar) #1628

Closed
1 task done
darkBuddha opened this issue Jan 25, 2024 · 1 comment · Fixed by #1708
Closed
1 task done

Enhancement: allow regular "new tab"-click on chat history (left menu bar) #1628

darkBuddha opened this issue Jan 25, 2024 · 1 comment · Fixed by #1708
Labels
enhancement New feature or request

Comments

@darkBuddha
Copy link

darkBuddha commented Jan 25, 2024

What features would you like to see added?

The UI items in the left menu bar (chat history) should be clickable as a regular link to allow "scrollwheel clicks". This was done for the "new chat" button in #1470, but would make sense for the chat history also.

More details

In ChatGPT, this UI element can be "clicked regularly", i.e. when I click it with the mouse scrollwheel, it opens in a new tab, as any classic <a href= link.

I use this quite often when I want to add an additional chat, rather than navigating away from the open one. (muscle memory...)

Thank you for consideration, and this awesome project in general. 🙏🏻

Which components are impacted by your request?

UI

Pictures

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@darkBuddha darkBuddha added the enhancement New feature or request label Jan 25, 2024
@darkBuddha darkBuddha changed the title Enhancement: Enhancement: allow regular "new tab"-click on chat history (left menu bar) Jan 25, 2024
@danny-avila
Copy link
Owner

Closed by #1708

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants