Responsive Breakpoint
A viewport width at which a layout changes, and the assumptions that come with it.
A responsive breakpoint is a viewport size at which layout rules change, expressed as a media query. Breakpoints are the oldest tool in responsive design and remain the right one when the page really does need to be arranged differently at different window sizes.
They encode an assumption that is often false: that viewport width equals available width. Any surface where content is inset — a preview frame, a panel-adjacent region, an embedded widget — breaks that assumption, which is what Container Query exists to fix.
Three practical notes recur.
Verify at the widths people actually use. A default automation viewport is much narrower than a real monitor, and layouts that overflow at wide sizes look perfectly centred at that default. Explicitly setting a wide viewport before a visual check catches a whole class of bug that otherwise reaches the user first.
Test runners have their own default width, and it is rarely the round number you would guess. An element hidden between two breakpoints will be absent from the default canvas, and a query for it fails in a way that looks like a component bug.
Fewer breakpoints is usually better. Maintaining the same spatial arrangement across sizes, where it works, removes a whole dimension from everyone's mental model.
See also4
Hand-picked in the note itself — the neighbours worth reading next.
Container Query
Styling based on the size of an element's container rather than the viewport.
Design & Interface6 connections
Component Story
An isolated rendered instance of a component, usable as documentation, a workbench, and a test.
Testing & Verification15 connections
Headless Browser
A real browser driven programmatically without a visible window.
Testing & Verification10 connections
Visual Regression Testing
Comparing rendered output against a stored baseline to catch unintended visual change.
Testing & Verification10 connections
Related3
Nearby in the graph rather than deliberately chosen. Looser, sometimes surprising.
Linked from5
Notes elsewhere in the wiki that reach for this one.
- Component StoryTesting & Verification
An isolated rendered instance of a component, usable as documentation, a workbench, and a test.
- Container QueryDesign & Interface
Styling based on the size of an element's container rather than the viewport.
- Headless BrowserTesting & Verification
A real browser driven programmatically without a visible window.
- Integration TestTesting & Verification
A test exercising several components together, through real interfaces rather than doubles.
- Visual Regression TestingTesting & Verification
Comparing rendered output against a stored baseline to catch unintended visual change.