Prompt
I'm building a responsive site and need checks for breakpoint-specific layout bugs
Latest observation
Oct 27, 2026
OpenAI APIWeb search: off
Here are practical checks you can use to catch breakpoint-specific layout bugs in a responsive site.
1) Test the key viewport ranges
Don’t just test “mobile” and “desktop.” Check the edges where bugs usually appear:
- 320–375px: small phones
- 390–430px: modern phones
- 768px: tablet portrait breakpoint
- 1024px: tablet landscape / small laptop
- 1280px+: desktop
- Also test just below and just above each breakpoint
Example:767px,768px,769px
2) Verify common layout failure points
At each breakpoint, inspect:
-
Overflow
- Horizontal scrolling
- Text or images spilling outside containers
- Fixed-width elements breaking the layout
-
Stacking and alignment
- Columns collapsing correctly
- Flex/grid items wrapping as intended
- Buttons and cards staying aligned
-
Spacing
- Padding/margins not becoming too large or too tight
- Unexpected gaps after layout shifts
-
Typography
- Headings not wrapping awkwardly
- Font sizes scaling properly
- Line height remaining readable
-
Navigation
- Menu toggles, off-canvas nav, dropdowns
- Touch targets large enough on small screens
- Nav items not overlapping
-
Images/media
- Aspect ratios preserved
- Images not stretching
- Videos/iframes fitting their containers
-
Interactive components
- Modals, tooltips, sticky headers, carousels
- Z-index issues
- Elements clipping or overlapping
3) Check orientation changes
Many bugs show up when rotating a device:
- portrait → landscape
- landscape → portrait
Pay special attention to:
- fixed position elements
- viewport height units (
vh) - content cut off below fold
4) Test zoom and browser UI effects
Responsive issues can appear when:
- browser zoom is set to 125% / 150%
- mobile browser address bar appears/disappears
- OS font scaling / accessibility settings are enabled
5) Use real-device and emulation tests
Use both:
- Browser devtools responsive mode
- Real devices when possible
Emulators are good for speed, but real devices catch:
- touch behavior
- viewport quirks
- dynamic browser chrome
- performance-related layout shifts
6) Add visual regression checks
To prevent breakpoint bugs from reappearing:
- capture screenshots for each breakpoint
- compare against baseline images
- run checks in CI
Useful when testing:
- component libraries
- landing pages
- nav/header/footer layouts
7) Automate with a breakpoint checklist
A simple QA checklist per breakpoint:
- No horizontal scrolling
- No clipped content
- No overlapping elements
- Navigation usable
- Forms usable
- Cards/grid align correctly
- Images scale properly
- Typography readable
- Sticky/fixed elements behave correctly
- Components render in the correct state
8) Example breakpoint test matrix
You can use a matrix like this:
| Viewport | Checks |
|---|---|
| 320x568 | nav, overflow, stacking, forms |
| 375x812 | spacing, text wrapping, buttons |
| 768x1024 | tablet layout, grid columns |
| 1024x768 | landscape behavior, menus |
| 1440x900 | desktop spacing, max-widths |
If you want, I can also help you create:
- a responsive QA checklist,
- a Playwright/Cypress test suite, or
- a visual regression breakpoint matrix.