[Bug]: only zoom on mouse clik and zoom not stayes
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
- 25/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- electron, typescript
- Área
- desktop-dev
Línea de trabajo
The payload names no files, so the first step is to locate the cinematic zoom implementation — search the TypeScript sources for the click handler that currently drives zoom, then trace where the focus region is stored and cleared. The request spans several interaction sources (typing, hover, text selection, drag), so map each event source before deciding how an "active interaction region" should be derived and when it expires. Done looks like a recording where the camera holds on the focused input while typing, follows hover and selection, and still transitions smoothly on the next click.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Describe the bug
The screen recording cinematic zoom effect only responds properly to mouse clicks. When recording a screen, the camera zooms into a clicked area, but it does not properly maintain or follow the area during typing, hovering, text selection, or other continuous mouse interactions.
For example, when recording a Chrome tab, if I click the search bar, the recording correctly zooms into the search bar. However, as soon as I start typing, the zoom effect moves back toward the normal/full-screen view instead of keeping the search bar properly focused. This makes the typing portion look unfocused and breaks the cinematic flow.
The zoom system should intelligently track the user's active interaction, not just click events.
To Reproduce
Steps to reproduce the behavior:
- Start a screen recording with the cinematic/automatic zoom effect enabled.
- Open a browser such as Chrome.
- Click on the browser's search/address bar.
- Notice that the recording zooms into the search bar.
- Start typing text.
- Observe that the zoom begins moving back toward the normal/full-screen view while typing.
- After typing, click the search button or another area.
- Notice that the zoom correctly moves toward the newly clicked area again.
- Move/hover the mouse around different areas without clicking.
- Notice that the cinematic zoom does not follow or focus on the hovered area.
Expected behavior
The cinematic zoom should intelligently maintain focus on the user's current area of interaction.
- When clicking an element, zoom smoothly toward that element.
- When typing into an input field, keep the camera focused on that input field instead of zooming back out.
- While typing, maintain a stable and cinematic zoom so the text entry remains clearly visible.
- When the user moves the mouse/hover around an area, the zoom should be able to smoothly follow the relevant area when appropriate.
- When the user selects or highlights text, the camera should recognize the selected/active region and keep it in focus.
- When the user moves to another interactive element, smoothly transition the zoom toward the new area.
- When the user clicks something after typing, transition the zoom to the newly clicked area.
- Zoom transitions should be smooth and cinematic rather than abrupt.
- The system should intelligently determine the active interaction region instead of relying exclusively on click events.
The overall result should feel like a professionally edited cinematic screen recording where the viewer's attention is automatically directed toward whatever the user is currently doing.
Screenshots
If applicable, attach screenshots showing:
- The zoomed-in search bar while clicking.
- The zoomed-out state while typing.
- The expected focused state during typing.
Desktop (please complete the following information):
- OS: Windows 11
- Browser: Chrome
- Version: [please specify]
- Screen recording application/version: [please specify]
Smartphone (please complete the following information):
- Device: N/A
- OS: N/A
- Browser: N/A
- Version: N/A
Additional context
This appears to be an interaction-detection/focus-tracking issue in the cinematic zoom system. The current implementation seems to prioritize click events while ignoring or losing focus during other interaction states such as keyboard input, mouse hover, text selection, and potentially drag operations.
The zoom engine should track the active interaction context and preserve focus during continuous actions. In particular, keyboard typing should inherit the focus region from the currently active input element. The camera should not automatically return to the default zoom level simply because there is no new click event.
The goal is a natural, professional cinematic recording where the camera continuously understands what the user is interacting with, rather than only reacting to clicks.
- Lenguaje dominante
- TypeScript
- Estrellas
- 32.4k
- Forks
- 2.6k
- Merge medio
- 1 d 22 h
- PR fusionados (30 d)
- 18
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
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de webadderallorg/Recordly
-
fix(audio): deduplicate getSourceTrackIdFromPath and fix companion track misclassificationPosiblemente ocupada @SomSamantray la tomó hace 5 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
webadderallorg/Recordly#1124 ·
Los mantenedores suelen responder en 2 días
-
System FFmpeg should be preferred over bundled ffmpeg-static on Linux for GPU hardware accelerationPosiblemente ocupada @LangerSword la tomó hace 10 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
webadderallorg/Recordly#757 · 1 reacción ·
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 55/100
webadderallorg/Recordly#1136 ·
Los mantenedores suelen responder en 2 días
-
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
webadderallorg/Recordly#1134 ·
Los mantenedores suelen responder en 2 días
-
bug
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
webadderallorg/Recordly#1129 · 3 comentarios ·
Los mantenedores suelen responder en 2 días
Todos los issues de webadderallorg/Recordly
Issues similares
-
test: make the #3408 Claude OAuth token fixture obviously fake so secret scanners stop flagging itAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
code-yeongyu/senpi#3436 ·
Los mantenedores suelen responder en 1 día
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Dificultad 1/5 Menos de una hora Aptitud para principiantes 78/100
lingdojo/kana-dojo#32505 · 1 comentario · 5 reacciones ·
Los mantenedores suelen responder en 1 día
-
code-quality refactoring
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
github/gh-aw-firewall#10040 ·
Los mantenedores suelen responder en 1 día
-
review-followup
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
griffinwork40/agent-afk#3868 ·
Los mantenedores suelen responder en 1 día
-
area: import-export bug status: needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
amatya-aditya/obsidian-rss-dashboard#1191 ·
Los mantenedores suelen responder en 1 día