Martin Auswöger

> AFAIR we have agreed on not adding any optimizations to the `.htaccess` file, because they are opinionated and might conflict with the server configuration. I agree that we should...

I thought of that in the past and I think it’s possible to write a PostCSS plugin that can achieve that, but the features would be way less powerful than...

I think the `texarea` example would be an element (not container) query because the styles would depend on the width of the element itself. This could result in the recursion...

> The problem I'm seeing with the first example is that they're based on viewport-percentage units, but the elements you'll need to be styling may not scale perfectly with the...

I proposed the CSS conditions feature on WICG Discourse: And wrote an article on how they might be an alternative for container queries:

> I think there's a way to handle circularity that makes sense to how CSS works already! I don’t think that’s true for container queries. I watched your video, but...

@beep: Awesome thanks! I’m looking forward to it :)

@gregwhitworth Thank you for taking a look at this! I agree that this feature would not solve *all* use cases for container queries, but I think it would solve many...

I just wrote another article regarding CSS conditions, including a nice hack which lets us use some form of CSS conditions today: [au.si/css-conditions-today](https://au.si/css-conditions-today) I think this demonstrates that the groundwork...

> At which point, would we just throw those styles away? That seems strange. What about using a pseudo class on the child element itself? Like so: ``` css .child-el:container(...