"Close" button not accessible to currently opened tab #7859

Closed
opened 2026-02-16 18:08:29 -05:00 by yindo · 5 comments
Owner

Originally created by @jeremyakers on GitHub (Jan 28, 2026).

Originally assigned to: @adamdotdevin on GitHub.

Description

In the Web UI: When multiple files are open, the "close" button in not accessible for the most recently opened tab:

Image

This makes it really difficult to close to currently opened tab

Plugins

None

OpenCode version

1.1.39

Steps to reproduce

  1. Open several file tabs in Web UI, enough to fill the entire width of the window
  2. Notice that the (X) close button is not accessible on the most recently opened file tab.

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

Originally created by @jeremyakers on GitHub (Jan 28, 2026). Originally assigned to: @adamdotdevin on GitHub. ### Description In the Web UI: When multiple files are open, the "close" button in not accessible for the most recently opened tab: <img width="1205" height="173" alt="Image" src="https://github.com/user-attachments/assets/98629031-f688-4c5c-a5cc-9b8f11684715" /> This makes it really difficult to close to currently opened tab ### Plugins None ### OpenCode version 1.1.39 ### Steps to reproduce 1. Open several file tabs in Web UI, enough to fill the entire width of the window 2. Notice that the (X) close button is not accessible on the most recently opened file tab. ### Screenshot and/or share link _No response_ ### Operating System _No response_ ### Terminal _No response_
yindo added the bugweb labels 2026-02-16 18:08:29 -05:00
yindo closed this issue 2026-02-16 18:08:29 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 28, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #10988: Cant close Review - Also involves inability to close panels/sections in the Web UI desktop version

Feel free to ignore if this doesn't address your specific case.

@github-actions[bot] commented on GitHub (Jan 28, 2026): This issue might be a duplicate of existing issues. Please check: - #10988: Cant close Review - Also involves inability to close panels/sections in the Web UI desktop version Feel free to ignore if this doesn't address your specific case.
Author
Owner

@jeremyakers commented on GitHub (Jan 31, 2026):

@adamdotdevin @alexyaroshuk Not sure why this was marked "Closed" when it is clearly not fixed:

Image

Screenshot from 1.1.48

@jeremyakers commented on GitHub (Jan 31, 2026): @adamdotdevin @alexyaroshuk Not sure why this was marked "Closed" when it is clearly not fixed: <img width="888" height="117" alt="Image" src="https://github.com/user-attachments/assets/7d619e7b-b6e6-4a7c-8fd9-6032d8c81cef" /> Screenshot from 1.1.48
Author
Owner

@alexyaroshuk commented on GitHub (Jan 31, 2026):

@jeremyakers I just rechecked - it works as expected. In the above referenced PR, scroll via mouse wheel functionality was added. Your screenshot suggests that you may have scrolled the tabs to the left, which would result in the close button being not visible.

Steps:

  1. Open several file tabs in Web UI, enough to fill the entire width of the window
  2. Notice how the latest opened file (if it does not exist yet in tabs) push the tabs to the left, ensuring the close button is visible
@alexyaroshuk commented on GitHub (Jan 31, 2026): @jeremyakers I just rechecked - it works as expected. In the above referenced PR, scroll via mouse wheel functionality was added. Your screenshot suggests that you may have scrolled the tabs to the left, which would result in the close button being not visible. Steps: 1. Open several file tabs in Web UI, enough to fill the entire width of the window 2. Notice how the latest opened file (if it does not exist yet in tabs) push the tabs to the left, ensuring the close button is visible
Author
Owner

@jeremyakers commented on GitHub (Jan 31, 2026):

Ok, sure. But now try closing it. The remaining tabs scroll to the right so that the close button for the next most recent tab is now covered again. I can assure you that I did not "scroll" the tabs in my screenshot. I simply closed the rightmost tab and the next rightmost tab was then partially hidden so I could not also close it.

Your video shows that you only looked at what happens when you open a tab. Not when you close a tab or select a tab.

The correct approach here would be to make it so that when any tab becomes "in focus" (for any reason, not just from being freshly opened) it is scrolled so that the full tab is visible.

@jeremyakers commented on GitHub (Jan 31, 2026): Ok, sure. But now try closing it. The remaining tabs scroll to the right so that the close button for the next most recent tab is now covered again. I can assure you that I did not "scroll" the tabs in my screenshot. I simply closed the rightmost tab and the next rightmost tab was then partially hidden so I could not also close it. Your video shows that you only looked at what happens when you open a tab. Not when you close a tab or select a tab. The correct approach here would be to make it so that when any tab becomes "in focus" (for any reason, not just from being freshly opened) it is scrolled so that the full tab is visible.
Author
Owner

@alexyaroshuk commented on GitHub (Jan 31, 2026):

@jeremyakers I see what you mean. I will work on the fix to address this. Thanks.

@alexyaroshuk commented on GitHub (Jan 31, 2026): @jeremyakers I see what you mean. I will work on the fix to address this. Thanks.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#7859