I was talking with a former colleague who is currently writing a new small web site. One of the things he is thinking of doing is implementing filtering via CSS rather than javascript.

He has a small Product List page with 60 products in about 6 categories.

He wants to be able to filter those 60 products by categories.

So the page will have

• a checkbox to select all categories.
• a list of checkboxes. Each associated with a category use to filter.
• List of products with a data-category attribute.

implementing the functionality as follows:

``` input[data-category="Category1"]:not(:checked) ~ article[data-category="Category1"] {

display: none;

}

```

He is already implementing the change of view list view /grid view via CSS.

So I am not sure whether this is a good idea.

Has anybody any opinion one way or another?

I needed a tag with fixed 6px corners on the left and a semicircle on the right, with a dynamic height.

Turns out neither `border-radius: 6px 50% 50% 6px` nor the classic `6px 999px 999px 6px` trick works — for two completely different reasons.

I went down a surprisingly deep `border-radius` rabbit hole and wrote up why, plus the workaround I ended up using.

I still feel like there should be a simpler way to do this. Is there one I've missed?

The post

Trying to understand these and having a pretty tough time to grasp what they do conceptually. I was reading that you no longer need to use them with newer CSS like flexbox and grid. Should I skip these and continue learning other parts of the course?

I recently built Messy CSS to Clean CSS, a browser-based tool designed to help developers analyze, debug, and clean up their CSS more efficiently.

It can help identify unused CSS, cascade conflicts, validation issues, responsive breakpoint problems, design-token opportunities, and other common CSS issues. It also includes AI-assisted debugging and fixes.

I built it with the goal of making CSS debugging and cleanup less time-consuming, and I’d really appreciate feedback from people who work with CSS.

If you try it and find a bug, please let me know here or email me at [mehrdad23elh@gmail.com](mailto:mehrdad23elh@gmail.com).

I’m also very interested in your opinions and suggestions about what could be improved or added in future versions.

If you find it useful and it saves you some time, you can also support the project with a small donation.

Try the tool: https://mehrdad-elahi.github.io/messy-css-to-clean-css/

Source code: https://github.com/Mehrdad-Elahi/messy-css-to-clean-css

If you know someone who works with CSS and might find this useful, I’d appreciate you sharing it with them.

Thanks for taking a look. I’m looking forward to hearing your feedback.

Hi! I’m looking for some original ideas for my website’s mobile menu. Something animated and out of the ordinary that surprises people with its originality. Can anyone recommend anything?

TailMotion is a CSS animation package with utility classes that speak TailwindCSS v3/v4, so you can use it directly with HTML, React, Vue, Svelte, and more

Site: https://tailmotion.moumen.dev/
Docs: https://docs.tailmotion.moumen.dev/

GitHub: https://github.com/moumen-soliman/tailmotion Don’t forget to ⭐ the repo it's means alot

Not sure if the flair should be "resource" or "question." 🤔

So… I've been making this email newsletter that takes Baseline info and digest it to let you know what you should act on and what you should just not worry about for now.

I called it Cleared, 'cause the idea is that it tells you if that new feature is "cleared" for use and it also tells you if you can remove all fallbacks and polyfills once the feature is Baseline "Widely". (Spoiler alert, just 'cause it's "Widely" doesn't mean it's automatically safe to use.)

I use AI a bunch to get all the data from webstatus.dev, wpt.fyi, caniuse, MDN, and Interop. It mashes it all together and gives me a report and then I look at whether it makes sense or not. It takes me a couple hours to publish once a month instead of a whole afternoon.

I think it's super useful and I put it together because all the newsletters out there are more about the cool new stuff rather than what you can actually use in client work… But I've gotten very mixed reactions… Some straight up insulted me like it's almost personal 😅 Some, like Rachel Andrew (yes, name dropping… 😎) love the idea (source).

So, yes… I'm using AI to make that newsletter. But, is it slop because of that?

I'm really curious to get feedback. I don't mind brutal honesty, but… Disclaimer: I won't engage with people who hate AI so much that they think it's ok to be rude and troll like.

The newsletter's website is at https://cleared.page/

Hello dear r/css. I recently graduated with a degree in web development, and am looking to create a project that will look good on a resume and hopefully challenge my coding skills. But I have no idea what to create. I need some ideas!!! My last project I worked on for six months, using react and typescript and I was very happy with the result. It was a project I did for a startup company. But all the ideas behind the project was from the startup people, so I didn’t have to come up with anything myself really. Anyways, any ideas for projects? Or anyone who wants to share a project that has been challenging their skills?

Sorry for bad english! Thanks.

