The issue says “dropdown flicker on second open.” The attachment is a 42 MB QuickTime from the laptop’s screen recorder. Half the reviewers won’t download it. The other half will, once, and never re-open it. The bug is two seconds long.
I’ve started treating a short, looping GIF (or a similarly lightweight clip) as the default repro artifact for UI bugs that are visible in a few seconds. Keep the original recording if you need it. Don’t make the issue tracker host the raw file as the only way to see the problem.
When a GIF is the right repro
Good fit:
- A visual glitch that repeats (flicker, mis-aligned popover, scroll jump)
- A sequence shorter than ~8–10 seconds
- Reviewers who will see it inline in GitHub / the tracker
- A bug that’s hard to describe in prose (“it jumps, then it doesn’t”)
Poor fit:
- 30-second flows, audio, or anything where frame-perfect timing is the bug
- Color-critical / banding issues (GIF palettes lie)
- Security-sensitive sessions you shouldn’t be rasterizing into a shareable loop
- A problem that’s already captured by a failing Playwright test — prefer the test
If the clip is long, cut it first. A GIF of a five-minute session is just a worse video.
A simple repro-artifact policy
- Length — aim for a few seconds, looped; cut idle time
- Width — 600–800px is usually enough for a UI control; 1080p GIFs are a tax
- FPS — 8–12 is often enough for a flicker or a menu; 30 fps is rarely worth the bytes
- Name —
repro-dropdown-second-open.gif, notScreen Recording 2026-11-11.mov - Where — attach the GIF in the issue / PR; keep the source MP4 out of
gitunless the repo has a real media policy
Don’t commit large recordings into the app repo “for documentation.”
Convert in the tab, with width and FPS in view
You want:
- Source: MP4 / MOV / WebM from the OS recorder
- A width cap and an FPS control you can see before download
- A local preview of the loop
- No mandatory upload of an unreleased product UI to a random converter
When the file is on disk and you’re already in the browser, an in-tab converter is enough. Uwarp’s video-to-GIF tool converts MP4, MOV, or WebM in the browser — you can adjust width and FPS, and it doesn’t upload the file to a server. Handy for the one-off issue comment. If you produce repro GIFs every week, script ffmpeg instead of clicking through.
Caveats: GIF palettes will posterize gradients and shadows; if the bug is a color/contrast issue, attach a lossless clip or PNGs too. Long or high-resolution sources may hit browser memory limits — cut first. A GIF is not a substitute for a failing test once you can write one.
How to attach it so people actually watch
In the issue:
Repro (2s loop): the listbox flicker on the second open.  Steps: open → choose nothing → close → open again. Chrome 142, macOS. One looping image beats a paragraph and a 42 MB download. If the tracker inlines images, you’re done. If it doesn’t, keep the GIF small enough that “download anyway” is cheap.
Reject / send back
Reject
- 30–100 MB screen recordings as the only repro of a two-second glitch
- Full-desktop captures where the bug is a 200px widget (crop or recapture first)
- Uncut five-minute GIFs
- Uploading an unreleased flow to a random online converter when a local/tab path exists
Accept
- A short, width-capped, reasonably low-FPS GIF (or an equivalently small WebM) plus exact steps and environment
- The original recording, linked or kept locally, when someone needs frame-accurate playback
- A follow-up Playwright test once the flicker is understood
Tiny habit
After you record a UI bug, don’t paste the raw movie into the issue by default. Cut it short, convert in the tab with a width and FPS you actually looked at, and attach the loop. Reviewers will watch it. That’s the point of a repro.
