2022-10-10
1894
#css
David Omotayo
136407
Oct 10, 2022 â‹… 6 min read

A new guide to CSS overflow

David Omotayo Frontend developer and indie game enthusiast.

Recent posts:

Fix over-caching with dynamic IO caching in Next.js 15

Next.js 15 caching overhaul: Fix overcaching with Dynamic IO and the use cache directive.

David Omotayo
Aug 6, 2025 â‹… 10 min read
LLMs are facing a QA crisis here’s how we could solve it

LLMs are facing a QA crisis: Here’s how we could solve it

LLM QA isn’t just a tooling gap — it’s a fundamental shift in how we think about software reliability.

Rosario De Chiara
Aug 4, 2025 â‹… 7 min read

Windsurf vs. Cursor: When to choose the challenger

Windsurf AI brings agentic coding and terminal control right into your IDE. We compare it to Cursor, explore its features, and build a real frontend project.

Chizaram Ken
Jul 31, 2025 â‹… 9 min read

The CSS if() function: Conditional styling will never be the same

The CSS Working Group has approved the if() function for development, a feature that promises to bring true conditional styling directly to our stylesheets.

Ikeh Akinyemi
Jul 30, 2025 â‹… 12 min read
View all posts

2 Replies to "A new guide to CSS <code>overflow</code>"

  1. The article needs two imrovements/corrections:
    1) Stop including the property name in what you refer to as being a *value*. Property name is one thing and the value (of a property) is another thing!
    2) The article states that overflow: clip is set to the container to make overflow-clip-margin work. This is false.

    1. Hi Widheg, I apologize if my reference to the values caused confusion for you. However, I’d like you to know that the `overflow-clip-margin` property, indeed, requires the use of `overflow: clip;` to function correctly. For further information on this property, please refer to the MDN documentation.

      Thank you.

Leave a Reply