[Following https://shaarli.lyokolux.space/shaare/pkpvPQ]
Ok ok another use case for container queries:

Notice that the horizontal style became too condensed, this is because we used a media query. When using a media query, the browser doesn’t care about what will happen to the components if the available space isn’t enough. [...] As you’ve seen using a media query to change the card style isn’t logical in this case. The number of cards can increase or decrease and that will affect the card’s content.

new CSS features limitations are our brain:

• feature fatigue
• browser support (well is 90% for the container queries enough?)
• invisible improvements: a big chunk of the new features today are “invisible” though - they focus more on code composition and architecture.
• I don't know where I would even use the feature
• break the habit
• keep one step at a time
• find inspiration

The part on re-thinking established patterns is awesome to understand how to use the cascade, @layer and @container ! https://mxb.dev/blog/old-dogs-new-css-tricks/#h-re-thinking-established-patterns

Key takeaways:

• if someone wants high-contrast on some websites, does it mean for every websites?
• go for the accessible version first: high-contrast except for @media (prefers-contrast: less)
• why not fixing color contrast by default?

Some browsers implements customization such as Arc https://resources.arc.net/hc/en-us/articles/19212718608151-Boosts-Customize-Any-Website

It opens new ways to build one-page website too.

I way to style external links in comparison to internal ones.

I would go for the simple css selector a[href^=<domain>]

The mansory layouts is broken for tabbing and keyboard accessibility

Nice example

Simple projects that are handy to learn HTML, CSS and Javascript

It generates an image gallery from a local folder

but it is still relevant

Seulement afficher le contenu cible via :target du hash de l'URL. Ce sélecteur peut se révéler utile, notamment pour afficher du contenu et masquer le reste sur la page avec :has et :not().

OU BIEN

afficher la partie sélectionnée sur la page.

In a nutshell, the purpose of REVENGE.CSS is to apply visual regressions to any markup anti-patterns. It makes bad HTML look bad.

Interesting.

Passing CSS variable errors can be useful too.

There are also useful patterns.

• use [class] and :not([class]]
• selecting ranges of content
• selecting all the elements except the one I am interacting with
• using nesting to style an element depending on context