Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Custom Cursor Not Used When Recording a Specific Window

Abierto
  • ¿Algo no está bien?
#889 0 comentarios 2 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
42/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
electron, typescript
Área
desktop-dev

Línea de trabajo

Reproduction is well described (Windows 11, Telegram, Window mode versus Full Screen mode) but no file, module or test is named, so the first step is to locate where the recording mode is chosen and where the capture stream is set up in this Electron/TypeScript app, then compare that path against the full-screen path. Expect the difference to sit in how the window capture source is configured versus the screen source. Done means a window-mode recording shows the application cursor, matching full-screen behaviour, with a note on how it was verified. Ask a maintainer which capture backend is in use before digging.

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

Descripción

Describe the bug

When recording in Window mode (recording a specific application window), the recording uses the default Windows cursor instead of the custom cursor provided by the application.

However, when recording in Full Screen mode, the application correctly replaces the Windows cursor with its own custom cursor.

There is no error message.

To Reproduce

  1. Open the application.
  2. Start a new recording.
  3. Select Window as the recording mode.
  4. Select a specific application window to record.
  5. Start and complete the recording.
  6. Save the recording.
  7. The resulting recording uses the default Windows cursor instead of the application's custom cursor.

I tested this specifically with Telegram.

Expected behavior

The application should use its own custom cursor when recording in Window mode, just as it does when recording in Full Screen mode.

The cursor behavior should be consistent between Window mode and Full Screen mode.

Screenshots

No screenshots are available at the moment. There is no visible error message.

Desktop

  • OS: Windows 11
  • Browser: Not applicable to the application itself.
  • Application tested: Telegram
  • Browser also installed/tested: Brave, latest version

Smartphone

Not applicable.

Additional context

The issue only occurs when recording a specific window. When recording the entire screen, the application's custom cursor works correctly.

The main difference appears to be the recording mode: Window mode uses the Windows system cursor, while Full Screen mode uses the application's custom cursor.

Lenguaje dominante
TypeScript
Estrellas
32.4k
Forks
2.6k
Merge medio
1 d 19 h
PR fusionados (30 d)
17

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 webadderallorg/Recordly

Todos los issues de webadderallorg/Recordly

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.