feat: give the camera its own layout so no control needs a scroll - #49
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Con la cámara encendida la app dejaba de caber en la pantalla. Medido en 390x844, el bloque primario ocupaba ~813 px antes de cualquier panel: cabecera 80 + stage 477 (
aspect-ratio: 3/4, altura fija que ignora el dispositivo) + chips 40 + transcripción + botones + status. Y los controles estaban debajo de todo eso, así que usar la app exigía hacer scroll mientras signas.Ahora hay dos estados. Apagada, la página de siempre. Encendida,
#appganais-running:flex: 1, adaptándose al viewport.100dvhcon respaldo avh— los navegadores móviles encogen el viewport al plegar su barra, yvhsigue midiendo la versión alta.Refina además el icono. El concepto se mantiene; el problema era de tamaño: a 32 px, cuatro dedos de 54 con huecos de 20 se fundían en una mancha y las líneas de texto de 28 desaparecían. Tres dedos más anchos y líneas de 40 sobreviven al tamaño al que el icono se ve de verdad.
Sin verificar visualmente: no hay navegador headless en el entorno, así que los criterios de "sin scroll a 390x844" y "sin desbordamiento a 320" están razonados, no comprobados. La maquetación tampoco lleva test: jsdom no calcula alturas.