https://data.firefox.com/dashboard/hardware is extremely slow to respond to resize or zoom operations

Abierto
#409 2 comentarios 2 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 9 días

@stephaniehobson ya está trabajando en esto.

Desde el 4/11/2026.

  • #472 de @stephaniehobson — abierto

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Tranquilo
Stack tecnológico
javascript

Línea de trabajo

Reproduce the slowdown at https://data.firefox.com/dashboard/hardware in Firefox and Chrome using zoom and window-resize operations. Start by tracing the rendering work triggered by viewport changes and consult Bugzilla 1750463 for the Firefox slow-script interaction. Done means the page repaints in about a second or less without repeated hangs when interacting during the update.

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

Descripción

STR:

  1. Visit https://data.firefox.com/dashboard/hardware in Firefox or Chrome
  2. Zoom the page (Ctrl+) or resize your browser-window.
  3. Wait to see the page update in response to your change

EXPECTED RESULTS:
The page should repaint with the new zoom level or viewport-size in about the time it takes for its initial rendering (around a second or less).

ACTUAL RESULTS:
On my pretty-fast Lenovo laptop, the page takes over 10 seconds to update its rendering (in Firefox as well as Chrome).

This issue is especially-bad in Firefox since it's long enough to trigger our slow-script notification (if you press any keys or attempt to scroll during the hang), and that notification itself triggers another viewport-resize which queues up another batch of the same slow work to happen again. See bug https://bugzilla.mozilla.org/show_bug.cgi?id=1750463. So instead of a 10-20 second hang, you can stretch it into an indefinite-duration hang (as long as you keep interacting with keypresses or scroll events during the hang).

Lenguaje dominante
JavaScript
Estrellas
21
Forks
7
Merge medio
7 d 6 h
PR fusionados (30 d)
5

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 mozilla/ensemble

Todos los issues de mozilla/ensemble

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.