Export screen text overflows its controls and statistics

Abierto
#4,274 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@thedavidweng ya está trabajando en esto.

Desde el 16/11/2026.

  • #4275 de @thedavidweng — abierto

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
1/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
rust, tauri
Área
desktop, frontend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
Rust
Estrellas
25k
Forks
2.4k
Merge medio
1 d 8 h
PR fusionados (30 d)
676

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de CapSoftware/Cap

Todos los issues de CapSoftware/Cap

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.