Skip to content
← Writing

2026-04-27·1 min read

Check the element renders before you blame the codec

I burned an evening on H.264 decoder theories. The video element was display:none on that breakpoint.

There was a stutter on a hero video loop. I spent an embarrassingly long time on PTS frames, codec negotiation, and Chrome's hardware decoder. None of it helped — because the element wasn't rendering at certain breakpoints. A `display: none` rule from a stale media query was hiding it, and the browser was serving a fallback.

First-principles debugging means starting at the bottom of the stack: is the element on the page, is the file loading, are the bytes arriving. Theories about exotic browser internals are the *last* place to look, not the first.

Anthropic
Claude
Gemini
xAI / Grok
TypeScript
Python
PowerShell
React
TanStack
Astro
Tailwind CSS
Vite
Node.js
Three.js
Radix UI
shadcn/ui
Supabase
PostgreSQL
Drizzle ORM
Express
Stripe
Firebase
Resend
Cloudflare
Vercel
Sentry
GitHub
VS Code
Unreal Engine / UEFN
UiPath
Anthropic
Claude
Gemini
xAI / Grok
TypeScript
Python
PowerShell
React
TanStack
Astro
Tailwind CSS
Vite
Node.js
Three.js
Radix UI
shadcn/ui
Supabase
PostgreSQL
Drizzle ORM
Express
Stripe
Firebase
Resend
Cloudflare
Vercel
Sentry
GitHub
VS Code
Unreal Engine / UEFN
UiPath