[Bug]: First-run language dialog is clipped off the bottom of the screen on Windows
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- Half a day
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- css, electron, typescript
- Domain
- desktop, frontend, internationalization
Research direction
Start by locating the first-run language dialog and its window sizing or positioning code; the issue describes a fixed-position card inside a full-window container with overflow hidden. Reproduce on Windows at high display scaling and inspect how the dialog fits the window. Done means the full prompt and both buttons are visible and Enter accepts the default choice.
Written by the indexing model from the issue text.
Description
Search existing issues
- I have searched the existing issues
Describe the bug
On Windows 11, the first-launch prompt "Use your system language?" is stuck to the bottom edge of the screen and clipped. Only the title and the start of the sentence are visible:
Use your system language?
We detected 简体中文 as your system language. Do you want to switch OpenScreen to 简体中...
The rest of the sentence and both buttons (Keep current language / Switch to 简体中文) are off the bottom of the screen. Changing the display resolution does not move or resize the card. Pressing Enter does nothing, so the prompt cannot be accepted or dismissed and the app cannot be used.
Installed build: Openscreen 1.5.0 from https://github.com/siddharthvaddem/openscreen/releases (publisher Sid). That repository was archived on 2026-10-17 and no longer accepts issues, so this report is filed here.
Display: 1440x960 at 175% scaling (AppliedDPI 168). System language: 简体中文.
In the v1.5.0 launch window the prompt is position fixed, top 2rem, inside a container that is 100vw by 100vh with overflow hidden. The window is shorter than the card, so the buttons are clipped. The buttons are type=button and there is no Enter handler.
Expected behavior
The whole dialog should be on screen, including both buttons. Enter should accept the default choice. Changing the display resolution should not be required to see or dismiss the prompt.
To Reproduce
- Install the Windows exe for Openscreen 1.5.0 from https://github.com/siddharthvaddem/openscreen/releases.
-
- On Windows 11, system language Simplified Chinese, display scaling 175%, launch Openscreen.
-
- The language prompt appears clipped along the bottom edge of the screen.
-
- Change the display resolution, then press Enter. The card stays clipped and nothing happens.
Screenshots
OS
Windows
OS Version
Windows 11 build 22631, 1440x960 at 175 percent scaling
Other OS
No response
Browser
None
Browser Version
No response
Other Browser
No response
Device Type
None
Other Device
No response
Additional context
No response
- Dominant language
- TypeScript
- Stars
- 3.7k
- Forks
- 231
- Avg merge
- 16h 38m
- Merged PRs (30d)
- 327
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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 getopenscreen/openscreen
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
getopenscreen/openscreen#1423 ·
Maintainers usually reply within 1 day
-
Native review wanted: machine-translated recording bar tooltips (14 locales)May be free again @auberginewly claimed this 21 days ago, and no pull request is open. Opengood first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getopenscreen/openscreen#913 · 5 comments ·
Maintainers usually reply within 1 day
-
QA: e2e pass on v2.2.0-rc.1 (macOS, Windows)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
getopenscreen/openscreen#1431 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
getopenscreen/openscreen#1426 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 57/100
getopenscreen/openscreen#1422 · 2 comments ·
Maintainers usually reply within 1 day
All issues in getopenscreen/openscreen
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
components-web-app/docs#307 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
localstack/localstack-mcp-server#112 ·
Maintainers usually reply within 1 day
-
area:frontend kind:bug priority:p1 ready
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
bug ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
PhyberApex/kuroshiro#1687 ·
Maintainers usually reply within 1 day
-
Performance (Web Vitals) collector: LCP/FCP from background tabs are not discarded, inflating p75Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
umami-software/umami#4720 ·
Maintainers usually reply within 3 days