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

[Feature]: `Update snapshot` sticky header in UI Mode Attachments panel

Abierto
  • ¿Algo no está bien?
#42,393 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@dcrousso ya está trabajando en esto.

Desde el 31/8/2026.

  • #42421 de @dcrousso — cerrado sin fusionar

Evaluación

Este issue todavía no se ha evaluado.

Descripción

v1.65
🚀 Feature Request

Add an Update snapshot action to each IMAGE DIFF section in UI Mode's Attachments panel.

The existing IMAGE DIFF header would remain sticky while scrolling through the comparison, with Update snapshot replacing that screenshot's expected snapshot with the actual screenshot.

This follows existing UI Mode patterns where actions are placed in a sticky header for the content they operate on, for example the Source panel actions:

https://github.com/user-attachments/assets/8d2c998b-2e56-4132-bccc-d3b23305bb1c

Example

After a failed test run with failing snapshots:

  1. Review a failed screenshot using the existing Diff / Actual / Expected views
  2. Click Update snapshot for any intentional change which should have the current snapshot replaced by the Actual snapshot
  3. Continue reviewing the remaining image diffs individually

The existing Attachments panel:

Image

The proposed action would be added to the existing IMAGE DIFF header:

IMAGE DIFF                                         Update snapshot
──────────────────────────────────────────────────────────────────
           Diff  Actual  Expected  Side by side  Slider

The header would remain sticky while scrolling through a large comparison. The action only appears for IMAGE DIFF sections, not other attachments.

Alternative designs can be seen in prior art:

Motivation

When several screenshot assertions fail, UI Mode lets you review each diff, but not update an intentional change directly from that diff.

I'm aware that Playwright v1.56+ supports updateSnapshots in UI Mode (issue #37007 + PR #37098), but the current workflow has a few drawbacks:

  1. If users enable it before running, snapshots are updated before users know whether the changes are correct
  2. If users run tests normally to failure and review first, accepting a change requires enabling it and running the test again, which can be slow, flaky, and interrupts the review flow
  3. Because updating is run-level, other changed snapshots can be updated before users have reviewed them
Lenguaje dominante
TypeScript
Estrellas
98.5k
Forks
6.7k
Merge medio
16 h 10 min
PR fusionados (30 d)
305

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 microsoft/playwright

Todos los issues de microsoft/playwright

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.