Link protocols
relative link protocol
Text fragments
href="#" scrolls to top
href="" reloads the page
href="." reloads the page and remove hash and search strings
href="?" reloads the page, remove the hash and search strings but preserve the query symbol.
href="data:" handle data URLs
href="video.mp4#t=10,20" for media fragments (support is not there yet)

TL;DR js solutions is often better for accessibility. At least information is conveyed.

Popover will be more useful than ever.

The tradeoff is currently the <details> tag with two limitations: the element does not announce a navigation menu is exposed; clicking outside or pressing Esc does nothing.

Note: JS does not have the concept. If we wanted to mutate something, e’d need to put it in an object first, and then pass that object.

Yes, I missed that thought even if I am programming! We simply pass by value often and reassign the function output to a variable.

I’m still not entirely sure what object freezing is useful for — I feel like it’s rarely what you want.

Me too. I never found a good case for it.

I just want to be able to tell if a function is going to mess with its parameters.

It's a way to tell it. Does the parameters are mutated in-place?

To ensure the parameters
In JS, we can freeze an object. The object can be (deep) cloned in Go. ({...o} as shallow clone in JS)

and I think I start to get it: Rust is awesome as interfaces because it can tell from the function signature if it mutates the parameters.

Indeed:

Similar ideas have been around for a while: In 1990, Philip Wadler wrote Linear types can change the world!

About safety in C or C++:

But those languages should be seen as asbestos.

It comes down to the multiple data structures in Rust.

But this complexity is simply a way to encode the reality of dealing with data in a multi-threaded environment, a way that can be checked at compile-time, before the program even gets a chance to run.

When you manage to make the type system work with you rather than against you, you can build things that would be wildly irresponsible to write in C and C++. And that’s the promise of Rust.

A modal is a small view in the window: this view makes the rest of the content inert.

The author of Kelp use public and private cascade layer.

Public layers are: theme, extend, overrides and effects.

The unit lh can be helpful to adjust the distance of the underline from the text.

Centering text and containery

How to measure web server capacity resource management: here a quick introduction with Rust snippets.

#idea: rewrite it in JS for backend in JS.

I thought of :focus-within and got it right. The author shares a JS snippet and a method with the new :has() selector.

How much do you know out of the basic CSS rules?

The stats are one thing.

The comments are another.

And Piccalili shares it https://piccalil.li/links/the-state-of-css-2025-results-are-in/

How to handle CSS color with the new CSS color functions instead of SASS?

The best seems to be color().
There is also rgba(), hsla() and color-mix()

• color()

It’s evident that there is a growing array of new CSS capabilities that can handle many tasks we previously relied on Sass for.

Yes indeed. Also I agree: it's a per project decision to make.

Bloom filters are excellent data structures to check if an element can be in a set.

Examples can be found on Wikipedia

A typical medium-sized Rust service packaged this way weights between 20 and 40 MB before compression and between 8 and 15 MB after compression. Not bad!

How to build a mansory layout that works. 66 lines of JS.

CSS builds results in faster loading times.

Buildless CSS has also advantages.
But the @import nesting must be avoided.

The author focus is on https://kelpui.com/docs/tools/install/
Get what you want of the CSS library and it spits out the import

font-size-adjust: ex-height 0.5 instructs the browser to scale the font such that the letter "x" is exactly half of the box.

A use-case for font-size-adjust I find much more compelling is that you probably are going to use several fonts on a web-page. And you also might change fonts in the future. And they will have different intrinsic size because that’s how the things are. Part of the mess is avoidable by pinning the meaning of font size.

0.53 is the invariant ratio for Helvetica.

Instead of BlurHash that needs aditionnal JS for 83 bits string, some CSS snippets can do the work for Low Quality Image Placeholders (LQIP).

The big disadvantage of pure CSS approaches is that you typically litter your markup with lengthy inline styles or obnoxious data URLs.

A blurHash like method in CSS can also be used and that's what the author is describing.
A more simpler solution is to use one color as placeholder.