Sidebar buttons pushed off-screen due to Flexbox overflow
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- css, typescript
- Domain
- frontend
Research direction
Start by inspecting assets/index.css and the sidebar input layout. Reproduce the issue with a long code block without line breaks, then verify that the input buttons remain visible instead of moving off-screen. Done means the overflow is contained and the relevant CSS behavior is covered by the existing project checks.
Written by the indexing model from the issue text.
Description
Before submitting your bug report
- I've tried finding an answer on the Continue docs site
- I'm not able to find an open issue that reports the same bug
- I've seen the troubleshooting guide on the Continue Docs
Relevant environment info
- OS: WIN11
- Continue version: continue.continue-2.0.0-win32-x64
- IDE version: VSCODE
Description
Bug: Sidebar buttons pushed off-screen due to Flexbox overflow
Description
When generating long code blocks without line breaks, the sidebar input buttons (like "Enter") gradually move right until they're off-screen. This happens because:
- Flex containers lack
min-width: 0 - Code blocks don't have
max-width: 100%+word-break: break-all
Expected Behavior
Buttons should remain visible regardless of content length.
Workaround
Manually adding these CSS rules to ./assets/index.css fixes it:
.flex, [class*="flex"] { min-width: 0 !important; }
pre, code { max-width: 100% !important; word-break: break-all !important; }
Suggested Fix
Add to global CSS:
.container, .chat-container {
min-width: 0;
overflow-x: hidden;
}
### To reproduce
_No response_
### Log output
```Shell
- Dominant language
- TypeScript
- Stars
- 36k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from continuedev/continue
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
continuedev/continue#13291 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
continuedev/continue#13254 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
continuedev/continue#13233 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
continuedev/continue#13198 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
continuedev/continue#13197 ·
All issues in continuedev/continue
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100