Export screen text overflows its controls and statistics

Open
#4,274 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@thedavidweng is already working on this.

Since Nov 16, 2026.

  • #4275 by @thedavidweng — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
1/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
rust, tauri
Domain
desktop, frontend

Research direction

Start in the export screen UI and its GPUI layout test mentioned in the issue; reproduce with a Studio recording at 1080p and 30 FPS, with Advanced and Export cursor only enabled. Check the MOV warning, Shareable Link destination, and statistics output value for text that stays within its control or card. A linked pull request, #4275, is already open.

Written by the indexing model from the issue text.

Description

Description

The export screen has several text layout problems:

  • With Export cursor only enabled, the transparent MOV warning runs past the right edge of its card.
  • The output value can cross into the next column in the export statistics, for example 1660×1080 · 30 fps in a 520 px-wide statistics card.
  • The Shareable Link destination is truncated in the English interface.

The text should remain readable within its own control or card.

The MOV warning extends beyond the export sidebar

The output value crosses the statistics divider

Reproduction
  1. Open a Studio recording in the editor and open Export.
  2. Select 1080p and 30 FPS, expand Advanced, and enable Export cursor only.
  3. Check the warning, the destination controls, and the output value in the statistics card.
Additional Context
  • Operating system: macOS
  • The statistics overlap was also reproduced with a GPUI layout test against commit e5fb548.
Dominant language
Rust
Stars
25k
Forks
2.4k
Avg merge
1d 8h
Merged PRs (30d)
676

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CapSoftware/Cap

All issues in CapSoftware/Cap

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.