# A designer traced a line-break bug back to the culprit: themselves

> "Oh f*ck I was the problem, sorry."

This is the Markdown copy of https://usesuperflow.ai/bug-book/i-was-the-problem, published for AI agents and scripts. The HTML page is canonical.

## Key facts

| Field | Value |
| --- | --- |
| Page type | Bug Book entry |
| URL | https://usesuperflow.ai/bug-book/i-was-the-problem |
| Issue type | Mobile |
| Severity | Mild |
| Status | Resolved |
| Site | Client site |
| Platform | Webflow |
| Captured on | Firefox, macOS, Mobile |
| Date | 2026-04-01 |

## Why it matters

The rarest arc in QA: report the bug, investigate the bug, discover you ARE the bug, confess in writing. Most people quietly fix it and say nothing. This person deserves a plaque.

## Outcome

Resolved by the problem themselves.

## The thread

- **Designer:** It looks like on smaller sizes the "ON BECOMING" alternate text style creates a line break where it's not needed
- **Designer:** Oh f*ck I was the problem, sorry. We passed this file back and forth so I missed some of the line breaks in Figma. I guess can we get rid of that line break in the copy?

## About Superflow

Superflow is a website and creative-asset review tool. Its agents watch every page of a site, report what changed, and route findings to the people who approve them. Teams leave contextual feedback on live sites, staging environments, PDFs, images, videos, and Lottie animations, and comments sync two-way with Asana, ClickUp, Monday, Slack, Webflow, and Google Tag Manager.

Machine-readable entry points:

- Site index: https://usesuperflow.ai/llms.txt
- Full site content in one fetch: https://usesuperflow.ai/llms-full.txt
- Free tools, with a Markdown copy of each: https://usesuperflow.ai/tools.md
- MCP server (Streamable HTTP, no account and no API key): https://usesuperflow.ai/api/mcp
- Agent card: https://usesuperflow.ai/.well-known/agent-card.json