It's pretty dynamic on our end, such bots almost always trip over one of our honey pots and get banned automatically.

same here

Here's a simple postcss-preset-env demo showing how to switch from Browserslist's `defaults` query to Baseline, and seeing how that affects the results

github.com/GoogleChrome...

Thank you for taking a look!
I've submitted a bug report: bugs.webkit.org/show_bug.cgi...

@nicolesullivan.bsky.social I've also submitted this through feedback assistant for Safari, but maybe you can take a look?

We were very surprised to find that Safari 26 effectively breaks all our modal dialogs in all our projects :)

They "solved" this on apple.com by setting height to 100% on the body and the html element when the dialog is open.

This implies a jump to the top of the page each time you open and close the menu.

Realized that even when I want to ignore the search engine "ai" answers/summaries, my brain still reads it in the few seconds it takes to scroll away. And yes when it is an unfamiliar topic all the misinformation is happily consumed :/ Added a browser extension to hide it completely.

I think the spec is pretty nice and covers the use cases well. I am unsure about a JS API. Haven't needed it myself, so I can't speak to it.

On why I think it is important see the thread here: github.com/w3c/csswg-dr...

Yes, I was equally disappointed when I realized the implications of this :)

If you have any concrete use cases, feel free to add them in the issue :)

I filed this issue a while back: github.com/w3c/csswg-dr...

When using a typed argument with a default value: codepen.io/romainmenke/...

Property registrations from outside the CSS function do not exist inside of it.

Inside a custom function all props are untyped unless they are typed arguments or a typed result.

# c2f5fc

Sunset with just a few cloudy streaks. Everyone is always excited about the fiery streaks but I like the bits in between.

Using layers does allow for some really neat and clean source code. We really liked the structure.

Nothing really wrong with using layers, it's more that we don't need them while also experiencing some drawbacks.

So not using cascade layers is a better fit for us.

Needing to repeat base styles in each cascade layer seemed a bit silly.

This is just one example, but the most straightforward to explain.

Having full control/ownership over all styles we find that we don't need layers.

We add "[hidden][hidden] { display: none; }" in our base styles.
Using the double attribute to get a double class specificity.

When layered as "reset, base, components, ..." we found that components with ".foo { display: grid }" are always visible even when they have the "hidden" attribute.