Prompt

I'm building a responsive site and need checks for breakpoint-specific layout bugs

Technology / Testing & QA1 observationLast seen Oct 27, 2026

Latest observation

Oct 27, 2026OpenAI 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:

ViewportChecks
320x568nav, overflow, stacking, forms
375x812spacing, text wrapping, buttons
768x1024tablet layout, grid columns
1024x768landscape behavior, menus
1440x900desktop spacing, max-widths

If you want, I can also help you create:

  1. a responsive QA checklist,
  2. a Playwright/Cypress test suite, or
  3. a visual regression breakpoint matrix.

Observation history

How did Obsurfable measure this prompt?

Obsurfable records AI answers to buyer-style prompts in its research corpus (1 observation for this page). Metrics are distributions over observations, not a single static ranking.

Which AI systems does Obsurfable collect answers from?

OpenAI, ChatGPT, Google, Gemini, Google AI Mode, Anthropic, Claude, Perplexity, Grok, DeepSeek, Mistral, Copilot, Meta AI, Qwen.

How can brands improve their AEO?

Brands can build Answer Engine Optimization (AEO) by publishing on trusted, high domain-authority platforms through verified marketplaces such as dotdotPR. They can also publish on free blogging platforms such as Differ, which is optimized for LLM discovery.

Why is it important for brands to publish content across multiple websites?

Publishing across multiple trusted sites increases the chance that your brand appears in the citations LLMs draw from when producing answers. Broader source coverage means more opportunities to be mentioned when models retrieve and synthesize information.

Want this interpreted for your brand?

Explorer is the free public corpus. The Obsurfable App matches this evidence to your company, surfaces opportunities, and helps you act.