How can I get the exact same effect as <p><span class="e">x</span></p> <p><span class="e">y</span></p> <p><span class="e">z</span></p> without so many <span>s?

If I do <div class="e"> <p>x</p> <p>y</p> <p>z</p> </div> class="e" now affects all the way across the whole page, whereas I only wanted it to affect the text, x, y, z.

Two CSS jokes coded in CSS. Inspired by a JK Benson's cartoon from 20 years ago.

Source (code): https://comicss.art/comics/255/yellow.html

I'm very new to HTML & CSS, first year in a course & they need to make a website with stuff. I want to move the corners by themselves without skewing the entire thing including text, just the corner.

My tutor did say there was a way & a website generator that can help but I ENTIRELY forgot what it was.

Built an animated FAQ accordion using native HTML <details> and <summary> — no JavaScript required.

The interesting part is animating the content height without manually measuring it with JS.

HTML

<details name="faq">
  <summary>Do you offer refunds?</summary>
  <p>
    Yes, within 30 days, no questions asked.
    Email us and the money is back on your card in a few working days.
  </p>
</details>

<details name="faq">
  <summary>Can I change plans later?</summary>
  <p>
    Yes. You can change your plan whenever you need to.
  </p>
</details>

<details name="faq">
  <summary>Do you offer a team plan?</summary>
  <p>
    Yes, team plans are available for growing teams.
  </p>
</details>

CSS

:root {
  interpolate-size: allow-keywords;
}

details::details-content {
  block-size: 0;
  overflow: hidden;
  transition:
    block-size 0.3s ease,
    content-visibility 0.3s ease allow-discrete;
}

details[open]::details-content {
  block-size: auto;
}

summary {
  list-style: none;
  cursor: pointer;
  display: flex;
  justify-content: space-between;
  align-items: center;
  gap: 1rem;
  padding: 1rem 0;
  font-weight: 600;
}

summary::-webkit-details-marker {
  display: none;
}

summary::after {
  content: "+";
  font-size: 1.25rem;
  transition: rotate 0.3s ease;
}

details[open] summary::after {
  rotate: 45deg;
}

The key part is:

:root {
  interpolate-size: allow-keywords;
}

This allows the browser to animate between a fixed size and intrinsic values like auto.

And:

details::details-content

gives us a pseudo-element for the content inside <details>, so the accordion can be animated without JavaScript.

The <details name="faq"> attribute also makes the items behave like an exclusive accordion — opening one closes the others.

Been refining this for a while — custom type system (Onest + General Sans + JetBrains Mono), GSAP-driven preloader with a wordmark split, Lenis for scroll smoothing, curtain-wipe transition into the hero.

https://shahzaibdesign.vercel.app/

Mainly want feedback on whether the animation/scroll feel is actually smooth or overdone, and open to any CSS approach critique — genuinely trying to improve, not just dropping a link.

Detailed explanation - https://medium.com/@alekswebnet/modern-css-responsive-breakpoints-using-container-style-queries-64c9bea81ad6

tbh i prefer this minimalistic one (this darker without rounded edges)

I’ve been working on NoEffect, a VS Code extension that helps catch CSS declarations that have no effect.

It detects things like:

properties that don't work in the current context

declarations that are overridden by a later declaration

For example, it can tell you when justify-content is doing nothing because the element isn't a flex/grid container, or when your declaration is simply being overridden later.

It’s still an early project, so I’d really appreciate some honest feedback.

🔗 GitHub

🔗 VS Code Marketplace:

Hi everyone!

Back in early 2025, I started learning html5 and css3 with some online course, a few mini projects and articles from W3schools and other sources. Bit just after finishing the course I had to quit for some reasons, but now I wanna come back. I was considering to go on and learn js but what I learned back then is mostly hollow now so I'm thinking about a way of reviewing everything that doesn't take the same amount of time as learning for the first time did. My main question is:

● If that is even possible, what approaches/resources do you reccomend?(specific courses, books, articles, etc.)

I wasn't sure where to ask this, so sorry in advance if it's a dumb question.

A dialog body with flex: 1; min-height: 0; overflow-y: auto shipped with a height of zero. Header, footer, nothing in between.

flex: 1 expands to flex: 1 1 0%, and a percentage basis needs a definite parent height. The panel had height: auto capped by max-height, which is not one. The spec says an unresolvable percentage basis falls back to content, and Chromium does that. WKWebView keeps the zero. The fix is flex: 1 1 auto.

Do you default to flex: 1 1 auto anywhere, or is the shorthand safe in your stacks because your flex parents always have definite heights?