feat: ability to expand sidebar to see chats names #7816
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 355d148484
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
DOsinga
left a comment
There was a problem hiding this comment.
can you use the settings.json to store this? we're trying to move away from localstorage
|
@DOsinga updated it to use settings.json to store |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0ccc9cb554
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
DOsinga
left a comment
There was a problem hiding this comment.
on second thought, I'm wondering whether we should persist this at all.
consider CSS resize: horizontal on the nav panel (with min-width/max-width constraints) instead of manual mousedown/mousemove/mouseup tracking — it gives you native drag-to-resize with near-zero JS
it would be smoother, less code and yeah, might upset some people, but fixes the basic problem. what do you think?
|
also what codex says |
f444276 to
2d104dd
Compare
I deleted this by mistake: orginal comments I poseted : Hi @DOsinga I looked into this and the thing is the nav panel needs |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2d104dd46e
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
Signed-off-by: Abhijay007 <Abhijay007j@gmail.com>
Signed-off-by: Abhijay007 <Abhijay007j@gmail.com>
Signed-off-by: Abhijay007 <Abhijay007j@gmail.com>
Signed-off-by: Abhijay007 <Abhijay007j@gmail.com>
Signed-off-by: Abhijay007 <Abhijay007j@gmail.com>
Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com>
2d104dd to
80ecf05
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 80ecf05817
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| document.body.style.cursor = 'col-resize'; | ||
| document.body.style.userSelect = 'none'; | ||
| window.addEventListener('mousemove', onMouseMove); | ||
| window.addEventListener('mouseup', onMouseUp); |
There was a problem hiding this comment.
Cancel sidebar drag when pointer leaves the window
The drag lifecycle only ends on window's mouseup, so if the user starts resizing and releases the mouse outside the app window, cleanup never runs: dragStateRef stays set, userSelect/cursor overrides remain, and moving the mouse back over the app can keep resizing unexpectedly until another in-window mouseup happens. This is a user-visible interaction regression for common edge-drags and should be handled by also terminating drag on window blur/leave (or by using pointer capture).
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
@jh-block these are edge cases I think we can skip it for now
Signed-off-by: Abhijay007 <Abhijay007j@gmail.com> Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com> Signed-off-by: esnyder <elijah.snyder1@gmail.com>
Signed-off-by: Abhijay007 <Abhijay007j@gmail.com> Signed-off-by: Abhijay Jain <Abhijay007j@gmail.com> Signed-off-by: esnyder <elijah.snyder1@gmail.com>
closes : #7791
Summary
Type of Change
AI Assistance
Testing
Tested on desktop app
Screenshots/Demos (for UX changes)